This is a migrated thread and some comments may be shown as answers.

Data-Driven Test Flow Control

1 Answer 101 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Val
Top achievements
Rank 1
Val asked on 02 Oct 2010, 07:41 AM
Hi - I understand how to connect data to test case fields, but have a test case that requires flow control customization that I'd like some help on.

Test Case Pseudo Steps
1. Navigate to app search page under test
2. Enter Login/Password
3. Select Simple Search button
4. Nav to text box 1 - enter search param 1 - data-driven record 1/col 1
5. Nav to text box 2 - enter search param 2- data-driven record 1/col 2
6. Nav to text box 3 - enter search param 3 - data-driven record 1/col 3
7. Click search button to present results
8. Verify/log search results
9. Select Simple Search button
10. same as #4-8 above but using record 2/col 1, 2, 3
... Continue until end of data set is reached

For the test case above, how do you customize the recorded steps to iterate steps 4-9 for each record in your data file?  Simply binding the text box fields in the recorded steps to the data file doesn't trigger the search, verification, and simple search buttons. 

Thanks in advance for your help/suggestions.

1 Answer, 1 is accepted

Sort by
0
Cody
Telerik team
answered on 05 Oct 2010, 12:22 AM
Hi Val,

In case you don't already have it, I have attached a document that goes into detail on how to do data driven testing with WebUI Test Studio.

Your scenario is actually fairly common in data driven scenarios. What you can do is split up your test into a couple of modules:

  1. Test A performs the login. This test is not data driven and will run just once.
  2. Test B is data bound to your data source and performs the searching. It assumes you're already logged on. It runs all steps for n number of times (the number of rows in the data source)
  3. Teat A calls Test B using Test-as-a-step.
  4. You run just Test A to run everything. You don't select and run Test B by itself.
The end result is that Test A will run only once while Test B will run n times. Did I explain that clearly enough?

Sincerely yours,
Cody
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Tags
General Discussions
Asked by
Val
Top achievements
Rank 1
Answers by
Cody
Telerik team
Share this question
or