Skip to main content

VSTS 2008 Data-Driven Web Test

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:

image

Create a table or CSV file (comma-delimited...just use Excel and save as CSV) with relevant headings for your inputs and expected values:

image

From Solution Explorer, double-click on your web test. In the main window, right-mouse on your web test selecting Add Data Source... :

image

Establish a connection to a relational database, CSV or XML file:

image

For each parameter posted, select Properties and then the drop-down next to the Value property:

image

For each of the post parameters, select the appropriate / associated data element:

image

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..."

image

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:

image

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:

image

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):

image

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):

image

Comments

Najam said…
Hi,

I want to thank you to post this article. its a very informative for me.

Thanks and Regards,
Najam
Anonymous said…
Hi

It's really very helpful for the beginners like me.

Thanks,
Nirmala
Anonymous said…
This Information is really very good to implement for my Project
Juan Trujillo said…
Hi Jeff,

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 ?
Juan Trujillo said…
Hi Jeff,

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 ?

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Configuring a Development Sandbox for the Azure CTP

I'm getting up to speed on Azure and the other cloud SDKs and need to configure an environment for development, demos and learning. My experiences... First off, if you've read my blog, you know I haven't installed non-productivity software on my core OS for years . Further, I don't get the warm and fuzzies installing CTP software on my core OS. I also love the recoverability and start-over-from-a-checkpoint features of virtualization. Virtual PC (VPC) houses all my development, demo and learning sandbox instances. So, let's start off with a VPC instance. For this to work well, ideally, you need a good 4GB of memory. Further to the ideal, you're running x64 so as to have access to the full 4GB of memory. ACQUIRE AN AZURE SERVICES DEVELOPER KEY To develop against Azure and/or .Net Services and SQL Services, you need an invitation code. Oooh, very exclusive. Pretty people to the front of the line! You can start the process here . If you run into problems, che