Hello,
I am working on simplifying a number of tests for my employer; the old tests are large and cumbersome and our intention is to create small atomic tests.
I am curious how Telerik suggests to perform a test such as 'add user' without relying on a 'login' test to navigate to the desired page.
We do not wish to test more than one funtion per test, it seems to me that navigation, verification, or even login and verification tests used as your early steps make this test anything but atomic.
thank you
I am working on simplifying a number of tests for my employer; the old tests are large and cumbersome and our intention is to create small atomic tests.
I am curious how Telerik suggests to perform a test such as 'add user' without relying on a 'login' test to navigate to the desired page.
We do not wish to test more than one funtion per test, it seems to me that navigation, verification, or even login and verification tests used as your early steps make this test anything but atomic.
thank you
3 Answers, 1 is accepted
0
Hello Parker,
I am curious how Telerik suggests to perform a test such as 'add user' without relying on a 'login' test to navigate to the desired page.
What does "without relying on a 'login' test" really mean? Any Test Studio test must start by launching the browser, then most applications need to login. I expect that any sort of "add user" test will have to go through login and navigate to the desired page before it can perform the core of the test. You're not expecting or asking how the test can work w/o logging in, right?
We officially recommend that you take advantage of our Test as Step feature to make them modular (login would be your first subtest) and design your main tests so that they are independent and can run in any order. That way you can also take advantage of our Distributed Tests feature that is part of our Scheduler Server. Then you will have multiple tests running in parallel (one test at a time on each machine). You will see a significant time in test execution this way, and still be able to modularize and parameterize your modules.
Regards,
Cody
Telerik
I am curious how Telerik suggests to perform a test such as 'add user' without relying on a 'login' test to navigate to the desired page.
What does "without relying on a 'login' test" really mean? Any Test Studio test must start by launching the browser, then most applications need to login. I expect that any sort of "add user" test will have to go through login and navigate to the desired page before it can perform the core of the test. You're not expecting or asking how the test can work w/o logging in, right?
We officially recommend that you take advantage of our Test as Step feature to make them modular (login would be your first subtest) and design your main tests so that they are independent and can run in any order. That way you can also take advantage of our Distributed Tests feature that is part of our Scheduler Server. Then you will have multiple tests running in parallel (one test at a time on each machine). You will see a significant time in test execution this way, and still be able to modularize and parameterize your modules.
Regards,
Cody
Telerik
0
Parker
Top achievements
Rank 1
Rank 1
answered on 08 Mar 2014, 12:36 AM
Hi Cody,
This is what we have been doing.. tests that occurred further into the application would be navigated to by running small tests (login, click users...continue on) But we have been trying to find ways to being more atomic in our testing.
For example a login failure fails all of our tests, and true atomicity would mean each test can only break one way.. on the intended feature that is in fact failing.
I have discussed this with some other professionals, they use a hook in some cases for login.
I will continue to investigate this. Thank you
This is what we have been doing.. tests that occurred further into the application would be navigated to by running small tests (login, click users...continue on) But we have been trying to find ways to being more atomic in our testing.
For example a login failure fails all of our tests, and true atomicity would mean each test can only break one way.. on the intended feature that is in fact failing.
I have discussed this with some other professionals, they use a hook in some cases for login.
I will continue to investigate this. Thank you
0
Hello Parker,
Have you learned about our "Stop Test List on Failure" feature? I would turn this on for common subtests, such as Login, where if that test fails everything is going to fail.
Regards,
Cody
Telerik
Have you learned about our "Stop Test List on Failure" feature? I would turn this on for common subtests, such as Login, where if that test fails everything is going to fail.
Regards,
Cody
Telerik