Chrome v.139 cannot record and execute web tests with Test Studio

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Planned

Last Updated: 07 Aug 2025 10:55 by ADMIN

Lakesha

Created on: 07 Aug 2025 07:54

Type: Bug Report

Chrome v.139 cannot record and execute web tests with Test Studio

Chrome version 139 cannot record or execute Test Studio tests.

Steps to reproduce for test execution:

Open a web test and execute it.

Expected: The test to be executed as expected.
Actual: The test stops at the Navigate step and fails with the following exception in the test execution log:

Failure Information: 
~~~~~~~~~~~~~~~
Wait for condition has timed out
InnerException:
System.TimeoutException: Wait for condition has timed out
   at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
   at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
   at ArtOfTest.WebAii.Core.Browser.WaitUntilReady()
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request, Boolean performDomRefresh, Boolean waitUntilReady)
   at ArtOfTest.WebAii.Core.Browser.ExecuteCommand(BrowserCommand request)
   at ArtOfTest.WebAii.Core.Browser.InternalNavigateTo(Uri uri, Boolean useDecodedUrl)

Steps to reproduce for test recording:

Open a web test and start recording.

Expected: The browser to navigate to the selected page and to continue with the recorder attached.
Actual: The browser is launched but stays on about:blank and fails with the following exception in the application log:

EXCEPTION! (see below)
     Outer Exception Type: ArtOfTest.WebAii.Exceptions.ExecuteCommandException
     Message: ExecuteCommand failed!
          InError set by the client. Client Error:
          Protocol error (Page.navigate): Invalid referrerPolicy
          BrowserCommand (Type:'Action',Info:'NotSet',Action:'NavigateTo',Target:'null',Data:'https://telerik.com/',ClientId:'BFD7ED2D99EFCBA532CA527E680A6AC8',HasFrames:'False',FramesInfo:'',TargetFrameIndex:'-1',InError:'True',Response:'Protocol error (Page.navigate): Invalid referrerPolicy')
          InnerException: none.

1 comment

ADMIN

Elena

Posted on: 07 Aug 2025 10:55

Hello,

The issue is caused by some changes in the Chrome browser version v.139. Test Studio team is already working on implementing a fix.

Workarounds:

Use Edge for automation.
Use Chrome for Testing with a previous version - follow the steps outlined in this article. You can use the example link listed in the instructions.

Regards,
Elena
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.