Indy TFS Meeting - Lap Around VSTS 2010 Presented by Paul Hacker (Indianapolis)

This month Paul will be talking about many of the new features of Visual Studio 2010.  The meeting will be from 8:00-9:00 PM Thursday December 11th 2008 immediately following IndyNDA.

The Gene B. Glick
Junior Achievement
Education Center
7435 North Keystone Ave
Indianapolis, IN 46240

Map and Directions

Paul is a Principle Consultant at Polaris Solutions, LLC in Indianapolis, with a passion for Team System. He has been working with the product since mid-2005. Paul has implemented Team System/TFS in numerous organizations. When not spending time with his family, you can find him presiding over the Indianapolis TFS SIG, Podcasting on Radio TFS, or writing tools to enhance Team System.

Dallas VSTS Users Group November 19th

Join the Dallas VSTS Usergroup next Wednesday evening, November 19 @ 18:00, for a presentation by Ed Blankenship.  Ed will be going over the new October release of the Team Foundation Server 2008 Power Tools as well as the new features coming in VSTS 2010.  If you weren’t able to make it to PDC this year and you have yet to check out the presentation videos on Channel 9 (see links to the right), you will want to be at this meeting!

Ed is the Release Engineering Manager at Infragistics and a Microsoft Visual Studio Team System MVP.  He is also a technical evangelist for Smart Client applications (primarily Windows Forms & Windows Presentation Foundation.)

Ed has been a technical editor for the Wrox Silverlight 1.0, Silverlight 2.0 Developer's Guide, and Silverlight 2.0 Bible books, author of numerous articles, and has spoken at various user groups, events, and conferences.  He is a resident of Dallas, Texas and also a graduate of Midwestern State University in Wichita Falls, Texas.

This meeting will be held Microsoft office in Las Colinas (7000 State Highway 161, Irving, TX 75039.)  Visit our home page for directions and please remember the $2 entry fee.  To RSVP, please email me at omar_villarreal@yahoo.com.

NOTE: Please add noreply@dallasvsts.com to your email system so our emails are not caught by the Junk email filters.

Seattle Code Camp November 15-16, 2008 w Two full days of VSTS Content

For those of you looking for something to do this weekend; Seattle code camp will have two full days of VSTS content and will be going on in Redmond at Digi Pen. 5001-150th Ave. N.E. Redmond, WA U.S.A. 98052.  Unfortunately I will only be there Sunday but if you want to catch up drop me a line Chass@Microsoft.com

 

Day 1 - Saturday, November 15^th

 

1:15pm
to
2:30pm

Writing WCF with TDD

WCF is a great technology for writing rich and extensible services. It does present some challenges for working with Test Driven Development. This session will code a WCF service and client using Test First Development practices with the red/green/refactor pattern.
Track: General
Speaker: David Starr

2:45pm
to
4:00pm

Pex - Automated White box Testing for .Net

Pex is a tool that analyses code at runtime in a similar fashion to what we usually refer as 'white box' testing: Pex tries to cover every reachable branch in the program. As a side effect, it also tries to 'break' every assertions, and thus, find what we call bugs. Check out how you can use Pex get started from a single click or discover the power of parameterized unit tests.

NOTE: This was the highest rated Session at PDC AND the highest attended session of the internal VSTS MVP/Insiders presentations.

Speaker: Peli

Peli de Halleux is a Research Software Developer Engineer in the Foundations of Software Engineering Group in Redmond. Peli is working on Pex (http://research.microsoft.com/pex), and created the infamous MbUnit. Peli joined the Foundations for Software Engineering in October 2006. Peli worked in the CLR as a SDET in charge of the Just In Time compiler (2004-2006). Before joining Microsoft, Peli earned a PhD in Applied Mathematics from the Catholic University of Louvain (2000-2004).
Email: jhalleux@microsoft.com

4:15pm
to
5:30pm

Agile Estimation Techniques

Is your manager inaccurately estimate your work in man hours to the PMO? Want to show them a different and more accurate way to do planning? We'll discuss the fundamental importance accurate estimating and planning has on successful projects and attendees get a chance to actually practice the techniques in the session. Go back to work Monday with a new technique in your pocket that can fundamentally improve your team's effectiveness.
Track: General
Speaker: David Starr

4:15pm
to
5:30pm

How to get better Coding Standards and Code Review from VSTS

There's some good stuff in VSTS for coding standards and code review, but how can you use it, and more importantly how can you make it better? In this session I will share my experience of successfully extending and customizing VSTS simultaneously in the open source community and at the enterprise level to get better code by automating the most important code standards and creating more valuable code reviews. Experience, an adoption/implementation plan, and code will be shared.
Track: General
Speaker: JB Brown

Day 2 - Sunday, November 16^th

9:00am
to
10:15am

A Quick Lap Around Team System 2010

Microsoft has finally announced the name of the new version of Visual Studio! In this session I will provide an overview of the new features of Visual Studio Team System 2010. This session will include the new Architecture SKU, Development features (Aftershock and Proteus) and testing using the new Camano UI. This session is meant to whet your appetite for the new features of Team System 2010. I'll also be giving some dedicated sessions for some of the new features such as the Architecture and Testing SKU's.
Track: General
Speaker: Jeff Levinson

 

10:30am
to
11:45am

Team System 2010 Architecture

This session focuses on the new UML tools available in the Team System 2010 Architecture SKU. We'll take a look at the Use Case, Sequence, Component, Layered and Activity diagrams and discuss how they can be used practically in your daily environment.
Track: General
Speaker: Jeff Levinson

1:15pm
to
2:30pm

Testing with Team System 2010 Test

The new testing tools in the next version of Team System finally bring Team System in line as a viable professional testing tool. Learn how to manage, record, playback and track tests as well as create coded tests from manual tests. You will see how to use Camano and how Camano ties into Team Explorer via work items.
Track: General
Speaker: Jeff Levinson

2:45pm
to
4:00pm

Integrating WiX into your Automated Build

WiX is an easy to use, XML based software packaging technology used to create powerful install / uninstall packages. In this session, I'll introduce WiX, show off some of the common tools, create a basic WiX package, extend it to include a UI, and wrap it all up so that it runs nicely during an automated build in Team Build.
Track: General
Speaker: Steven Borg

Team Test Special Interest group November 17 (Redmond Wa)

The next Team Test Special Interest group will take place on Monday November 17 from 3-5:00PM in the Quinault room in Microsoft Building 34 (map). This session promises to be quite exciting as for the first time we will be able to talk publically about lab management, which was just announced as a new offering in Team System 2010 yesterday.   In addition, we are very excited to have Jeff Levinson of Northwest Cadence present some practical tips on making use of metrics to improve software quality.  A description of his presentation is as follows:

Much of process improvement revolves around eliminating inefficiencies in the process. One key way to do this is through the use of test case management. For example, what answer does your developer give you when asked, “How do you know when you’re done coding?” The answer is usually “I don’t” which is not a good answer. This presentation shows how to address issues like this and how to reduce the overall time it takes to handle virtually any development task – and it all revolves around a smart testing process.             

Agenda:

1. Jeff Levinson talk on Practical Process Management

2. Ram Cherala Overview of Lab Management

3. Michael Rigler Overview of Requirement based testing with Camano

 

Please reply to vsttsig@microsoft.com if you are planning to attend

Code Camp Raleigh this weekend

Special Event

CodeCampRDU Fall '08
Saturday November 15, 2008
Register now! *Registration is required for this event
We have an unbelievable day full of developer content. There will be over 30 sessions led by some of the best and brightest community speakers. There will also be an Open Spaces area, for developers to drive their own discussions on relevant topics.
Schedule: view it... download it...
Presentations: get details...
Agenda
7:30 - Doors open
7:31 - Coffee and bagels
8:15 - Keynote - Karl Shifflett
9:15 - Sessions 1, 2
12:00 - Lunch
1:20 - Sessions 3, 4, 5
5:00 - Closing / Prize Drawings
* Spread the word: Remind any co-workers that haven't registered on the TRINUG site to do so now!

Location:
ECPI College of Technology
4101 Doie Cope Rd
Raleigh, NC 27613

Custom Errors being ignored in ASP.net

 

In playing with custom errors i found even though i set the <customerrors> and debug section in my web.config like those below

<compilation debug="false"/>

<customErrors defaultRedirect="GenericErrorPage.htm">
        <error statusCode="403" redirect="NoAccess.htm"/>
        <error statusCode="404" redirect="~/myerror.htm"/>
    </customErrors>

I found these settings were still getting ignored until i set the retail flag in the Machine.config.

    <system.web>
    <deployment retail="true"/>

</system.web>

…now i don’t know if this is a change with the .NET framework in Windows Server 2008 -or i had forgotten i had done this in the past but it is working this way now.

Free Seminar on Software Testing (Washington)

 

Implementing and Creating an Effective Test Strategy with Microsoft Visual Studio Team System

Today, identifying potential issues in the software development lifecycle early is critical to establishing a rhythm of verifying quality early and often. Implementing good software testing practices can lead to cost and resource savings and can be adopted by teams of all sizes. In planning your testing initiative, there are some key questions to ask and strategies to define Test Best Practices for your organization.

Please join Microsoft and Testhouse (Microsoft Visual Studio Team System Inner Circle Partner) for this half-day seminar. Doug Hoffman, American Society for Quality Fellow, Testhouse will provide an overview on how to create and implement an effective test strategy. In addition, senior members of the Microsoft Visual Studio Test Team will lead the discussions on the topics of test case management, tools in Visual Studio 2008, and provide a brief overview of what’s to come in the next version of Visual Studio 2010.

TARGET AUDIENCE

This seminar is intended for Quality Assurance Managers responsible for implementing testing in organizations. Presentation will provide an educational overview of testing strategy; it is not a deep dive technical presentation on software testing.

AGENDA

09:00 AM    Introduction

09:15 AM    "Best Practice" - Defining the Concept, Doug Hoffman, Testhouse

09:30 AM    Testing Technology & Interest, Doug Hoffman, Testhouse

10:30 AM    Test Management Leadership, Doug Hoffman, Testhouse

10:45 AM    Break

11:00 AM    Visual Studio Team Test Tools, Microsoft Visual Studio Test Team

12:00 PM    Raffle & Close

DATE, TIME & LOCATION

Thursday, November 13, 2008

Registration: 08:30 AM, Event: 09:00 AM-12:00 PM

Microsoft Corporation

Civica Office Building

205 108th Ave. NE, Suite 400

Bellevue, WA 98004

Phone: 425.705.1900

REGISTER

To register, please click on the link below or call 1.877.MSEVENT (1.877.673.8368).

Registration Link: http://msevents.microsoft.com/cui/EventDetail.aspx?culture=en-US&EventID=1032393301

Event ID: 1032393301

SPEAKER BIO

Douglas Hoffman, MBA, MSEE, BACS, ASQ Fellow
Test House | www.testhouse.net

Douglas Hoffman has over 20 years on experience in the Industry.  From Strategic and tactical planning for software quality, through to test automation architectural design and selection and deployment of software tools. A regular speaker at national and international conferences and seminars within the Software Testing field. He has taught many Management and QA courses, published many articles and has ground breaking work based on his implementation and design on Test Automation.

Great Community Created Walk Through for Visual Studio 2010

After you work your way through a walk through our VSTS Updated CTP VSTS Walk throughs make sure and check out

Loic BAUMANN Working through the Source Control of the October CTP

Visual Studio Team System 2010 Test Features walk through with screen shots.

 

Walking through the some of the Test Features of Microsoft Visual Studio Team System 2010 Community Technology Preview that can be download at:

Visual Studio 2010 and .NET Framework 4.0 CTP

The information contained in this post is a work in progress update to the overall Visual Studio Team System 2010 walk through which can be found at:

Updated CTP VSTS Walk throughs

This walk through will focus on how you can plan, design, develop, and test an application by using the Microsoft Visual Studio Team System 2010 Community Technology Preview

October 2008

Introduction

Walkthrough: Creating Manual Test Cases and Adding to a Test Suite

This walkthrough guides you through the process for creating manual test cases and adding a test case to a test suite. In this scenario, Lucerne Publishing wants to add another test to the DinnerNow.net payment system. You have to add an end to end test for the purchasing scenario.

Suppose that you work on Lucerne team and have the task of testing the payment system for Iteration 2. First, you will create a manual test for this. You will add the steps to this test case and the expected results. Then you will add it to the existing test suite for the integrated payment system.

In this walkthrough, you complete the following tasks:

· Add a test case to an existing test suite.

· Add test steps to a manual test case.

Overall, performing these tasks will help you create and organize the tests for testing your application.

Before you begin this walkthrough, complete the following prerequisites:

To fulfill the walkthrough prerequisites

1. Follow these steps to open the new tool for generalist testers, Microsoft "Code Name Camano" for Visual Studio Team Test 2010 CTP:

2. To display the Microsoft "Code Name Camano" window, click Start, and then point to All Programs.

3. Point to Microsoft Visual Studio 2010 and then click Microsoft Code Name Camano.

4. To connect to a team project, point to Home, click the down arrow, and then click Connect to a Team Project.

5. To add a new Team Foundation Server, click Add.

6. The Add Team Foundation Server dialog box is displayed.

7. Type localhost, and then click Add.

8. To select the team project, click the name of the team project, DinnerNow, in the list. Then click Connect.

9. If you successfully connect to this team project, the name of the team project is displayed in the Microsoft "Code Name Camano" window following Team Project.

Add Test Case to an Existing Test Suite

You can manage your test cases by organizing tests into test suites. You use a test suite to group test cases together. For example, you can group all test cases for a specific feature together. By grouping them in a test suite, you can now easily run all the tests in the test suite together. Test suites also help in planning your testing effort by working with this logical grouping of test cases.

To add a test case to an existing test suite

1. To display the Planning Activities Center, click Planning.

2. To display all the test suites, click Test Suite Manager in the Planning Activities sidebar.

3. To select the test suite, click End to End Test.

The tests that have already been added to the test suite are displayed in the test suite details panel.

Note   There is a prebuilt test case that you can use instead of creating a test case yourself called Prebuilt: Complete Purchase Scenario.

4. To add a test, click New test case in the toolbar for the test suite details panel.

The new test case is displayed in the main editing pane of Microsoft "Code Name Camano" titled New Test Case 1*:.

5. To name the test case, type Complete Purchase Scenario in Title.

You use this title to identify the test case and search for it if you have to.

6. Check Area shows DinnerNow.

7. Click Owner to select Ellen Adams for the test case.

8. Click Priority to select 1 for the importance of the test case.

9. To save the test case, click the save icon in the toolbar.

Note   After the test case has been saved, the test case identifier is shown in the title of the editing pane.

Add Test Steps to a Manual Test Case

A test step might be an action only, or it might include validation.

To add test steps to a manual test case

1. Click Steps.

2. Click <click here to add a step>, type Verify that DinnerNow Web application is started as the Action for the first test step, and press Enter.

3. Type Enter 98101 in the Your Zip field as the Action for the next step.

4. Type Select American as the food type in the combo box as the Action for the next step.

1. Type Select Dinner as the meal of choice as the Action for the next step.

2. Type Select 1 hour as the time frame as the Action for the next step.

3. Type Click Find as the Action for the next step.

4. In the Expected Result column, type Check 3 restaurants are displayed: TailSpin BBQ, SouthRidge Subs, Northwind Bar and Grill.

a. Note   If you type a value in the Expected Result column, the step is automatically set to a validation step, as indicated by the check mark icon.

5. Type Select Northwind Bar and Grill as the Action for the next step, and then type 12 items should be displayed as the Expected Result.

6. Type Select Classic Burger and Ice cream from the menu list as the Action for the next step, and then type Your menu today has a cost of $27 as the Expected Result.

7. Type Click Testimonials at the top of the screen as the Action for the next step, and then type Positive reviews are displayed for Northwind Bar and Grill as the Expected Result.

8. Type Click Checkout as the Action for the next step.

9. Type Select sign in using InfoCard as the Action for the next step.

10. Type Select Brad Sutton and click Send as the Action for the next step.

11. Type Click the radio button (Work) for Choose Delivery Address as the Action for the next step.

12. Type Click the radio button (Visa) for payment option as the Action for the next step.

13. Type Confirm Order as the Action for the next step, and then type Check Total is $27, Delivery address is 1 Microsoft Way, and Payment Option is Visa as the Expected Result.

14. Type Click Bring my Meal as the final test step.

a. Note   You can mark any test step as a validation test step when you click Toggle Step Validation in the Steps Toolbar. When you run the test case, you must individually mark a validation test step as either passed or failed.

15. To save and close this test case, click Save and Close.

16. Important   If you do not close the test case and continue to a different activity, the test case is now shown in Work in Progress in the sidebar. Click this test case to open it again.

Walkthrough: Connecting Test Cases to User Stories

This walkthrough guides you through the process for connecting existing test cases to user stories. In this scenario, Lucerne Publishing wants to be able to view which test cases will test which user stories for the DinnerNow.net payment system. This lets Lucerne publishing know the level of test coverage for each user story.

Suppose that you are a test lead at Lucerne Publishing. You want to link the existing manual test to the user story to check that the reviews are displayed for a restaurant because the test also covers this functionality.

In this walkthrough, you complete the following task:

Link Existing Test Case to a User Story

Link Existing Test Cases to a User Story

To link existing test cases to a user story

1. To display the Planning Activities Center, click Planning.

2. In the Requirements pane, double-click the requirement Customer Finds Reviews for Restaurant that you want to link to your test case.

The requirement is displayed.

3.

4. Select the Test Cases tab.

5. To find the test cases, click Add.

The Add Link to User Story dialog box is displayed.

6.

7. To find the test cases that you want to link to the requirement, click Browse to select a query to use.

The Choose linked work items dialog box is displayed

8. Select the following query: Team Queries/Open Test Cases, and then click Find.

The test cases in the query are displayed

9. Select the check box for the row that contains Complete Purchase Scenario.

10. To select to link these test cases to this requirement, click OK.

The Choose linked work items dialog box is no longer displayed

11. To add the links to this requirement, click Ok.

The links are now displayed.

12. To save the requirement, click Save and Close in the toolbar.

Walkthrough: Executing Manual Tests

This walkthrough guides you through the process for running manual test cases and creating a bug when you find an issue. This bug will contain details of the computer that you used to run the test, diagnostic events for the application under test, a video recording, an automation strip and an action log of each UI action that the tester performed. In this scenario, Lucerne Publishing is required to run the manual tests for the DinnerNow.net payment system.

Suppose that you are the test lead at Lucerne Publishing. You have determined that you must run the test in this test suite, End to End Test, on Vista with Internet Explorer 7 for Iteration 2. You also want to collect diagnostic events to provide a developer with more information to debug if you find a bug. You create test settings, DinnerNow with Diagnostic Trace Collector, to use for your test plan to collect this data. You now create a test plan, Test Plan for Iteration 2, for your team project using these test settings. Then you add a test run for this suite and configuration.

Now suppose that you are a tester; you will start to run the tests. You will run the individual steps in a test case. You will create an automation strip for each of your UI actions that can be played back the next time that you want to run this test. When you find that the actual results for a test step do not match the expected results for a validation step, you will create an actionable bug that includes the diagnostic events from running the application. Then, you will save the test results.

In this walkthrough, you complete the following tasks:

· Review the test plan and test settings for your test run

· Run a manual test, create a bug and save the test results

Overall, performing these tasks will help you understand how to use test plans, test settings, test configurations and run your manual tests, create any necessary bugs and save the test results.

Review the Test Plan and Test Settings for the Test Run

To review the test plan and test settings for the test run

1. To display the Planning Activities Center, click Planning.

2. Click Test Plan Manager in the Planning Activities sidebar.

3. To select the test plan, click Test Plan for Iteration 2 and then click Open.

The details of the test plan are displayed. You will see a test run End to End Test. This test run associates each test in the test suite, End to End Test, with the test configuration Vista and IE7. When a test from this test plan is run, the results will be associated with this test plan.

4. View the value for Test settings in the test plan information. This shows the test settings that will be used when any tests are run from this test plan.

5. To display the Testing Activities Center, click Testing. Then click Test Settings Manager in the Testing Activities sidebar.

6. To select the test settings, click DinnerNow with Diagnostic Trace Collector and then click Open.

The details of the test settings are displayed.

7. Click Data and Diagnostics to view what data you want to collect, or the actions to perform on a system for each role.

8. Click Cancel to close the test settings.

9. Close the Test Settings Manager.

Run a Manual Test, Create a Bug, and Save the Results

Now that you have created a test plan that contains a test run, you can run any one of the manual test cases in this test run and create a bug if you find one. You can then save the test results from running the test case.

To run the manual test case, create a bug, and save the results

1. To display the tests that are ready to run, click Testing Overview in the Testing Activities sidebar.

2.

3. In the left pane under Test Plans in Progress, expand the test plan Test Plan for Iteration 2 to show its test runs.

4. Under Test Plan for Iteration 2, click End to End Test.

The right pane displays the test cases in the selected test run.

5.

6. In the right pane, click the test case Complete Purchase Scenario.

7. Click Run.

The Microsoft Test Runner opens.

The Test Cases panel displays the name of the test case. The test case, Complete Purchase Scenario, is selected. Its test steps are displayed in the Test Steps panel.

8. To dock the Microsoft Test Runner on the left, click the arrow next to the View icon and point to Dock Left.

9. To start the DinnerNow.Net application, double click the DinnerNow Web icon on the desktop.

10. To run the manual test case and create an automation strip at the same time, click Test and Automate.

Note   The automation strip can be used for future playback of the test case. Also it can be used to create a coded UI test using the automation strip to generate code.

The Recording Settings dialog box is displayed. If it does not appear, click Test and Automate again.

11. Under Select recording types to capture, the three types of recordings that you want to be captured when you run the test case should be automatically selected.

· Action. This choice records information to a log file when you test. It writes text to describe the UI actions that you perform for each test step when you run the test.

· Background. This choice records the actions that you perform in the application under test. When you play back this recording, the actions are performed again in the application under test. This recording is known as an automation strip.

· Video. This choice creates a video recording of the desktop while you run the test.

12. Under Select applications under test, select DinnerNow.net – Windows Internet Explorer, and then click OK.

13. Important   Wait until the counter in the Test Steps pane begins, the Test Steps header changes to blue, and a marker for the automation strip is displayed. The text End Test Case is enabled.

14. Perform the first step in the Complete Purchase Scenario test case: Verify that DinnerNow Web application is started.

Note   Under the Test Steps pane, the Properties pane is displayed. This pane shows details for the test case and the individual test steps. Click the Test Step Details tab on the Properties pane to show the current test step and any data associated with it. You can copy this data and use it in your application under test. You can collapse and expand the Properties pane as required.

15. Click the exclamation mark to the right of the test step to mark it as passed, or right-click the test step and then click Pass.

16. Run the next two steps and mark them as passed.

You can pass each step or pass multiple steps, passing each step provides improved granularity when you playback using the automation strip.

Note   To pause the test case at any time, click Pause.

17. Run the steps up to and including the testimonials step. When you click Testimonials, notice that the actual results do not match the expected results.

Note   Wait until the DinnerNow application completes each action. The performance may be slow using the Virtual PC image.

18.

19. Click the exclamation mark to the right of the test step to mark it as failed, or right-click the test step and then click Fail.

20. To take a screenshot to add to a bug, click the camera icon on the test steps toolbar, point to Rectangular Capture and drag an area for the screen shot.

21. To add a comment to this test step to add to the bug, click Test Step Results tab on the Properties pane. Then type Reviews are not displayed in Comments. (In the screenshot it actually says “Chuck’s Step step

22. To create a bug, click the Create New Bug icon on the Test Steps toolbar.

23. To give the bug a title, type Testimonials are not displayed in Title. (Screen Shot just says “Testimonial Bug”)

24. To see the test steps that are automatically added, click Details.

25. To see the input data and comments added, expand the test steps.

Note   You can edit these test steps and comments as needed.

26. To see the system information that is automatically added about the computer that you are using for the test, click System Info.

27. To see the log files that are automatically added, click Other Links. The action log, the automation strip, the diagnostic trace log, and the video recording are added.

28. To update the priority, click Priority.

29. To save the bug, click Save.

The id number for the bug is now displayed.

30. To close the bug dialog, click the close icon.

31. Click Resume Test Case.

32. Scroll to the last test step and then click End Test Case.

33. The test case is now marked as failed in the Test Cases panel.

As you chose to record the test case, the recording is automatically stopped and saved.

Important   It is required to mark a test step with a status if it is a validation test step. The overall result for a test case is based on the status for the test steps that were marked. If one test step is marked as failed, or it is not marked, then the test case will acquire a status of failed.

34. To save the test results, click Save and Close.

The Testing Activity Center is now displayed.

35. To view the saved test results and the linked files, double-click the test in the list of tests.

Note   When a test has been run, it is now considered not ready to be run. You can reset the test if you want to run it again when the bug is fixed.

36. Close the DinnerNow.Net application.

Walkthrough: Automating Test Cases with Coded UI Test

This walkthrough guides you through the process for automating test steps and adding validation for these steps using a Coded UI Test. In this scenario, Lucerne Publishing wants to automate the test that has been created for the DinnerNow.net payment system. For more information about the overall scenario, see Scenario Overview.

Suppose that you are a tester on the Lucerne Publishing team and you have the task of automating the test steps for the payment system in Iteration 2. You want to create an automated UI test which will let you record the test steps and generate code from this recording. You will add validation for your test to verify the expected results. In this walkthrough, you complete the following task:

· Create a coded UI test to automate a test case

Overall, performing this task will help you create an automated test which can be used for regression testing your application.

Create a coded UI test to automate a test case

To create a coded UI test and automate a test case

1. Open Visual Studio.

2. Click Test and then point to New Test...

The Add New Test dialog box is displayed.

3. To create a coded UI test, click Coded UI Test.

4. In the Add to Test Project dropdown, select Create a new Visual C# test project, then click OK.

The New Test Project dialog box is displayed.

5. Click Create.

The Coded UI Test dialog box is displayed.

6. To record your test steps and generate code to automate these steps, select Launch the recorder to generate code.

Visual Studio is minimized and the Test Recorder opens.

7. To start recording, click Record.

8. To start the DinnerNow.Net application, double-click the DinnerNow Web icon on the desktop.

9. Perform the following test steps using the DinnerNow.Net web site.

a. Type 98101 in Your Zip field.

b. Select American as the Food Type in the combo box.

c. Select Dinner as the meal of choice.

d. Select 1 hour as the time frame.

e. Click Find.

All these actions will be recorded by the Test Recorder and you can see them in the Recorded Actions section of the Test Recorder.

10. To use the Test Recorder to create the code for these test steps, click Generate Code.

The Enter Method Name dialog box is displayed.

11. To enter a name for the method for these test steps, type FindRestaurant in Enter Method Name and click OK.

12.

13. To use the Test Recorder to add validation, click Add Validation.

The UI Control Locator tool opens.

14. Drag the crosshair to the image representing Northwind Bar & Grill in the DinnerNow.Net web application. Release the crosshair when the image is highlighted with a blue rectangle.

15. To add the Northwind Bar & Grill Image to the UI control list, click Add in the Microsoft UI Control Locator.

16. To display the properties of the NorthWind Bar & Grill Image, click Done.

17. Click the checkbox next to Exists. On the same row select AreEqual in the Comparator column.

18. To add an assertion in the code to check that NorthWind Bar & Grill Image exists, click Generate Code.

19. Click Edit UI Controls to move to the UI Control Finder view.

20. Repeat steps 14 – 18 for Tailspin BBQ and Southridge Subs images.

21. Close Microsoft UI Control Locator by clicking on the close icon.

22. Close the Test Recorder by clicking on the close icon.

23.

24. Click on Test, point to Edit Test Run Configurations and click on Test Setttings. The Configuration Settings dialog opens up.

a. Click on Execution Criteria.

b. Scroll down to the Collectors section.

c. Uncheck the Enabled checkbox on Diagnostic Trace Collector.

d. Click Apply and then Close.

This step is a temporary workaround since the Diagnostic Trace Collector feature now conflicts with the running of Coded UI Test.

25. Right-click in the editor window for CodedUITestMethod1, and then click Run Tests.

This builds the test project with the coded UI test, and then runs the test. This will perform the test steps that you have created in this coded UI test.

The test results window displays the results for the coded UI test.

26. Right-click in the editor window for CodedUITestMethod1, select Edit Coded UI Test, then point to Record and Generate code to start the test recorder again.

Visual Studio Team System 2010 Videos

I was asked by one of my coworkers “What video’s do we have on VSTS 2010” –turns out mostly due to Brian Keller’s efforts – A LOT.

Below is the list i know about:

1. Announcing Visual Studio Team System 2010
2. Visual Studio Team System 2010 Week on Channel 9!
3. Cameron Skinner: Visual Studio Team System 2010 – Architecture
4. "Top-down" design with Visual Studio Team System 2010
5. "Bottom-up" Design with Visual Studio Team System 2010 Architect
6. ARCast.TV - Peter Provost on what’s coming for Architects in Visual Studio Team System
7. Team Foundation Server 2010 Setup and Administration
8. An early look at Team Foundation Build 2010 with Jim Lamb
9. Enterprise Team Foundation Server Management with Mario Rodriguez
10. Update on Team Foundation Server Migration and Synchronization
11. Microsoft Visual Studio Team System Database Edition: Overview
12. Improving .NET Application Performance and Scalability
13. Microsoft Visual Studio Team S…er: How We Use It at Microsoft
14. Team Foundation Server 2010 Setup and Administration
15. Microsoft Visual Studio Team System: Software Diagnostics and Quality for Services
16. Architecture without Big Design Up Front
17. Microsoft Visual Studio Team System: Leveraging Virtualization to Improve Code Quality with Team Lab
18. Branching and Merging Visualization with Team Foundation Server 2010
19. Brian Harry: Team Foundation Server 2010
20. Better Software Quality with Visual Studio Team System 2010
21. Manual Testing with Visual Studio Team System 2010
22. Historical Debugger and Test Impact Analysis in Visual Studio Team System 2010
23. What’s new in Visual Studio Team System 2010: Feature: Historical Debugger

 

TFS Sprint Review Videos

In the spirit of Channel9 included in this VPC are a small sampling of videos created as part of the Visual Studio Team System Development process.  In these videos the Program managers and Developers review their features in a series of (rough) ~2 minute videos at the end of each sprint.  Since the videos are narrated live in Real time they typically are not recorded with Audio.  As you would expect they are not holistic end to end view of the product but rather of specific features –often mid flight.  If you have any issues please email chass@microsoft.com

 

New work item controls in Team System Web Access

Hakan Eskici

In our internal sprint reviews we often have videos of new features - here is an example by Hakan Eskici showing New Rosario Work Item Controls in Team System Web Access.

Note most of our sprint review videos are NOT narrated.

http://mschnlnine.vo.llnwd.net/d1/ch9/7/4/0/5/2/4/TSWA New Work Item Controls.wmv

mms://mschnlnine.wmod.llnwd.net/a1809/d1/ch9/7/4/0/5/2/4/TSWA New Work Item Controls.wmv

New Bulk Edit  functionality in Team System Web Access

Hakan Eskici

In our internal sprint reviews we often have videos of new features - here is an example by Hakan Eskici showing new Rosario bulk edit functionality in Team System Web Access.

Note most of our sprint review videos are NOT narrated.

http://mschnlnine.vo.llnwd.net/d1/ch9/7/5/0/5/2/4/TSWA Bulk Edit.wmv

mms://mschnlnine.wmod.llnwd.net/a1809/d1/ch9/7/5/0/5/2/4/TSWA Bulk Edit.wmv

New Querying experience in Team Foundation Server code named Rosario

Siddharth Bhatia

In our internal sprint reviews we often have videos of new features - here is an example by Siddharth Bhatia showing the new Querying experience in Team Foundation Server code named Rosario.

Note most of our sprint review videos are NOT narrated but in this particular video Siddarth managed to convince a couple of Robots to complete this task for him.

http://mschnlnine.vo.llnwd.net/d1/ch9/5/7/0/5/2/4/Query UX.wmv

mms://mschnlnine.vo.llnwd.net/d1/ch9/5/7/0/5/2/4/Query%20UX.wmv

The new Team Foundation Server 'simple' install wizard and MMC admin console for Team Foundation Server code named Rosario

Ed Holloway

In our internal sprint reviews we often have videos of new features - here is an example by Ed Holloway showing the new 'simple' install wizard where he installs and configures a TFS Server and the new MMC admin console for Team Foundation Server code named Rosario – specifically the process for creating a Team Project collection.

Note most of our sprint review videos are NOT narrated.

http://mschnlnine.vo.llnwd.net/d1/ch9/4/8/0/5/2/4/AO Phase 2 Install Demo.wmv

mms://mschnlnine.wmod.llnwd.net/a1809/d1/ch9/4/8/0/5/2/4/AO Phase 2 Install Demo.wmv

Stateless Mode in Team System Web Access

Hakan Eskici

In our internal sprint reviews we often have videos of new features - here is an example by Hakan Eskici showing the new Rosario Stateless Mode in Team System Web Access.

While most of our sprint review videos are NOT narrated this video does have nice call outs that describe what is happening- and in which version.

http://mschnlnine.vo.llnwd.net/d1/ch9/4/6/0/5/2/4/TSWA Stateless Mode.wmv

mms://mschnlnine.wmod.llnwd.net/a1809/d1/ch9/4/6/0/5/2/4/TSWA Stateless Mode.wmv

QueryResults WebPart  in Team System Project Site

Hakan Eskici

In our internal sprint reviews we often have videos of new features - here is an example by Hakan Eskici showing new Rosario QueryResults WebPart in Team System Project Site.

Note most of our sprint review videos are NOT narrated.

http://mschnlnine.vo.llnwd.net/d1/ch9/9/6/0/5/2/4/TSWA QueryResults WebPart.wmv

mms://mschnlnine.wmod.llnwd.net/a1809/d1/ch9/9/6/0/5/2/4/TSWA QueryResults WebPart.wmv

Team Foundation Server code named Rosario: Persisting Formulas and Formats In Excel Demo

John Nierenberg

In our internal sprint reviews we often have videos of new features - here is an example by John Nierenberg for Team Foundation Server code name Rosario Persisting Formulas and Formats In Excel Demo

http://mschnlnine.vo.llnwd.net/d1/ch9/1/3/1/2/2/4/Persisting Formulas and Formats In Excel.wmv

mms://mschnlnine.wmod.llnwd.net/a1809/d1/ch9/1/3/1/2/2/4/Persisting Formulas and Formats In Excel.wmv

Project Server Integration with Team Foundation Server code named Rosario

Ameya Bhatawdekar

In our internal sprint reviews the we often have video of features - here is on example by Ameya Bhatawdekar for Team Foundation Server code named Rosario Project Server Integration Demo

Note most of our sprint review videos are NOT narrated.

http://mschnlnine.vo.llnwd.net/d1/ch9/6/3/1/2/2/4/ProjSrvrint.wmv

mms://mschnlnine.wmod.llnwd.net/a1809/d1/ch9/6/3/1/2/2/4/Project Server Integration Demo (FC2)-1.wmv

The new Team Foundation Server Work Item linking in Team Foundation Server code named Rosario

Gregg Boer

In our internal sprint reviews we often have videos of new features - here is an example by Gregg Boer showing the new Work Item linking functionality for Team Foundation Server code named Rosario – specifically the process for creating a Team Project collection.

Note most of our sprint review videos are NOT narrated.

http://mschnlnine.vo.llnwd.net/d1/ch9/7/1/7/9/2/4/LinkingDemo-CP2.wmv

RadioTFS interview with Habib on Microsoft Visual Studio Team System 2010 developer features

RadioTFS is going to be doing a series of shows on the new Features in Visual Studio Team System 2010 – In this edition they catch up with Habib and the developer features!

Habib is a Lead Program manager on the VSTS Development group.  His main responsibilities include the Visual Studio debugger, profiler, code coverage and pretty much anything related to troubleshooting and diagnosing applications.  He joined Microsoft in 2000 and has been in Developer Division ever since.  Before joining Microsoft, Habib studied computer science at the Australian National University in Canberra.  While not at work, Habib spends his time playing with robots, shooting hoops or chasing that elusive Yellowfin.  One of his favorite possessions is a Washington state license plate with the label "RUNTIME".

 

Team Test Special Interest group Monday October 13th from 3-5PM

The next Team Test Special Interest group will take place on Monday October 13^th from 3-5PM in the Microsoft Building 40 classroom 5 (map).  We’re excited to be provide you with an opportunity to play with the latest bits of Rosario and hear your feedback.  This is the same code that will be released in the next community technology preview. 

The event will follow the following schedule:

1. Hands on Lab walking through the Test Mini-Stories of the October CTP:

a. Executing Manual Test Cases

b. Automating portions of Manual Test Cases

c. Converting Recorded Automation into Coded Automation

d. Load Testing an Application

e. Test Case Management

2.  Polo Shirt Giveaway

As the lab can only accommodate so many people, please reply to this message indicating your attendance so that we can have an idea of how many computers to set up.  Please be sure to park in visitor parking in building 40 and sign in at building 40 front desk afterwards.  Classroom 5 is accessible directly from the lobby.

Thanks and I look forward to seeing you soon,

Naysawn w/ the Rosario Testing Team

9 sessions at PDC on Visual Studio Team System 2010

Definitely looking forward to my trip to PDC!  I plan to drive down with Grant Holiday and stopping by Portland Area .Net User Group, then Bay.NET on the way and hitting the SoCal code camp in LA.   I ‘think’ I am doing a WPF/Vista session in SF and might be doing a Rosario session in Socal – I will post final details as i get them.   Should be good time – especially with so many of the team going.

 

1. Microsoft Visual Studio Team System: Software Diagnostics and Quality for Services

In this session we present processes and tools from the upcoming Visual Studio Team System code name "Rosario" release and Microsoft Research and show how we deliver on quality, scalability, and experience goals for the new class of applications that demand rich UI, service consumption, and frequent release.

Presenter(s): Habib Heydarian, Justin Marks

 

2. Microsoft Visual Studio Team System Team Foundation Server: How We Use It at Microsoft

Take a detailed look at the present and future of Team Foundation Server (TFS). With close to 14,000 users, 2,000 projects, 33 million files, and over 2 million work items, Microsoft runs one of the largest known installations of TFS. In this session we share our internal best practices for version control, branching and merging, work item tracking, metrics, reporting, testing, and integrations with TFS.

Presenter: Brian Harry

 

3. Architecture without Big Design Up Front

Presenter: Peter Provost

Microsoft Visual Studio Team System (VSTS), code-name "Rosario" Architecture Edition, introduces new UML designers, use cases, activity diagrams, sequence diagrams that can visualize existing code, layering to enforce dependency rules, and physical designers to visualize, analyze, and refactor your software. See how VSTS extends UML logical views into physical views of your code. Learn how to create relationships from these views to work items and project metrics, how to extend these designers, and how to programmatically transform models into patterns for other domains and disciplines.

 

4. Improving .NET Application Performance and Scalability

Performance must be considered in each step of the development lifecycle. See how to integrate performance in design, development, testing, tuning, and production. Work with tools and technologies like: static analysis, managed memory profiling, data population, load testing, and performance reports. Learn best practices to avoid the performance pitfalls of poor CPU utilization, memory allocation bugs, and improper data sizing.

Presenter(s): Steve Carroll, Ed Glas

 

5. Agile Development with Microsoft Visual Studio

Visual Studio has built-in tool support for agile practices such as Scrum, XP, and others. The next version adds practices like test-driven development, continuous integration, and single product backlog. See how these can be applied at scale and across geographies.

Presenters Stephanie Saad and Lori Lamkin

6. Microsoft Visual Studio Team System: Leveraging Virtualization to Improve Code Quality with Team Lab

Would you like to test fixes in a production-like environment before checking them in to source control? The Visual Studio Team System (code name "Rosario") release of Team Lab improves productivity and quality while reducing the cost of building and testing world class products. Learn how Team Lab provides a fast and easy way to create a test environment and tear it down, target specific test environments, and take snapshots of an environment for easy deployment.

Presenter: Ram Cherala

 

7. "Rosario": A Sprint with the Next Version of Microsoft Visual Studio Team System

In the spirit of an agile sprint, see how to use the next version of Visual Studio Team System to manage user stories and re-factor existing architecture. Learn how to diagnose real production problems, debug in-production virtual labs, capture test data to eliminate the no-repro bugs, transparently plan, monitor, and adapt software projects.

Presenter: Cameron Skinner

 

8. Microsoft Visual Studio Team System Database Edition: Overview

Visual Studio Team System (VSTS) Database Edition enables developers to apply agile practices to the database tier. VSTS takes "One Version of the Truth" for database objects and moves it into source control. See how it interoperates with external data sources like MySQL, Oracle, IBM DB2, and Microsoft SQL Server 2008.

Presenter: Gert Drapers

 

9. Team Foundation Server: Cool New Features

Get under the hood of the next version of Team Foundation Server (TFS), and learn how TFS has factored its learnings about usability, industrial scale, geographic distribution, manageability, and development process into the next version of the product. See a demonstration new project planning and tracking features, such as agile planning, end to end traceability, reporting, and dashboards--all designed to improve transparency and velocity for teams from size 5 through 50,000. Learn how to scale distributed and parallel development with improvements to setup, administration, scalability, and how to cut down development time in the checkin/build process with source control improvements, branch visualization, gated check-in, buddy builds, distributed builds and workflow-based builds, and more.

Presenters: Sunder Raman, Stephanie Saad

 

Like i mentioned above we are also having LOTS of members of the team down.  Below is the current list:

 

1. Brian Harry
2. Cameron Skinner
3. Charles Sterling
4. Dan Massey
5. Doug Seven
6. Ed Glas
7. Euan Garden
8. Gert Drapers
9. Grant Holliday
10. Habib Heydarian
11. Justin Marks
12. Lori Lamkin
13. Matt Nunn
14. Norman Guadagno
15. Peter Provost
16. Ram Cherala
17. Sam Guckenheimer
18. Stephanie Saad
19. Steve Carroll

New blog on Visual Studio Team System 2010 Database and Software Development features

Good friend and fishing buddy Habib creates his blog and starts off with a bang with a great video and post on Database and Software Development features in Visual Studio Team System 2010

• What’s new in Visual Studio Team System 2010: Episode 1
• What’s new in Visual Studio Team System 2010: Episode 2

Brian Keller releases 4 more Rosario Videos to Channel9

 

The mad man with the camera is still at it.  Today Brian released four more videos –today focused on Team Foundation Server Project management and Processes.

His goal is to have 20 by the end of the week! So if you haven’t visited Channel9 lately now is the time.

 

• Enterprise Project Management with Visual Studio Team System 2010

  Ameya Bhatawdekar, a program manager for Team Foundation Server, took a few minutes to take us through the end-to-end storyboards for how Team Foundation Server 2010 will integrate with Microsoft Project Server to enable true enterprise-wide collaboration. Note that this is not a demo of working software (yet), but it's the next best thing - a detailed storyboard walkthrough of mocked-up screenshots. This "Humanized Screencast" is best viewed at fullscreen using the high-quality WMV…

  click to read more...

• Requirements Management and Traceability with Visual Studio Team System 2010

  How can you ensure that a requirement has been sufficiently tested? How do you track the work that goes into a specific feature? How much work is left to do before a feature is completed, and how does that feature relate to bigger scenarios or user stories? Siddharth Bhatia, a senior group program manager for Visual Studio Team System, takes us through an end-to-end example of how Visual Studio Team System 2010 will help an organization manage their requirements throughout the lifecycle of…

  click to read more...

• Agile Planning Templates in Visual Studio Team System 2010

  Stephanie Saad shows us a quick demonstration of how Visual Studio Team System 2010 will enable teams to be more agile. In this demonstration she shows the new Agile planning worksheet for Excel which can be used to easily balance resources, manage your backlog, and generate ad hoc reports.