Visual Studio Team System 2010 - 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

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. Select the Test Cases tab.
4. To find the test cases, click Add.

The Add Link to User Story dialog box is displayed.



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



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

Visual Studio Team System 2010 - Creating Manual Test Cases and Adding to a Test Suite

I am posting Test Features of Microsoft Visual Studio Team System 2010.

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

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

• To display the Planning Activities Center, click Planning.
• To display all the test suites, click Test Suite Manager in the Planning Activities sidebar.
• 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.

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

• 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:
• 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.
• Check Area shows DinnerNow.
• Click Owner to select Ellen Adams for the test case.
• Click Priority to select 1 for the importance of the test case.
• 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 , 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. 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 results.


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.

Automating Flex Applications with QTP

Flex application Automation Using QTP

There are two approaches to enable Flex application automation using QTP.

1. Runtime Approach.
2. Compilation Approach.

Runtime Approach:
General Implementation Concept:

You use the run-time testing files rather than building your applications with testing libraries. This lets you test SWF files that are compiled without automated testing support. To do this, you use a SWF file that does include the automated testing libraries. In that SWF file, the SWF Loader class loads your application's SWF file which does not include the testing libraries. The result is that you can test the target SWF file in a testing tool such as QTP, even though the application SWF file was not complied with automated testing support.

Flex Builder includes a wrapper SWF file and an HTML template that supports run-time loading. The source MXML file for the wrapper SWF file is also included. The following files are located in the “Flex_builder_install_dir/sdks\3.2.0\templates\automation-runtimeloading-files”

• RunTimeLoading.html -- The HTML template that loads the run-time loader SWF file. This template includes code that converts the automationswfurl query string parameter to a flashVars variable that it passes to the application. You use this query string parameter to specify the name of the application you want to test.
• runtimeloading.mxml -- The source code for the runtimeloading.swf file that you compile. The SWF file acts as a wrapper for your application. This SWF file includes the testing libraries so that you do not have to compile them into your application SWF file.
• Compile the runtimeloading.swf file: You can use the batch file in the Flex_builder_install_dir/sdks\3.2.0\templates\automation-runtimeloading-files directory. Execute this batch file from the sdks/3.2.0/frameworks directory. This batch file ensures that your runtimeloading.swf file includes the automation.swc, automation_agent.swc, automation_dmv.swc, automation_flashflexkit.swc, and qtp.swc libraries.
• Deploy the runtimeloading.swf, RunTimeLoading.html, and your application's SWF file to a web server. Request the RunTimeLoading.html file and pass the name of your SWF file as the value to the automationswfurl query string parameter.

For example: http://localhost/RunTimeLoading.html?automationswfurl=MyApp.swf

Implementation:
Please find the below steps followed to implement runtime approach.
Steps

1. Installed Flex builder 3.20 professional version.
2. Navigated to Flex_builder_install_dir/sdks\3.2.0\templates\automation-runtimeloading-files directory.
3. Observed that there one wrapper html file RunTimeLoading.html ,RunTimeLoading.mxml file and also build.bat.
4. We can use the batch file to compile RunTimeLoading.mxml with automation libraries.
5. After compilation it will generate runtimeloading.swf file in the same directory.
6. Request the RunTimeLoading.html file and pass the name of your SWF file as the value to the automationswfurl Automationswfurl=application.swf
7. Copy the runtimeloading.swf, RunTimeLoading.html, and your application's SWF file to a web server.
8. Start the services and access the URL as below
   ” http://hostname:11090/application/ux/RunTimeLoading.html
   

Compilation Approach:

If you do not use run-time testing, you must compile applications that you plan to test with the testing libraries. The functional testing classes are embedded in the application at compile time, and the application typically has no external dependencies for automated testing at run time.

Implementation of Compilation Approach:
Steps:
Copy the qtp.swc, automation_agent.swc, automation.swc and automation_dmv.swc files from the flex_automation_installer/frameworks/libs directory to flex_sdk_dir/frameworks/libs.

Need to copy the following files (airframework_rb.swc,automation_agent_rb.swc,automation_rb.swc,datavisualization_rb.swc,framework_rb.swc, rpc_rb.swc to) C:\Devtools\flex_sdk_3.3.0.4852\frameworks\libs\locale from flex_automation_installer/frameworks/libs directory to flex_sdk_dir/frameworks/libs

Implementation:
We have the added the above said tag to mxml target in ux/ant/compile.xml and compiled the application.mxml,Please refer the compile.xml from section 49 to 75
The modified ant target will be as follows.