During a client demo this afternoon, I mind-blanked on creating a data-driven web test. Sure enough, I stepped out of the client offices and figured it out. Super. But, I think it's counterintuitive enough to outline in a blog post (...trying to make myself feel better ;-). Somewhat in my defense, I was thinking about data-driven unit tests. These, IMO, are easy to implement. Data-driven web tests are a bit more effort and challenging.
Create a web test: Right-mouse on your test project selecting Add >> Web Test. Use the browser recorder to capture your web test scenario. Let's assume you're submitting an age and credit rating to an insurance rate calculator...similar to the screen capture below:
Create a table or CSV file (comma-delimited...just use Excel and save as CSV) with relevant headings for your inputs and expected values:
From Solution Explorer, double-click on your web test. In the main window, right-mouse on your web test selecting Add Data Source... :
Establish a connection to a relational database, CSV or XML file:
For each parameter posted, select Properties and then the drop-down next to the Value property:
For each of the post parameters, select the appropriate / associated data element:
Ok, so that covers our inputs. Now we need to verify the page produces the expected result. Right-mouse on the URL/page request including the form post selecting "Add A Validation Rule..."
Use the best option for your situation. Hopefully you can simply check a Form Field. In our circumstance, we're writing out an ASP.Net label to the form with the calculated results. So, we need to leverage the Find Text option (I tried Required Attribute Value but since labels output as <span id="lblSomething">Output Value</span> I wasn't able to grab the value...because it's an element vs. an attribute). Unfortunately, there's no nice drop-down for connecting to the data source's expected value. You'll need to enter it manually. The format looks like: {{DataSourceName.FileName#csv.FieldName}}. It's easiest just to copy from the input parameters and surround with the double curly brackets. Here's what the dialog looks like:
Finally, we need to instruct the test to execute once for every data record instead of the web test values captured in the recording. Within Visual Studio, select Test >> Edit Test Run Configuration >> Local Test Run:
Select Web Test from the left and select the "One run per data source row" option and click Close (save to the project if prompted):
Now we can execute our data-driven web test! (Make sure to check the Details tab confirming the Validation worked as expected and you're not experiencing a false positive):
Comments
I want to thank you to post this article. its a very informative for me.
Thanks and Regards,
Najam
It's really very helpful for the beginners like me.
Thanks,
Nirmala
Thanks for the post, very helpful. One question: I want to do the same thing for a coded UI test that I have previously recorded, how can I do this ?
Thanks for the post, very helpful. One question: I want to do the same thing for a coded UI test that I have previously recorded, how can I do this ?