Champion Level 3Hello tbwg,
We don't see this here. Our test volume isn't as high as yours however. I am sure this is frustrating. It would help to know more about your test environment. We run our pipelines on dedicated VM's through Azure DevOps pipelines.
Good call on check here though, there are many people here and one of us may have see this!
If you don't get a solid answer, given the nature of the behavior it would be best to write up a very basic test and run it repeatedly to rule out everything your can.
After that I would contact SmartBear:
... If you find my posts helpful drop me a Like👍 Be sure to mark the post as the Solution✅ when you get one to help others out and to credit the one who helped you. 😎
Hi scot1967,
Here is an explanation about our test environment.
* 10x Linux application servers, configured in Jenkins as lockable resources.
* 14x dedicated Windows servers with TestExecute, each configured as a Jenkins node.
* In Jenkins, we manage approximately 40 pipelines, distributed across various branches and teams.
Each test (build) uses:
* One application server to execute the application.
* The application client is a Java executable, but we also use Google Chrome in most tests.
* Multiple TestExecute nodes to execute automated tests.
* Each pipeline runs at least once every 24 hours, resulting in a minimum of 40 builds per day, each triggering a significant number of TestExecute test runs. A pipeline typically consists of multiple TestExecute stages, where tests can be executed in parallel within a stage.
* Each TestExecute node executes a maximum of one test at a time to ensure stability and reliability.
We already opened a ticket with Smartbear months ago but it hasn't lead to a solution yet.
Champion Level 3It's most likely being disabled by your Group Policy or Chrome
SmartBear Test Extension in Incognito
