Forum Discussion
Received an update from support saying multiple users are experiencing this issue with chrome 139 and windows 11. They have escalated the ticket and their developers are looking at the issue
anthonybad91​ Any idea by when it can be fixed?
- anthonybad9120 days agoOccasional Contributor
divyagupta03​ No answer from support on a timeline for a fix yet. Responded that this is a critical issue as we are unable to run tests successfully. I will update this post if I hear back.
We have not seen the issue with Edge at the moment. So we are using that for the time being. Looking into ways to parameterize what browser we use for a whole test suite run
- Hassan_Ballan20 days ago
Champion Level 3
That's a good workaround to use Edge until SmartBear address Chrome issue.
To run your TestComplete tests using different browsers (like Chrome or Edge) without rewriting your scripts, you can parameterize the browser selection at the project level, create a Project Variable. This allows you to switch browsers for the entire project by changing a single variable or setting.
function LaunchApp(url) { var browserName = Project.Variables.BrowserName.toLowerCase(); Browsers.Item(browserName).Run(url); } LaunchApp("https://yourwebsite.com");
You can also specify CI/CD pipeline command line value
TestComplete.exe "YourProjectSuite.pjs" /run /project:"YourProject" /pv:BrowserName=edge
💬 Found the answer helpful? Give it a Kudos by clicking Like!
✅ Got your issue resolved? Click Mark as Solution so others can find it quickly.- anthonybad9120 days agoOccasional Contributor
Yeah we found a pretty good path forward for us at the moment.
Basically added a global variable 'Browser' to our project suite. Specify 'Chrome' or 'Edge'
Then in every keyword test or script in each test project change the Navigate operation to use Parameterized, change the Browser to a variable and set the value to 'ProjectSuite.Variables.Browser'