Navigate Step: AUTO Browser Ready Property (Auto-wait?)

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 15 Dec 2023 09:48 by ADMIN

sitefinitysteve

Created on: 03 Sep 2013 13:42

Type: Feature Request

Navigate Step: AUTO Browser Ready Property (Auto-wait?)

I hate "Wait" steps...I really do, they bloat my tests, and are flakey as all heck.  Lets say my page takes 10.1 seconds to be "ready" but the wait is 10 seconds...FAIL (when in reality everything is fine, or would be in .1 seconds)...so increase the timeout to 15 seconds, then maybe my CPU is chugging and the page doesn't return for 15.1 seconds...

It's this constant annoying dance of managing wait times that's crazy frustrating.

Can we not have on navigate steps a DOM Ready or some other thing to just not run the next step...because IMO the "Navigate" step isn't complete...until it's complete.  

Wait for Url doesn't work because again
1) It's another bloat step
2) Assumes I know the URL, so if it's gonna fail here, and a bad url arrives I'm "waiting" an ungodly amount of time for the test to then just fail out.

My tests would be less frustrating to write if navigate just "Waited" by itself.

1 comment

ADMIN

Konstantin Petkov

Posted on: 17 Sep 2013 14:17

Hi Steve,

So the thing is Navigate steps aren't responsible (at least now) about the browser ready state. That's part of the work the Manager.LaunchNewBrowser does in the context of the framework or what the execution engine does in Test Studio before it starts running each test step. Next the Navigate step simply talks with the browser to navigate to the requested page. Auto-wait may come in place with the next steps (actions or verifications) when the execution needs to find the elements accordingly (WaitOnElements property).

So looking at your request I wonder if that makes sense for NavigateTo or also for steps dealing with elements. Does that makes sense?

Thanks for the feedback!