Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Declined
Last Updated: 13 Dec 2023 14:54 by ADMIN
David
Created on: 25 Feb 2013 13:56
Type: Feature Request
3
need a way to adjust all wait times
It would be very powerful to be able to provide a single place where all local step wait times can be adjusted.  Our environments can have radically different timing profiles and it is difficult to adjust times on various steps as we find that they are insufficient.  It also wastes time to code an unreasonably high timeout for an environment that doesn't need it - tester can be stuck waiting for tests to error out.

One suggestion might be to allow extracted values to be configured for the wait times.  This might put a burden on the test writer, but at least the values can be controlled.  Tighter integration, like an additional test list setting would be more user friendly.
6 comments
ADMIN
Konstantin Petkov
Posted on: 25 Mar 2013 15:11 
I see and agree that makes sense. Thanks for the feedback and please keep it coming!
David
Posted on: 25 Mar 2013 14:49 
Right, something like that - basically, it is too time consuming to update times on individual steps.  What if there was a fuzzy value like - short, medium, long that was configured on each step, then a place where you could configure what each of those meant?
ADMIN
Konstantin Petkov
Posted on: 25 Mar 2013 14:15 
So this is about the Wait steps' Timeout property, correct? I think this one has no global value one can change. So your request is to expose a property to control that one, isn't it? Similar to WaitCheckInterval:
http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/settings-class.aspx
David
Posted on: 25 Mar 2013 13:34 
Hi Konstantin - sorry I missed your earlier post.  We are fine with the test list level wait for element, we set that by updating the test list XML ahead of time.  My issue here is the wait times at each step...for example, a wait for visible step.  The global time controls the wait for the element to exist, but then I only have a hard coded wait time on the step.  The recent change to default that to 30 seconds has helped, but it seems there must be a better way to deal with that time - it is tedious to update step by step if we find it is too short.  Again, we have radically different times based on the environemt.
ADMIN
Konstantin Petkov
Posted on: 25 Mar 2013 13:06 
Besides building two similar test lists with slightly changed settings, I would also suggest to consider wrapping some custom logic into an execution extension OnBeforeTestListStarted event and update the settings accordingly. It may look something like:

        public void OnBeforeTestListStarted(TestList list)
        {
            // add custom logic to determine the enrivonment
            // list.Settings.ElementWaitTimeout = 20;
        }
ADMIN
Konstantin Petkov
Posted on: 06 Mar 2013 08:54 
Isn't this request more about "timing profiles", e.g. ability to specify which settings the test to use depending on the environment to execute on? If so this is more about test list configurations. For example you create a test list A to run the tests configured with wait times X on one envorinment and also configure A to run with settings Y on another environment. That is exactly the purpose of the test list settings. Does that work for you or are you missing specific settings exposed for the test lists?
Create an account Log In
View
Type
Status