a501715
New Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Edge has joined the party. Its version 113 is now having the issue too.
I have raised a new Case #00550249 to SmartBear regarding Edge 113. Last week I reported Case #00549796 to smartBear regarding Chrome 113 It is not an option for us to downgrade the browsers as we are a large company that will not allow security risks.379Views0likes0CommentsTestComplete and TestExecute does not support Chrome version 113
On wednesday May 3rd I reported a problem with TestComplete and TestExecute could not connect to Chrome version 113.0.5672.64 Case #00549796 Response from Support: "As a temporary solution, we suggest using a different browser such as Firefox instead of Chrome or Edge." As have been said by another member: We must test with the browsers most of our customers are using. As we are a large company that has high focus on security we have to use the newest version the browsers. SmartBear with TestComplete is still only supporting up to Chrome version 99. What is happening at SmartBear ? Customers are expecting more from a large company as SmartBear.ReadyAPI allow relative path for project´s .xml file
The path to the project´s .xml file when running ReadyAPI tests is fixed. When several users are using this project they all have to install the project in the same file-location since relative path is not supported by TC. Response from SmartBear when addressing this issue: Unfortunately, it doesn't look like TestComplete supports relative paths for this field. ${projectDir} is only available in SoapUI and the documentation is only relevant for SoapUI. I have spoken with a few team members and there does not seem to be any alternative to hard-coding the path.1.1KViews0likes0Comments