Friday, January 30, 2009

Team System Interesting Finds

Monday, January 26, 2009

Application Lifecycle Management Briefings / SDLC in a Box

I'll be presenting VSTS/TFS 2008 at this two day event Feb. 4-5th.

Alexei Govorine, Quick Solutions
Jeff Hunsaker, Cardinal Solutions
They are the co-founders of the Central Ohio ALM Group

The SDLC in a Box session will be led by two Central Ohio community leads. This 2 day briefing will discuss an application lifecycle project, from initial conception through requirements gathering, design, development, testing, build & review processes. We also cover process concepts, integration with non-Microsoft development and best-of-breed partner solutions & offerings for Visual Studio 2008 Team System.

This two day sesions is targeted for Developers, Architects, Project Managers, DBAs and Business Analysts looking for ALM and researching Team Foundation Server.

Register for this Event! Enter code: 857100

This event will be held at:
8800 Lyra Drive
Suite 400
Columbus, OH 43240 Map IT!

Friday, January 23, 2009

MDC Detroit: Introducing jQuery in ASP.Net

Update (2/7/2009): VsDoc for jQuery v1.3.1 released!

Update (1/23/2009): Thanks to all who attended! The packed house made for some great energy...and I hope some solid learning. I added the link to the samples/demos below (all the way at the bottom).

My colleague Jason Karns and I have the honor of presenting "Introducing jQuery in ASP.Net" at the Detroit MSDN Developer Conference on January 22nd. Come see this exciting inclusion of an open source library with Microsoft Visual Studio! I've included several links below we'll discuss in our talk:


Sunday, January 11, 2009

CodeMash: 2009

Another amazing CodeMash this year. I'm a third year alum now and it just keeps getting better. I embraced Open Spaces more this year. Along with that and the Microsoft Hands on Labs, there was never a dull moment. Most importantly, I got to hang with all the amazing folks who contribute so much to the community/region...and wow can Dustin Campbell and Carl Franklin *jam* guitar (...the real ones...not Rock Band)!

Huge props to Jim Holmes, Brian Prince, Jeff Blankenburg, Jason Follas, Jason Gilmore, Josh Holmes, tons of people I missed and all the great speakers and sponsors (including my employer, Cardinal Solutions).

Can't wait until next year!

Wednesday, January 07, 2009

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:


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