TestComplete issues with Chrome 113
Hey,
this is a general message about TestComplete issues with Chrome 113 Please note that the current version of our product may experience issues when used with Google Chrome 113. We apolog...
Forum Discussion
dhundley :
> just curious, is there not an 11 build for testcomplete?
No, there is no .11 build for TestComplete.
This numbering system has, probably, historical roots, but it exists for more than decade already.
Initially, TestComplete and TestExecute had Standard and Enterprise flavors.
Standard flavor for TestComplete ended with .5 (if I remember it correctly).
Enterprise flavor of TestComplete ended with .7.
For TestExecute Standard flavor ended with .9 (IIRC) while Enterprise flavor ended with .11.
Build number was in third set of figures. Prior to version 14 (IIRC) build numbering was continuous through all major version of the product (i.e. starting from, say, 12.0 and until final 12.x is released). Now build number seems to be reset for every minor version.
Thanks Alex
wanted to provide an update on recent developments. When I first opened up testcomplete this morning I got the notification that a new release/build was available so I downloaded and installed it. my web apps still did not work. At the suggestion of Alex Karras, I uninstalled testcomplete 15.51 and downloaded the install package for 15.49 and put it on my workstation. Now my web apps are working. My concern now is that, since I have also updated the testexecute apps on my VM’s to 15.51 will testcases I develop on my workstation with 15.49 be able to run? clearly something has changed about the newest releases of testcomplete that are causing this issue. when is smartbear going to address it?
The most aggravating part is that SmartBear has been silent for a week or more, and it has been three weeks since this issue occurred, with no evidence of a new version addressing it.
Customers are visibly affected, and we are all paying a lot of money for this product and support!
It is extremely disappointing! Especially when we are due to for a renewal in a few months and about to give another huge bucket of money to SmartBear for a product that is currently not working!
