ContributionsMost RecentMost LikesSolutionsRe: Problems with TestComplete 15 and Chrome 113 Fyi, looks like it is now fixed in Chrome. Should I now say "Happy testing!", or is is too early for that? Lol. Have a great day guys. Re: Running tests through pipeline using TC test adapter and publishing to the 'Tests' tab in DevOps HiadamH1. If I understand it correctly, you want the list of tests with their corresponding results? You can view it at the bottom of the Test tab. Just make sure to clear the filter over here... Let me know if that will work. Edge has joined the party. Its version 113 is now having the issue too. Do we have an update about the issue we're facing on the latest browser versions? First observed in Chrome version 113. Now I'm facing it in Edge too. Re: Problems with TestComplete 15 and Chrome 113 count me in. I'm having this issue as well Re: Events on TestComplete ChloeJust my 2 cents... You can also explore adding a 'Run Script Routine' operation. That way you can call a block of code within your keyword tests. Re: Not able to bind testcomplete test cases with Azure Himeghaphophalia!Were you able to resolve this issue? I'm having the same thing now. Re: facing issue while integrating Testcomplete with Azure devops Same with AlexKaras , I am also curious of how the TestComplete Test Adapter was set up in the pipeline. dhasadeIf there's still no luck after trying the suggestions above, you might want to double check the "Search for test cases" field in TC Test Adapter. If value is In Execution Plan, go check in TestComplete if your tests are already added in Execution plan and if they are all checked and marked as a Test case. Screenshot source:https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/execution-plan/index.html Which object search strategy is better? Which is better - Depth-first or Breadth-first? I already scanned through the documentation (link below) and already compared both by running a simple script, but I don't see much time difference. https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/properties/playback.html Any thoughts on which would be better on certain occasions? SolvedRe: Unable to navigate to URL from TestExecute SaraJensAny more clues you can get on the test reports (attached on the pipelines) ? My guesses: 1. An unexpected screen was encountered after it launches the browser with a clear cache (ex. splash screens, pop ups). 2. The page took longer time to load, as compared to your local runs. Possible solutions: For 1, you might need to add additional steps to handle those objects For 2, you might add or improve your step to wait for the page load Re: Need to use different namemapping files when running on different versions of the same Tested App Maybe you can try merging your NameMappings into one. You'll find the steps here: https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/how-to/merge.html