An alternative... rather than going third party, have you looked into using TestComplete's own aqHTTP object for sending Get and Post requests?
https://support.smartbear.com/testcomplete/docs/reference/program-objects/aqhttp/index.html
__getprop__ only applies to objects from your AUT, not to the requests object.
Just as an experiment, what happens if you add the requests package to the ...\TestComplete 12\Bin\Extensions\Python\Python36\Lib folder as well. Does that work better?
Thanks, Robert,
That makes sense about the __getprop__ only being for tested objects' properties. It was a punt...and is always an afterthought/fix for me when the standard Python format fails on me. :-)
I did copy the requests package to the x86 path, stopped and restarted the x64 version of TestComplete (just to be certain!) and get the same error on the "get" (direct requests.get, not requests.__getprop__). I also ran the x86 version of TestComplete and get the same error. It is finding the package, because I get a different error (ModuleNotFoundError: No module named 'requests') if the package is not in the right path.
Good thoughts/info, though. Much appreciated. Other ideas??
Can you inspect the "requests" object? By that, I mean drop a break point in your test complete code and use the Evaluation tool to see what "requests" actually has in the way of properties, methods, fields, etc. It could be that "get" might be an overloaded function in which case TestComplete might actually see get1, get2, get3, etc.
Another good suggestion and I've done that earlier in the week, or at least explored the Local var values of a "requests" object (defined as "r" in the attached). I see nothing that looks like a "get" of any kind at the first or second level.
