What is the best practice to do keyword driven testing in test studio?
My first thought was to create many different small fragmented tests which together can be put into a larger test. For example a test for "login" another for "open order registration" "add..." "close..." etc
Then in the test list i would add all the tests in the order i want them to create the complete test.
But it seems to me now that each test i run in the test list should be complete itself, and i instead should "import" other tests into that complete test with "test as step".
Is that correct? If that is the case why would i have severel different tests in a test list?
3 Answers, 1 is accepted
Thank you for your interest in Test Studio.
If test in a test list depends on a previous one (for example - when the browser is closed the login session is lost) there is a simple solution. Try to open the test list settings and set in the Web tab - RecycleBrowser option enabled. It will not close the browser instance from the previous run and next test will be executed there.
I hope this answers to your question.
Regards,
Nikolay Petrov
Telerik by Progress
Rank 1
But I am creating a WPF test. So it seems my best bet it to make smaller parts of test and then create a test that has all the smaller parts put together via creating "test as step"
Then run that test in a test list
Like the attached screenshot
In case of WPF automation to keep the application open on each test run the approach you found is the only one available. When using test as step all test included in the active test would be executed in same instance of the app.
I hope this answers to your question.
Kind Regards,
Nikolay Petrov
Telerik by Progress