We internally have produced a product that has a Python library based on 3.7.3 (all dlls are compiled aginst 3.7.3)
I've been struggling taking my standlone Python 3.7.3 scripts to work in Test Complete.
After banging my head against a brick wall I found out that installing python 3.6 locally causes the same issue..
Hence TestComplete does not work.
So I'm after a TestComplete Python 3.7 update...
ie. replacement of the 'aqPyScript36.dll' and Python36 folder.
(TestComplete included python3.6 was complied in 2016!!)
can anyone help.?
Solved! Go to Solution.
Note the first line that TestComplete supports Python 3.6 as of TestComplete 14.30.
Essentially, again as per the article, TestComplete has it's own internal copy of the Python engine that it uses based upon 3.6. If you want to utilize Python libraries developed outside of TestComplete, they need to be compatible with 3.6 and you need to follow the instructions as per the article for importing those libraries.
Updating TestComplete to use Python 3.7 is not something available to the general user. That's something to request as a feature for SmartBear to develop.
You can request such things (or look for a similar request) at https://community.smartbear.com/t5/TestComplete-Feature-Requests/idb-p/TestXCompleteFeatureRequests
The only solution I would was for us to recompile our Lib against Python 3.6.
This worked... buth then I fell into the trap of only being able to run it once... every subsequent run throws error.
I found another post about this .. something about Com instances and found no workaround.
I'm looking into running the python externally and feeding back responses into TC...
This is giving hard ache also, may just end up running this particular suite of tests out of TC.
If TC becomes Python3.7 and I don't have to fight the Com Instances issue; then I can return this test suite back to TC