QC Using

STUDENT WORKBOOK
Using Quality Center v11 STQC-155
LearnQuest Solutions
LearnQuest provides complete education solutions for organizations that need to train their staff on the latest business skills and Information Technology tools, methodologies, and languates. With over 20 years of experience, LearnQuest provides complete education solutions for corporations and government organizations that need to train their staff on the latest business skills and information technology tools, methodologies, and languages. LearnQuest offers an extensive library of customized private and public instructor-led training. Services include custom instructor-led classroom training, Virtual Classroom Training, project mentoring, assessments, blended learning, and comprehensive reskilling/new hire boot camps. LearnQuest works with organizations to better plan, develop, administer, and deploy training to their employees
Courseware Copyright 2001 - 2013 by First Contact Software Consultants Inc. All rights reserved. All text and figures included in this publication are the exclusive property of First Contact or its licensors, and may not be copied, reproduced, or used in any way without the express permission in writing of First Contact. Information in this document is subject to change without notice and does not represent a commitment on the part of First Contact. First Contact may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents except as expressly provided in any written license agreement from First Contact. This document may also contain registered trademarks, trademarks, service marks and/or trade names that are owned by their respective companies or organizations. First Contact disclaims any responsibility for specifying which companies or organizations own which marks. If you have any comments or suggestions regarding this document, please send them via e-mail to: training@firstcontactconsulting.com
130211_QC_USING
This hands-on course teaches Students how to use Quality Center to manage their testing data. Students will learn how to manage quality information to construct and organize requirements, create and execute test sets, monitor defects and use graphs and reports to track the success of a project.
Course Overview
Intended Audience
Quality assurance engineers Quality testers Project managers Developers
Course Objectives
At the end of the course, you will be able to: Define Releases and Cycles Define test requirements. Organize subjects and tests in the test plan tree. Design and create test plans. Execute manual tests Record and track test execution results. Log and manage defects Generate reports and graphs Export Data into Quality Center
How this Course is Organized

The course is divided into two sections: I. The first section teaches the concepts of Quality Center. It is intended for all users of Quality Center. The second section focuses on activities to learn how to use Quality Center. It is intended for those users who will enter test data such as testers and business analysts, or those users who need to see the details of the test data such as team leads, project managers and developers.
II.
Using Quality Center
Concepts and Overview| 1
Introducing Quality Center

The Quality Center Testing Process
Application testing is a complex process. Quality Center helps you organize and manage all phases of the application testing process, including specifying testing requirements, planning tests, executing tests and tracking defects.
Quality Center offers an organized framework for testing applications before they are deployed. Because test plans evolve with new or modified application requirements, you need a central data repository for organizing and managing the testing process. Quality Center guides you through all phases of the testing process.
The Quality Center testing process includes 5 phases: Specifying Releases - Develop a release-cycle management plan. Specifying Requirements - Identify and validate the functional and performance requirements that need to be tested. Planning Tests - Plan and confirm which tests need to be performed and how these tests must be run. Running Tests - Organize test sets, schedule their execution, perform test runs and analyze the results of these runs. Tracking Defects - Add defects that were detected in the application and track how repairs are progressing.
Throughout the testing process, you can generate reports and graphs.
Specifying Releases and Cycles

You begin the testing process by specifying releases in the Releases module. A release represents a group of changes in one or more applications that will be available for distribution at the same time. Each release can contain a number of cycles. A cycle represents a development and quality assurance cycle based on the project timeline. The releases and cycles have defined start and end dates. After you have created requirements in the Requirements module, you assign them to releases and cycles. You later plan tests to test these requirements and run them as part of test sets, belonging to test set folders. Each test set folder is assigned to a cycle defects, from which you can assign them to specific cycles. In this way, you can keep track of the progress and quality of your release.
Specifying Requirements
After you have defined releases and cycles, you specify requirements in the Requirements module. Requirements describe in detail what needs to be tested in your application and provide the test team with the foundation on which the entire testing process is based. You can define the requirements in Quality Center by creating a requirements tree. This is a graphical representation of your requirement specifications, displaying your requirements hierarchically. You can group and sort requirements in the tree, monitor task allocation, monitor the progress in meeting requirements and generate detailed reports and graphs. After you create tests in the Test Plan module, you can link requirements to given tests. Later, after you begin logging defects you can also link requirements to defects. In this way, you can keep track of your testing needs at all stages of the testing process. If a requirement changes, you can immediately identify which tests and defects are affected, and who is responsible for them.
Planning Tests
After you define your requirements, you need to determine your testing goals. To do this, examine your application, system environment and testing process to outline the testing strategy for achieving your goals. After you determine your testing goals, you build a test plan tree, which hierarchically divides your application into testing units, or subjects. For each subject in the test plan tree, you can define tests that contain steps. For each test step, you specify the actions to be performed on your application and the expected result. You can increase the flexibility of a test step by adding parameters.
To keep track of the relationship between your tests and your requirements, you can add links between them. This can help you ensure compliance with your requirements throughout the testing process. After you design your tests, you can decide which tests to automate. When you automate a test, you can generate a test script and then complete it using other HP testing tools (for example, QuickTest Professional).
Running Tests
Running tests is the core of the testing process. As your application changes, you can run manual and automated tests in your project to locate defects and assess quality. You start by creating test sets and choosing which tests to include in each set. A test set is a group of tests in a Quality Center project designed to achieve specific testing goals. Quality Center enables you to control the execution of tests in a test set by setting conditions and scheduling the date and time for executing your tests. After you define test sets, you can begin to execute your tests. You can then use Quality Center to view and analyze the results of your tests. When you run a test manually, you can execute the test steps you defined in test planning. You can pass or fail each step, depending on whether the actual results match the expected output. When you run a test automatically, Quality Center opens the selected testing tool, which runs the test and imports the test results to Quality Center.
Adding and Tracking Defects

Locating and repairing defects is an essential phase in application development. Defects can be detected and submitted by developers and testers in all stages of the testing process. Using Quality Center, you can submit defects detected in the application and track them until they have been repaired and retested.
Analyzing the Testing Process

Quality Center reports and graphs help you assess your testing process. You can generate reports and graphs at any time during the testing process from the Requirements, Test Plan, Test Lab and Defects modules using default or customized settings. When customizing a report or graph, you can apply filters and sort conditions and display information according to your specifications. You can also save your settings as favourite views and reload them as needed.
Project customization
The HP Quality Center administrator should customize projects to meet the specific needs of your testing team. This includes adding and customizing fields, and creating categories and lists that reflect the needs of a specific testing project and suit your projects unique quality objectives, standards and testing approach. The administrator can modify the behavior of HP Quality Center fields by: Restricting users to selecting only values from associated lists Making an entry in certain fields mandatory Preserving a history of values entered in a specific field Including data unique to your project by creating user fields Associating these fields with HP Quality Center and user-defined lists
You can customize and add fields that may be critical to collecting relevant quality metrics. The data quality increases as the drop-down lists and automatic fill-ins are used. You can identify the information required for evaluating application readiness and progress of the testing development and other relevant IT processes. Properly customizing HP Quality Center helps to manage multi-application testing efforts.
Quality Center Administration

Throughout the testing process, Quality Center projects are accessed by many usersincluding developers, testers, and quality assurance managers. In order to protect, maintain and control information in a testing project, users are assigned to groups with different access privileges. Only a Quality Center project administrator (belonging to the TDAdmin user group) has full privileges in a Quality Center project. As a Quality Center site administrator, you use Site Administration to create and maintain Quality Center domains and projects, manage Quality Center users, connections, licenses, define database servers and modify Quality Center configurations. As a Quality Center project administrator, you can use Project Customization to customize project entities and lists, set up user groups and permissions, configure mail, set alert rules, and configure the workflow in the Quality Center modules. Quality Center is shipped without any passwords defined. To protect your testing data from unauthorized access, it is highly recommended that you set passwords early in the Quality Center process.
Login to Quality Center

Server
Address
http://
User Name Password
Project
Domain Project
1. Open Internet Explorer by double clicking on the Desktop shortcut. The homepage is set to load the quality center home page (now also known as Application Lifecycle Management) 2. From the Quality Center home (now listed as Application Lifecycle Management), click on the Application Lifecycle Management link. 3. For the Login Name:/Password: , enter the values provided by the instructor and click Authenticate. 4. Select the Domain and Project provided by the instructor and click Login.
Case Study 1 Standard Implementation
This case study will describe the simplest complete way to implement Quality Center across all the modules.
Quality Center Implementation
Case Study 1|1
Activities Summary
Releases Testing needs to be done on the Progressive.com website. The specific applications being developed are Find a Quote, navigation links, Report a Claim, and Site Search. We will create a Release structure for each of the applications being tested, with Cycles for each release. Each Cycle will describe the functionality to be tested during that cycle. Requirements We will create an organizational structure similar to that used in the Releases module to hold the testing requirements and the applications being tested. Testing requirements will be created within each folder and linked to their appropriate cycles to indicate where they should be tested. Tests We will create a Test Plan folder structure similar to those used in the Releases and Requirements modules to hold the tests being developed. We will create manual tests to verify the testing requirements we created for the Get a Quote application. Test steps will be added to one of the tests so that it can be executed. The tests will be linked to their appropriate requirements so that we can monitor whether the requirements are being met. Test Execution We will create a Test Set Folder structure to organize the execution of the tests during the cycles of development. We will create a Test Set for an execution of the regression tests to be executed during Cycle 1. The Test Set Folder will be linked to Cycle 1 so that we can see a report of the progress of the cycle. We will perform a manual execution of one of the tests on the Progressive.com website and report a defect when the test fails. Defects The defect found during test execution will be updated once the problem has been found. A new defect will be opened to report a problem found outside of the execution of a test. Analysis Generate graphs and reports.
Quality Center Implementation Case Study 1|2
You can begin the application management process by defining a releases tree in the Releases module. The foundation of the Releases module is the releases tree. This tree enables the modeling of upcoming releases within a hierarchical tree structure. You can start by defining a release folder along with its releases. A release represents a group of changes in one or more applications that will be available for distribution at the same time. After defining the release, you define cycles. A cycle is a set of development and quality assurance efforts performed to achieve a common goal based on the release timeline. After defining the releases tree, you define and review the requirements in the Requirements module and assign them to releases and cycles. Following test runs, you can review the test progress to determine how well it meets the release goals. You can also determine how many defects were resolved and how many still remain open. The results can be analyzed at a release or cycle level.
Releases and Cycles
Instructor-Led Demo
2. Create the Releases 3. Add the Cycles
1. Create the Releases folders
Case Study 1|3
Activity 1: Create the Releases Folders

Part 1 Navigate to Releases Module
1. In the Quality Center Sidebar, click the Management icon. 2. Click on the Releases tab.
Part 2 Create Release Tree

3. In the tree section, select the top level folder Releases. 4. Click the New Release Folder button.
5. In the New Release Folder window, name the new folder Progressive.com. 6. Click OK. 7. Select the Progressive.com Website folder. 8. Use the table below to create additional folders under the Progressive.com Website folder. Folder Name Get A Quote Navigation Report Claim Site Search 9. The Releases tree should resemble the following:
Case Study 1|4
Activity 2: Create Releases and Cycles

Part 1 Add a Release
1. Select the Get a Quote folder 2. Click the New Release button
3. Name the release Release 1 4. In the *Start Date: field, enter the current date 5. In the *End Date: field, enter the current date two months from now 6. Click OK.
Part 2 Add Cycles

7. Ensure Release 1 selected. 8. Click the New Cycle button.
9. Name the new cycle Cycle 1 - Regression. 10. In the *Start Date: field, enter the current date. 11. In the *End Date: field, enter the current date one week from today. 12. Click the OK button. 13. Ensure Cycle 1 - Regression is selected. 14. Click the Duplicate Cycle button.
Case Study 1|5
15. Select Cycle 1 - Regression_Copy_1. 16. In the Details tab, select the Name field and replace the existing name with Cycle 2 New Features.
17. Click the Refresh button. Verify the name changes in the folder tree.
18. Ensure Cycle 2 New Features is selected. 19. Click the Reschedule button.
10. Change the Start Date to one week from today and the End Date 4 weeks from today. 11. Select Release 1. 12. Select the Master Plan tab to view where the overall release schedule.
Case Study 1|6
Activity 3: Complete Release Tree

use random Start and End Dates within the two month period. Parent Folder Get a Quote Navigation Navigation Report Claim Report Claim Site Search Release Name Release 1 Release 1 Release 1 Release 1 Release 1 Release 3
1. Use the table below to create Releases and Cycles for the remaining applications. For each release, select a Start Date of today and an End Date two months from today. For each cycle, Cycle Name Cycle 3 Performance Testing Cycle 1 Sanity Testing Cycle 2 Stress Testing Cycle 1 Security Testing Cycle 2 End To End Testing Cycle 1 UAT Testing
2. The releases tree should resemble the following:
Case Study 1|7
You can begin the application life cycle management process by gathering all available documentation on the application under development, such as marketing and business requirements documents, system requirement specifications and design documents. Use these documents to obtain a thorough understanding of the application under development and determine your scope, goals, objectives and strategies.
Requirements
Instructor-Led Demo
2. Add a Requirement 3. Add an attachment
1. Create a Requirement folder
4. Refresh the Requirements page 5. Filter the Requirements 6. Use Zoom to filter the Requirements 7. Examine the various Requirements views
Case Study 1|8
Activity 4: Create a Requirements Tree

Part 1 Navigate to the Requirements Module
1. In the Sidebar, click the Requirements button.
2. Select View > Requirement Details. Note: With the exception of the Requirements Grid view, you can create the structure in any of the views but Requirement Details is a commonly-preferred view.
Part 2 - Create the Requirements Structure

3. Select the Requirements folder. 4. Click the New Folder button.
5. In the Requirement Folder Name field, type Progressive.com and Click OK. 6. Select the newly created folder and Click the New Folder button. 7. Name this folder Get A Quote and Click the OK button. 8. Use the details in the following table to create additional Requirement Folders: Parent Folder Progressive.com Progressive.com Progressive.com Folder Name Navigation Report Claim Site Search
9. The requirements tree should resemble the following:
Case Study 1|9
Activity 5: Create Requirements

Part 1 - Create the Requirement
1. Select the Get A Quote folder. 2. Click the New Requirement button.
3. In the New Requirement window, click the Requirement Type drop down menu select Functional.
4. Use the table below to fill in the required information: Name Request a Homeowner Quote Priority 2-Medium Target Release Progressive.com > Get A Quote > Release 1 Target Cycle Progressive.com > Get A Quote > Release 1 > Cycle 1 - Regression Description The application needs to provide the ability for a user to request a Homeowner policy quote and the application needs to provide a valid quote based on the users input. 5. Click the Submit button.
Part 2 Finish Requirements for Get A Quote Folder.

6. Use the table below to fill in the information for the second requirement. Name Request an Auto Quote Type Functional Priority 2-Medium Target Release Progressive.com > Get A Quote > Release 1 Target Cycle Progressive.com > Get A Quote > Release 1 > Cycle 1 - Regression Quality Center Implementation C a s e S t u d y 1 | 10
7. Click the Submit button. 8. Use the table below to fill in the information for the third requirement. Name Find Agent Type Functional Priority 2-Medium Target Release Progressive.com > Get A Quote > Release 1 Target Cycle Progressive.com > Get A Quote > Release 1 > Cycle 2 New Features 9. Click the Submit button. 10. Use the table below to fill in the information for the fourth requirement. Name Rate Comparison List Displays Correctly Type Functional Priority 2-Medium Target Release Progressive.com > Get A Quote > Release 1 Target Cycle Progressive.com > Get A Quote > Release 1 > Cycle 2 New Features 11. Click the Submit button, followed by Close. 12. The requirements tree should resemble the following:
Part 3 - Create Requirements For Remaining Folders

13. Use the details in the following tables to create requirements in the specified folders. For each requirement, use a Priority of 3-High Navigation parent folder: Type Name Target Cycle Functional Car Insurance and More links Progressive.com > Navigation > Release 1 > goes to correct page Cycle 1 Sanity Testing Functional Shop with an Agent links goes Progressive.com > Navigation > Release 1 > to correct page Cycle 1 Sanity Testing Functional Home link returns to main Progressive.com > Navigation > Release 1 > page Cycle 1 Sanity Testing Functional Car and Vehicle Insurance link Progressive.com > Navigation > Release 1 > goes to correct page Cycle 1 Sanity Testing Functional Home and Renters Insurance Progressive.com > Navigation > Release 1 > link goes to correct page Cycle 1 Sanity Testing
C a s e S t u d y 1 | 11
Report Claim parent folder: Type Name Functional Successful login Functional Incorrect logins are unsuccessful
Target Cycle Progressive.com > Report Claim > Release 1 > Cycle 1 Security Testing Progressive.com > Report Claim > Release 1 > Cycle 1 Security Testing
Site Search parent folder. Type Name Functional Search results are correct
Target Cycle Progressive.com > Site Search > Release 3 > Cycle 1 UAT Testing
14. The requirements tree should resemble the following:
C a s e S t u d y 1 | 12
Creating Manual Tests
Developing a clear and concise test plan is fundamental to successful application testing. A good test plan enables you to assess the quality of your application at any point in the application management process. The test plan tree is a graphical representation of your test plan. It is a hierarchical list of tests organized according to topic, which describes the set of tests you will implement in order to meet your quality requirements. Plan tests for each subject in your test plan tree. Decide which types of tests to create for each subject, such as sanity level tests or regression tests. (For an explanation of these test types, see Creating Test Sets.) Then create the tests and assign them to a branch of the test plan tree.
Instructor-Led Demo
1. Create the test plan tree 2. Create tests 3. Add test steps 4. Link Tests and Requirements
C a s e S t u d y 1 | 13
Activity 6: Create a Test Plan Structure

1. In the Quality Center Sidebar, Click the Test Plan button.
2. Select the Subject folder. 3. Click the New Folder button.
4. 5. 6. 7. 8. 9.
In the New Folder window, name your new folder as Progressive.com. Click OK. Click the New Folder button. In the New Folder window, name your new folder as Get A Quote. Click OK. Use the following table to create test plan folders for the remainder of the applications being tested: Parent Folder Folder Name Progressive.com Navigation Navigation Home Page Navigation Site Nav Progressive.com Report a Claim Progressive.com Site Search
10. The subject tree should resemble the following:
C a s e S t u d y 1 | 14
Activity 7: Create Tests

Part 1 - Add a Test
1. Select the Get a Quote folder. 2. Click the New Test button.
3. 4. 5. 6.
In the New Test window, ensure the Test Type is Manual. Enter Request a Quote in the Test Name field. Click OK. Click in the Description field and enter the following text: This test will request the various types of quotes (Auto, Homeowner, etc.) and validate the values returned to the user.
Part 2 - Create additional Tests

7. Use the table below to create additional Test Plans in the specified folders. Use Test Type Manual for each test Test Plan Folder Test Name Description Get a Quote Find Agent This test will put the user in touch with a local Agent who can serve their needs. Get A Quote Correct Display of Rate Verify that the rate comparison list is Comparisons displayed correctly Navigation \ Home Car Insurance and More Verify that each link in the "Car Insurance Page and More" section navigates to the correct page Shop with an Agent Verify that each link in the "Shop with an Agent" section navigates to the correct page Navigation \ Site Nav Home Verify that the Home link always returns to the main page Car and Vehicle Verify that the Car and Vehicle Insurance link goes to the correct section Quality Center Implementation C a s e S t u d y 1 | 15
Test Plan Folder
Test Name Home and Renters
Description of the site Verify that the Home and Renters Insurance link goes to the correct section of the site Verify that a user can correctly login with a valid Username and Password Verify that a user CANNOT login with an invalid Username or Password Verify that the Site Search feature returns correct results
Report a Claim
Valid Login Invalid Login
Site Search
Search returns relevant results
8. The subject tree should resemble the following:
C a s e S t u d y 1 | 16
Activity 8: Complete the Design Steps

Part 1 Add Design Steps
1. Select the Request a Quote test plan. 2. Select the Design Steps tab.
3. Click the New Step button.
1. In the Description Field, type Navigate to Progressive.com Website. 2. In the Expected Result Field type The Progressive.com Website loads. 3. Within the Design Step Editor window, Click the New Step button to proceed to the next step:
4. Using the above process, continue adding the following Description and Expected Result values: Step Name Description Expected Result Step 2 In the Get a Quote section, select the Policy Holder Name and Address type as Auto, enter your zip code (or screen should appear. 44143) and click Quote and Compare button. Step 3 Complete the Name and Personal Add Vehicles to your Quote screen Information screen and Click Next. appears. Step 4 Select the vehicle Type, Year, Make and The vehicle is added to the list and Model. Click Add This Vehicle. the caption reads, 1 Vehicle On Your Quote Step 5 Click Next. Provide Vehicle Details screen appears. Note: In real life youd complete all the remaining steps, but to save time well stop here. 5. Click OK in the Design Step Editor window when steps are complete. 6. Your steps should appear in a grid format as follows: Quality Center Implementation C a s e S t u d y 1 | 17
Part 2 Create additional Test Steps

7. Use the table below to add Design Steps to the other tests Test Name Step Description Correct display of Open a web browser and navigate rate comparisons to http://www.progressive.com Verify that the rate comparison list is displayed to the right of the Get a Quote application Verify the rate comparison list is scrolling vertically Choose a rate from the list and verify it is correct Car Insurance and Open a web browser and navigate More to http://www.progressive.com Click each link in the Car Insurance and More section of the main page Shop with an Agent Open a web browser and navigate to http://www.progressive.com Click each link in the Shop with an Agent section of the main page
Expected Results Progressive.com homepage is displayed. Rate comparison list is displayed to the right of Get a Quote. Rate comparison list is scrolling vertically. Selected rate is correct. Progressive.com homepage is displayed. Page corresponding to the link clicked is displayed. Progressive.com homepage is displayed. Page corresponding to the link clicked is displayed.
C a s e S t u d y 1 | 18
Activity 9 - Link Test and Requirement

Part 1 - Navigate to the Req Coverage Screen
1. Select the Request a Quote test plan. 2. Select the Req Coverage tab.
3. Click the Select Req button. The Requirements tree is displayed on the far right of the screen:
Part 2 - Link requirements to Test Case

4. 5. 6. 7. 8. In the Requirements tree, expand the Requirements folder. Expand the Progressive.com folder. Expand the Get a Quote folder. Select the Request a Homeowner Quote requirement. Click the Add to Coverage button.
9. Select the Request an Auto Quote requirement. 10. Click the Add to Coverage button. 11. The requirement coverage list should resemble the following:
12. Select the Find Agent test in the Test Plan tree. 13. Select the Find Agent requirement in the Requirements Tree. 14. Click the Add to Coverage button. Quality Center Implementation C a s e S t u d y 1 | 19
Part 4 - Link the rest of the tests to their requirements

15. Use the table below to link the remainder of the tests to their corresponding Requirements Test Name Requirement Correct display of rate comparisons Rate comparison list displays correctly Car Insurance and More Car insurance and More links go to the correct pages Shop with an Agent Shop with an Agent links go to the correct pages Car and Vehicle Car and Vehicle Insurance link goes to the correct page Home Home link returns to main page Home and Renters Home and Renters Insurance goes to the correct page Invalid login Incorrect logins are unsuccessful Valid login Successful login Search returns relevant results Search results are correct
C a s e S t u d y 1 | 20
Test Execution
As your application changes, you can run the manual and automated tests in your project in order to locate defects and assess quality. Start by creating test sets and choosing which tests to include in each set. A test set is a group of tests in a Quality Center project designed to achieve specific testing goals. Once you have defined test sets, you can begin executing the tests. When you run a test manually, you can execute the test steps that you defined during test planning. You can pass or fail each step, depending on whether the application's actual results match the expected output.
Instructor-Led Demo
1. Create a Test Set tree 2. Create a Test Set 3. Add tests to the Test set 4. Run a manual test
C a s e S t u d y 1 | 21
Activity 10 - Create the Test Set Folder

Part 1 - Create Test Set
1. In the Quality Center Sidebar, Click the Test Lab button.
2. In the Test Lab tree, select the Root folder. 3. Click the New Folder button.
4. Name the new folder Regression and click OK.
Part 3 - Link the Regression folder to Cycle 1

5. Select the Regression folder. 6. Click the Assigned to cycle drop down menu and select Progressive.com > Get A Quote > Release 1 > Cycle 1 Regression.
7. In the Description field type Execution of all the regression tests for Cycle 1.
C a s e S t u d y 1 | 22
Activity 11 - Add Tests to Test Set

Part 1 - Create the R1.1 Tests Test Set
1. Select the Regression Test Set folder. 2. Click the New Test Set button.
3. Use the table below to fill out the required information: Test Set Name: R1.1 Tests Description First execution of all the regression tests defined in the Test Plan 4. Click OK. 5. Select the Execution Grid tab.
Part 2 - Add tests to the R1.1 Tests test set

6. Click the Select Tests button.
7. In the Test Plan Tree on the right side of the screen, expand the Progressive.com folder and select the Get A Quote folder. 8. Click the Add Test To Test Set button.
9. In the Confirm window, click Yes.
C a s e S t u d y 1 | 23
10. The execution grid should resemble the following:
C a s e S t u d y 1 | 24
Activity 12 - Execute a Test

Part 1 - Begin executing the Request Quote test
1. Ensure the (1)Request a Quote test is selected.
2. Click the Run drop down menu and select Run with Manual Runner.
3. In the Manual Runner window, click the Begin Run button.
3. Open a new Internet Explorer window and perform the operations described in the Description field: navigate to http://www.progressive.com. Type a description of the result into the Actual field: Progressive.com website loaded 4. Click the Pass Selected button.
5. Follow the Description for Step 2. In the Actual pane, type Policy Holder Name and Address page loaded
Part 2 - Report a Failed Step

Note: For the purposes of this exercise, we are going to assume that Step 3 of the test has failed. 6. With Step 3 of the test selected, enter Actual result: Server unavailable error is displayed 7. Click the New Defect button.
C a s e S t u d y 1 | 25
8. Use the table below to fill in the required information: Summary Severity Priority Target Cycle Vehicle Quote Fails 4-Very High 4-Very High Get A Quote > Release 1 > Cycle 2 New Features
9. Click OK. 10. Click the Fail Selected button.
Note: The defect that you just reported represents a fatal error: we cannot continue executing the test because the application crashed. We will need to stop executing the test at this point, leaving Step 4 and Step 5 unexecuted 11. Click the End Run button.
12. At this point the execution grid should resemble the following:
C a s e S t u d y 1 | 26
Activity 13 - Execute The Test Again

Part 1 Begin executing the Request a Quote test Note: You are performing a test execution here, so you will want to actually execute the steps described in the test 1. Ensure the (1)Request a Quote test case is selected.
2. Click the Run drop down menu and select Run with Manual Runner.
3. Click the Begin Run button. Note all the Steps show a status of No Run.
4. Open a new Internet Explorer window and perform the operations described in the Description field: navigate to http://www.progressive.com. Type a description of the result into the Actual field: Progressive.com website loaded 5. Click the Pass Selected button. 6. Complete the remaining steps as Passed steps. (We will assume the remaining steps work properly so that we can see what a passing test looks like.) 7. Once all the steps are passed, the Manual Runner should resemble the following:
Part 2 Stop the Test 8. Click the End Run button. 9. At this point your Execution Grid should resemble the following:
C a s e S t u d y 1 | 27
Part 3 Examine Past Runs

10. In the Execution Grid, right-click on the (1)Request a Quote test and select Test Instance Details.
11. Select the Runs link.
12. Review the information displayed in the Report tab between the two runs and click OK.
C a s e S t u d y 1 | 28
Defects
Locating and repairing application defects efficiently is essential to the development process. Defects can be detected and added to your Quality Center project by users during all stages of the application management process. Using the Quality Center Defects module, you can report design flaws in your application and track data derived from defect records. When you discover a defect in your application, you can submit a defect to the Quality Center project. The project stores defect information that can be accessed by authorized users, such as members of the development, quality assurance and support teams. You can associate this new defect with the cycle and release in which it was detected.
Instructor-Led Demo
1. Add a Defect 2. Filter the Defects grid 3. Save the filter to the Favourites list 4. Update a Defect 5. Add a comment to a defect 6. Manually link a defect to a test
C a s e S t u d y 1 | 29
Activity 14 - Modify an Existing Defect

Part 1 - Navigate to the Defects Module
1. In the Quality Center Sidebar, click the Defects button. 2. In the Defects menu, select Defect Details
Part 2 - Add a Comment to the Defect

3. In the Comment field type The problem was a missing value in the database query. The issue has been resolved 4. Click the Add Comment button. Your user name and the current date appear in the Comments window:
5. In the Status drop down menu, select Fixed.
6. Click OK to save your modifications to the defect.
C a s e S t u d y 1 | 30
Activity 15 - Create a New Defect

Part 1 - Create a new Defect
1. Click the New Defect button. 2. Use the table below to fill in the required information: Summary Incorrect Quote Value Severity 4-Very High Detected in Cycle Get A Quote > Release 1 > Cycle 1 Regression Subject Get A Quote Assigned To <select the user you are logged in as> Description While using the Rate Comparisons application I discovered that some of the values being returned are incorrect. I will capture a screenshot and attach it to the defect. 3. Click Submit to create the defect. 4. Click Close to close the New Defect window
Part 2 Assign Defect to Test Case

5. Navigate to the Test Plan module. 6. Select the Correct Display of Rate Comparisons test case. 7. Select the Linked Defects tab.
8. Click the Link Existing Defects menu and select Select
9. In the Defects To Link window, select the Incorrect Quote Value defect and click Link. 10. Select the Req Coverage tab.
C a s e S t u d y 1 | 31
11. Under the Entity Name column, click the Rate Comparison List Displays Correctly link. 12. Select the Linked Defects tab.
13. Click the Type of Link drop down menu and select All Links.
14. Verify the Defect now is present. Click the Defect ID link to head back to the Defects module.
C a s e S t u d y 1 | 32
Analysis
You can generate graphs that let you view images describing the information in a Quality Center project. You can also design graphs that combine data from multiple projects. Standard reports offer you a variety of report types that list data from Quality Center modules.
Instructor-Led Demo
1. Create a graph 2. Create a report
C a s e S t u d y 1 | 33
Activity 16 - Analysis and Dashboard tree

Part 1- Creating a Public Graph
1. Select the Analysis View module 2. Select the Public folder. 3. Click the New Folder button to create a new folder. 4. Enter My Graphs for the folder name. Click OK. 5. Click the New Item icon. 6. Select New Graph from the New Item drop down menu.
7. In the New Graph dialog window, select Defects from the Entity list and select Progress Graph from the Graph Type list. Name the graph Defects Progress Graph. 8. Click OK. 9. Repeat the steps for the following graphs: Entity REQUIREMENTS TEST INSTANCES TESTS Graph Tree PROGRESS GRAPH SUMMARY GRAPH PROGRESS GRAPH Graph Name Requirements Progress Test Instances Summary Tests Progress
Part 2 - Create a Dashboard Page

10. Under the Dashboard module, click Dashboard View. 11. Select the Public folder. 12. Click the New Folder button to create a new folder. 13. Enter My Dashboard Folder for the folder name. Click OK. 14. In the Dashboard tree, select the folder you created. Quality Center Implementation C a s e S t u d y 1 | 34
15. Click the New Page button.
16. Enter My Dashboard Page for the name. Click OK. Part 3 - Configuring Dashboard Pages
17. Click the Configuration tab.
18. Click the Refresh button to refresh the graphs tree. 19. Select and expand My Graphs folder. You should see the graphs you have created. 20. Add all graphs to your dashboard page by clicking the Add Graph to Dashboard Page button. Alternatively, you can drag a graph to a new row above or below existing graphs, or to an empty box alongside a graph. 21. The Tests Progress graph should be expanded. Click the Expand button. The button is located at the top-left corner of each graph.
22. Do the same for the Test Instances Summary graph. 23. Move the Requirements Progress graph next to the Defect Progress graph by dragging the graph. 24. Remove the Tests Progress graph by clicking the Remove button which is located at the topright corner of the graph.
Part 4 - Viewing Dashboard Pages

25. Click the Generate button on the Dashboard View toolbar. Alternatively, click the View tab. Quality Center generates and displays the graphs in the Dashboard page. 26. Click the View Page in Full Screen button.
C a s e S t u d y 1 | 35
Part 5 - Moving Items and Folders

27. Select the My Graphs folder you created and expand it. 28. Select the Defects Progress Report. 29. Click the Cut button. Alternatively, right-click and choose Cut. 30. Select the Private folder. Click the Paste button. Alternatively, right-click and choose Paste. 31. Navigate back to the My Graphs Folder. 32. Select Tests Progress Graph. 33. Right-click and select Copy. 34. Select the Private folder, and right-click select Paste.
C a s e S t u d y 1 | 36
Activity 17: Standard Reports and Graphs

Part 1 Create Report for Requirements
1. Navigate to the Requirements module 2. From the View menu, select Requirement Details.
3. From the Analysis menu, select Reports > Standard Requirement Report.
4. Note the number of pages for the report.
5. Click the Add to Analysis Tree button. 6. In the New Standard Report window, select the Private folder and click the New Folder button.
7. Name the new folder as your student** account and click OK. 8. Click Save. 9. If you are not automatically transported to the Analysis View module, navigate there and select the newly created report.
C a s e S t u d y 1 | 37
10. Click on the Configuration tab.
11. Click the Filter button.
12. Mouse over the row for Req Parent and click the drop down menu.
13. In the Select Filter Condition window, expand the Requirements root folder and select the Progressive.com > Get A Quote folder. 14. Click OK twice. 15. Click the View tab and review the contents of the report. Note the number of pages now present in the report.
Part 2 Create Report For Test Cases

16. Select the student** folder you created. 17. Click the New Item drop down menu and select New Standard Report.
C a s e S t u d y 1 | 38
18. In the New Standard Report window, use the table below to complete the requirement information. Entity Standard Report Type Standard Report Name 19. Click OK. 20. In the Configuration tab, click the Filter button. Tests Test Plan Report Get A Quote Test Cases
21. In the Filter Tests window, select the Cross Filter tab.
22. Under Requirements, click the Filter radio button.
23. In the Cross Filter: Requirements window, click the drop menu for Req Parent.
24. In the Select Filter Condition window, expand the Requirements root folder and select the Progressive.com > Get A Quote folder. 25. Click OK. 26. Click the ellipsis button for the Type drop down menu.
27. Select MANUAL and click OK, followed by OK.
C a s e S t u d y 1 | 39
28. Click the Add Sub Report button.
29. In the Add Sub-Report window, select Design Steps from the Type drop down menu and click OK. 30. Click the View tab and review the contents of the report. Note all of the tests cases displayed are MANUAL test cases and their Design Steps are displayed as well.
C a s e S t u d y 1 | 40
Case Study 2 Exporting With Excel
Exporting with Excel
Case Study 2|1
If you have existing test documents in Microsoft Excel, you can export them directly to Quality Center. To export Requirements, Test Plans, or Defects from Microsoft Excel to Quality Center, the user must install the Microsoft Excel Add-in on their client machine. The Add-in is installed through the Quality Center home page under the Add-Ins Page
General Setup
Once the user navigates to the More HP ALM Add-ins page, the Add-in will be found under the Microsoft Office Add-ins: section. Installation is completed through a wizard that guides the user through a relativity fast setup process Once the Add-in is installed, a link under the Add-Ins ribbon will now be visible to the user call Export To HP ALM Note: The Add-in can be uninstalled through Add/Remove programs in Windows Control Panel
When creating data to export to Excel, the first row is typically used as the column heading. As such when selecting which cells to export, the column heading row must never be selected. When exporting, Excel will start an exporting wizard, starting with prompting the user to enter
Case Study 2|2
in the address of the Quality Center server, followed by the user's login credentials and what project the data will be exported to. Mapping Fields The user must match the column heading to the field value to be populated in the Mapping wizard. Any Quality Center fields that are red require the user to specify a column with data for that field or the export process cannot go any further. The mapping wizard also has a button that will ask for the row with the column headings and will text match the headings to the Field names in Quality Center.
Once the export is complete, the wizard closes and the user can then view the results in Quality Center
Case Study 2|3
Instructor-Led Demo
1. Prepare Excel sheet for exporting to Quality Center
2. Export To Quality Center
Case Study 2|4
Activity Summary
Test Plan
Export and view results
Case Study 2|5
Activity 1 Export from Excel

2. Highlight every row of data except the header row 3. In the Excel ribbon, choose Add-Ins Export to HP ALM
1. On the desktop, locate the file Using QC Tests.xls and open it
4. In the Quality Center Export Wizard, enter the server name and press Next 5. Enter the login and password credentials (student/mercury) and click Next 6. Select the Domain and Project specified at the beginning and press Next 7. Select the type of data as Tests 8. Select Type a new map name and use the following name: TestMap1. Then click Next. 9. In the left column, select Subject and press the > to move it to the right side. In the popup that appears, choose column A and press OK. Complete the mappings as follows:
10. Press Next 11. You should have a message saying You have successfully exported the Microsoft Excel Worksheet to Quality Center 12. Press Finish 13. Navigate to the Test Plan Section and expand the section to validate the tests have been imported correctly.
Case Study 2|6
Lesson 3 Advanced Test Options
Advanced Test Options
Lesson 3-1
Test Parameters
To increase the flexibility of manual tests, you can add parameters to design steps. This enables you to run the same test repeatedly with different data each time. A test parameter is a variable that can be assigned a value outside the test from which it is defined. Before you can use parameters in design steps, you need to define them in the test. Manual tests with parameters can be called from other tests. This is useful if you have common steps you often want to perform as part of other tests.
Lesson 3-2
Instructor-Led Demo
1. Add test parameters
2. Call a test with test parameters
Lesson 3-3
Activity Summary
Tests

Add test parameters to make the login test more flexible Call a test that uses the new login test.
Test Execution
Run a test with parameters
Lesson 3-4
Activity 1 Add Test Parameters

Part 1- Create a new test 1. Select the Test Plan module 2. Create a new folder named Subject > Website Security. 3. Create the following test (use any values for any other mandatory field). Test Name Login with Parameters Design Steps Step 1 Step 2 Step 3 Step 4 Description Verify that a user can correctly login with a valid Username and Password
The homepage is displayed The valid username is entered in the User ID field. The password is entered in the field but is not readable by the user. User is successfully logged in.
Open a web browser and navigate to the home page In the User ID field enter a valid username In the Password field enter the correct password for the username you entered Click the Log in button
Part 2 - Add Test parameters 4. Click on the Design Steps tab 5. In Step 2, position the cursor after the last word in the description cell and click on the Insert Parameter button ( ) ) 6. In the Parameters window, click on the New Parameter button ( 7. Type UserID in the Parameter Name: field 8. Click OK 9. Click OK to close the Parameters window 10. Repeat the above steps to create a parameter called Pwd in Step 3. 11. Your steps should look like the following:
Lesson 3-5
Part 3 - Call the test 12. Highlight the Website Security folder. 13. Create a new test called Test Authentication. 14. Click on the Design Steps tab 15. Click on the Call to Test button ( )
16. In the Select Test window, remove the check besides Show only Template Tests 17. Navigate the tree and highlight the Login with Parameters test and click OK 18. In the Called Test Parameters window, click on the drop down menu button ( in the Actual Value field for the UserID parameter 19. Enter training and click OK 20. Enter the value mercury for the Pwd parameter )
21. Click OK to close the Called Test Parameters window 22. Right click on the Description for Step 1, and select Called Test Parameters.... 23. Change the password to qwerty and click OK 24. Your Test Authentication test steps should look like the following:
Lesson 3-6
Activity 2 Run the Test

1. Select the Test Lab module 2. Click on the New Folder button ( ) 3. Name the new folder WebSite Testing and click OK 4. Click on the New Test Set button ( 6. Select the Execution Grid tab ) 5. Name the new test set Advanced Tests and click OK
7. Click on the Select Test button (
8. From the Test Plan Tree that opens to the right of the screen, select the Test Authentication test. 9. Click on the Add Tests To Test Set button ( )
Part 3 - Run Test 10. Click on the right end of the Run button ( ) to bring up the drop down
menu and select Run Manually (or Run with Manual Runner).
11. The Manual Runner window pops up. Click on the Begin Run button ( and click OK 13. There should be no errors in the test run, so pass each step by clicking on the Pass Selected ( ) button for each step
12. The Test AuthenticationRun dialog box opens. Verify the values of the parameters
14. Once all steps are marked as Passed under the Status field, click on the End Run button ( )
Lesson 3-7
Test Configurations
You can run tests for different use-cases of the application you are testing. Each use-case of a test is represented by a test configuration. A test configuration is a set of definitions that describe a specific use-case of a test. You can associate different sets of data for each test configuration. Working with test configurations enables you to run the same test under different scenarios. When creating a test, by default, a single test configuration is created. This test configuration is created with the same name as the test. Using the Test Configurations tab of the Test Plan module, you can create as many additional test configurations as needed. You associate a test configuration with data defined in the Parameters tab of the Test Plan module. You can associate different data with each test configuration. When creating coverage, instead of covering each requirement only at the level of the test, you can link a requirement to a test configuration. Associating test configurations with requirements provides finer granularity for requirements coverage by enabling coverage by different use-cases of a test. After creating coverage, you define a test set in the Test Lab module. A test set can include any or all of the test configurations defined for a test, or it can include test configurations based on requirement coverage. When you run a test set, the parameter values are retrieved from the data resource according to the settings defined for each test configuration.
How to Work with Test Configurations 1. Define tests with test parameters in the Test Plan module 2. Define test configurations 3. Define a test set 4. Add test configurations to a test set 5. View results
Lesson 3-8
Instructor-Led Demo
1. Add parameters
2. Add Test Configuration
3. Link Test Configurations to a Requirement
Lesson 3-9
Activity Summary
Prerequisites

You should know how to create tests with parameters. You should know how to add a test set and include tests
Test Plan
Create a test with parameters Add test configurations
Test Lab
Use test configurations Run the test configuration
L e s s o n 3 - 10
Activity 3 Create Test Configurations

1. In the Test Plan module, add a new folder and test using the following data: Folder name Configuration Examples Test Name Test Type Design Steps Create Investment account Manual 1. Sign in to the Personal Investors page 2. Open an investment account 3. Complete the account details
2. Add the following test parameters: Parameter name funds
3. Modify Step 2 to include the funds parameter as follows: Open an investment account using fund <<<funds>>>
tip: Don't type the word <<<funds>>>. Instead click on the Insert Parameter button and select funds from the list of parameters.
L e s s o n 3 - 11
4. Click on the Test Configurations tab. 5. Click on the New Test Configuration button.
6. In the New Test Configuration window, type "Capital Value" and press OK. 7. With the new configuration created, select the Data tab.
8. Click in the Actual Value field, and click on the dropdown arrow to open the data entry window.
9. In the data entry window, type "Capital Value" and press OK to close the window.. 10. Repeat the above steps to create two additional configurations: Configuration Name Precious metals US Growth Data Precious Metals and Mining U.S. Growth
L e s s o n 3 - 12
11. Delete the default configuration "Create Investment". You should have only 3 configurations.
Part 2 Run the test configurations 12. Select the Test Lab module. 13. Choose a folder (or create a new one) and add a new test set called "Configurations" 14. In the Execution Grid tab, click Select Tests. 15. locate the "Create Investment Account" test and add it to the test set. Notice that it adds all 3 configurations as test instances. 16. Run the Run menu, select Run Manually
17. Click Begin Run. 18. Pass Step 1 19. On Step 2 notice that the <<<funds>>> parameter has been replaced with the data value. 20. Pass all the steps and press End Run to complete the test execution.
21. Repeat the above steps to run the remaining two tests instances.
L e s s o n 3 - 13
Activity 4 Optional Create Additional Test Configurations

1. Create and run test configurations using the following data: Tests
Folder name Test Name Test Type Parameters Design Steps Configuration Examples Manage Accounts Manual 1. action 1. Log in to your account 2. Perform action <<<action>>> Configurations Name 401K Roll over Account Transfer Data Roll over a 401(k) plan Transfer an account
2. Challenge: Create two functional requirements and associate each one to each of the configurations. Choose any data for the requirements and associate each configuration in the Test Coverage tab. 3. Add the test to the Configurations test set. 4. Run the tests. Pass the 401K instance and fail the Account transfer instance. 5. Examine the results and the requirement status.
L e s s o n 3 - 14
Draft Runs
Overview
A test run whose outcome does not impact test statistics such as execution status or coverage. You can set a test run as a draft before or after the run, enabling you to try out tests while they are in development, or after they have been modified. When you change the draft run value, ALM recalculates tests statistics and updates status fields.
Work with Draft Runs

Before a test run. You can mark a test that you are running manually as a draft run before performing the test. In the Manual Runner: Run Details page, set the value of the Draft Run field to Y.
After a test run. You can mark any test run as a draft by modifying the Draft Run field for the run.
L e s s o n 3 - 15
Purge Draft Runs

Purge draft runs only Purges only runs marked as Draft Run
L e s s o n 3 - 16
Instructor-Led Demo
1. Perform a Draft Run
2. Purge a Draft Run
L e s s o n 3 - 17
Activity 5 Create a Draft Run

1. Navigate to the Test Lab, and select any manual test to run. 2. Write down the test name and test set you chose Test Set Test Name 3. In the Manual Runner window, set the Draft Run field to Y.
4. Click Begin Run to start the test. 5. Pass all the steps and end the test run.
L e s s o n 3 - 18
Activity 6 Purge the Draft Runs

1. Click on the Test Runs tab. 2. Select Test Runs > Purge Runs 3. In the Select Test Sets to Purge window, double click on the test set you used to run the test. This will move the test set to the Selected Test Sets view. 4. Click Next. 5. Select the following options:
Purge Draft Runs only From run older than: Number of runs per test to keep:
checked 0 days 0
6. Click Next. 7. Click Finish. 8. With the Test Runs tab open, click the refresh button
9. Verify that the test run has been removed.
L e s s o n 3 - 19
L e s s o n 3 - 20
Case Study 4 Advanced Reporting
Advanced Reporting
Case Study 4|1
Standard Reports
Quality Center provides you with analysis tools enabling you to analyze and display ALM data in various formats. Dashboard contains two modules: The Analysis View module and the Dashboard View module. The Analysis View module contains the analysis tree in which you organize all of your analysis items. Analysis items can be any of the following analysis types: graphs, project reports, Excel reports, and standard reports. Standard Reports can have several layers, or sub reports to them. For example, a Standard Report for Requirements can have a sub report showing the linked tests cases, or defects. Filters can be applied to the Standard Reports to grab only the data that is relevant to your report. This is handy in that a Standard Report without such filters can be massive in size.
Advanced Reporting
Case Study 4|2
Instructor Demos
1. Generating a Standard Report from module Notes
2. Use Filters and Sub Reports Notes
3. Create Report From Analysis View Notes
Advanced Reporting
Case Study 4|3
Activity 1: Standard Reports and Graphs

Part 1 Create Report for Requirements
1. Navigate to the Requirements module 2. From the View menu, select Requirement Details.
3. From the Analysis menu, select Reports > Standard Requirement Report.
4. Note the number of pages for the report.
5. Click the Add to Analysis Tree button. 6. In the New Standard Report window, select the Private folder and click the New Folder button.
7. Name the new folder as your student** account and click OK. 8. Click Save. 9. If you are not automatically transported to the Analysis View module, navigate there and select the newly created report.
Advanced Reporting
Case Study 4|4
10. Click on the Configuration tab.
11. Click the Filter button.
12. Mouse over the row for Req Parent and click the drop down menu.
13. In the Select Filter Condition window, expand the Requirements root folder and select the Mercury Tours Application folder. 14. Click OK twice. 15. Click the View tab and review the contents of the report. Note the number of pages now present in the report.
Part 2 Create Report For Test Cases

16. Select the student** folder you created. 17. Click the New Item drop down menu and select New Standard Report.
18. In the New Standard Report window, use the table below to complete the requirement information. Entity Tests Standard Report Type Test Plan Report Standard Report Name MT Test Cases 19. Click OK. Advanced Reporting Case Study 4|5
20. In the Configuration tab, click the Filter button.
21. In the Filter Tests window, select the Cross Filter tab.
22. Under Requirements, click the Filter radio button.
23. In the Cross Filter: Requirements window, click the drop menu for Req Parent.
24. In the Select Filter Condition window, expand the Requirements root folder and select the Mercury Tours Application folder. 25. Click OK. 26. Click the ellipsis button for the Type drop down menu.
27. Select MANUAL and click OK, followed by OK. 28. Click the Add Sub Report button.
29. In the Add Sub-Report window, select Design Steps from the Type drop down menu and click OK. 30. Click the View tab and review the contents of the report. Note all of the tests cases displayed are MANUAL test cases and their Design Steps are displayed as well.
Advanced Reporting
Case Study 4|6
Activity 2: Challenge
Defects Defects
1. Use the table below to create Two more reports. Entity Standard Report Type Standard Report Name Runs Runs Failed Test Runs Open Defects
Filter Status = Failed Status = Open Cross Filter With Req Parent = Mercury Tours Application
Sub Report Parent Test Source Test/Coverage Requirements
2. Hint: The Failed Test Runs report should resemble the following:
3. Hint: The Open Defects report should resemble the following:
Advanced Reporting
Case Study 4|7
Project Reports
Project Reports are a new feature in Application Lifecycle Management 11. They are generated through the Analysis View module, enableing you to design and generater a wide veriety of comprehensive reports. Usuing templates designed by the project administror for potentially each ALM entitiy, users can generate reports that follow company standards with regards to layout conventions and formating. Templates can be created using Microsoft Word, however this particiular feature is availible only to those running Word 2007 or 2010.
Advanced Reporting
Case Study 4|8
Instructor Demos
4. Generating a Project Report Notes
5. Use Filters and Sub Reports Notes
6. Create Custom Templates Notes
Advanced Reporting
Case Study 4|9
Activity 1: Create Project Report
1. Ensure you are in the Analysis View module. 1. Under the Private folder, click on the student**folder you created earlier. 2. From the menu, select Analysis > New Project Report.
3. In the New Project Report window, type Requirements 4. Click OK. 5. In the Configuration tab, change the Output Format: to Doc.
6. Click on the Edit Document Field Values button.
7. In the Edit Document Template Field Values window, use the table below to change the following values: Field Name Field Value Project Mercury Tours Title1 Custom User Requirements Summary This is my custom report Author You Name 8. Click OK. 9. Click on the Add Report Section button.
10. In the Add Report Section window, change the Type field to Requirements and click OK. 11. Click on the Generate Report button. 12. Review the report and close Microsoft Word. Note: if Microsoft Word is not installed, try creating an HTML report.
Advanced Reporting
C a s e S t u d y 4 | 10
Activity 2: Enhance Project Report

1. Click on the Filter button.
2. Set the Req Parent filter to the Mercury Tours Application folder.
3. Select the Document node.
4. Click on the Add Report Section button.
5. In the Add Report Section window, click the Type drop down menu and select Tests, followed by OK. 6. Click the Filter button. 7. In the Filter Tests window, select the Cross Filter tab.
7. Under Requirements, click the Filter radio button. 8. In the Cross Filter: Requirements window, set the Req Parent filter to the Mercury Tours Application folder. 9. Click OK. 10. Click the ellipsis button for the Type drop down menu.
11. In the Select Filter Condition window, select MANUAL and click OK. 12. Click OK and verify the Filter box resembles the following:
Advanced Reporting
C a s e S t u d y 4 | 11
13. Ensure the Tests node is selected and click the Add Report Section button.
14. In the Add Report Section window, click the Type drop down menu and select Design Steps, followed by OK. 15. Click the Project Template drop down menu and select Design Steps Tabular Template green by Alice.
16. 17. 18. 19.
Select the Tests node and click the Add Report Section button. In the Add Report Section window, click the Type drop down menu and select Defects, followed by OK. Select the Document node. Change the Output Format to PDF.
20. Click the Generate button. 21. Navigate through the report and verify the Design Steps template looks slightly different in terms of style from the rest of the report.
22. Close the PDF.
Advanced Reporting
C a s e S t u d y 4 | 12
Activity 3 Sharing Graphs

Part 1 Create Public Graph
1. 2. 3. 4.
Ensure you are in the Analysis View. Select any of the graphs created in the previous activity. From the module menu, select Edit > Share Analysis Item. In the Share Analysis Item window, select Copy Analysis Item Public URL.
5. Click OK.
Part 2 - View Public Graph

6. Open a browser, clear the address bar right-click and select paste, followed by ENTER. 7. Review the graph data. Note the Last Generated: field as to how current the data is. 8. Close the browser.
Part 3 View User Authenticated Graph

9. Repeat the steps in Part 1 to create another public graph, except this time select the option Copy Analysis Item URL (Authentication Required). 10. Open a new browser, clear the address bar right-click and select paste, followed by ENTER. 11. When the Application Lifecycle Management window appears, enter your login credentials for your project and click Authenticate. 12. Review the graph and close the browser.
Advanced Reporting
C a s e S t u d y 4 | 13
Live Analysis Graphs

Live Analysis graphs enable you to create and display a dynamic graphical representation of data related to test plans and test sets. You use Live Analysis graphs to view data that relates to a test subject folder or test set folder. Each time that you click on a test subject folder or test set folder, the graphs change to reflect the data related to your selection. About Generating Live Analysis Graphs You create Live Analysis graphs to provide a dynamic quick visual overview of all the tests in a folder, or test sets in a test set folder. After you have created a graph, you can access it by choosing the Live Analysis tab when you are in the tree view of the Test Plan or Test Lab modules. When you update a record in the folder, the data change is reflected in the graph, without the need for the graph to be manually regenerated. Live Analysis graphs differ from the graphs described in Generating Graphs, in that you do not have to recreate a graph to view data that has changed. In addition, the layout and settings of the graph are preserved when you select another folder in the same module. This enables you to view the same graphical analysis of different folders without the need to recreate the graphs. Creating Live Analysis Graphs You can create Live Analysis graphs for test subject folders and test set folders. For more information on creating Live Analysis graphs for test subject folders, see Creating Test Subject Folder Graphs.
Advanced Reporting
C a s e S t u d y 4 | 14
Instructor Demos
8. Live Analysis graph. Notes
Advanced Reporting
C a s e S t u d y 4 | 15
Activity 1: Add a Live Analysis Graph

1. Open the ALM_demo project. 2. Select the Test Plan module. 3. Highlight the Flight Reservation folder 4. Select Live Analysis tab. 5. Click on the Add Graph link. 6. Select the following options Graph Type Summary Graph
Group By X-axis
Status Designer
23. Click on the second Add Graph link. 24. Select the following options Graph Type Group By Progress Graph Execution Status
25. Review the second graph. 26. Delete the second graph, and add a new Summary Graph using Status as the X-axis and Group By value. 27. Starting with the Flight Reservation folder, note how many tests are in the Ready state in each folder Folder Flight Reservation Book Flight Flight Confirmation Flight Cost Flight Finder Select a Flight # of tests in "Ready" State
Advanced Reporting
C a s e S t u d y 4 | 16
Activity 2: Test Set Live Analysis Graphs

1. Select the Test Lab module. 2. Highlight the Mercury Tours Web Site folder. 3. Select the Live Analysis tab. 4. Click on the Add Graph link. 5. Select the following options Graph Type Summary Graph
Group By X-Axis
Tester Test Set: Name
6. Click on the Set Graph Appearance button
7. Update the following fields Tab Titles Appearance Bar Parameters Field Graph Title 3D Graph Mark Position New Value Tests by Test Set Uncheck Middle
8. Click on the bars in the graph to drill down to the details 9. Close the Drill down results. 10. Select different folders and verify the graphs are being updated
Advanced Reporting
C a s e S t u d y 4 | 17
Document Generator
The Document Generator enables you to create a hard copy of the data contained in a Quality Center project. You create the document by performing the following tasks: 1. Set document format. 2. Specify document content. 3. Generate and edit the document. First, you set formatting instructions in order to determine how your project document will look. For example, you can print a company logo on each page of the document, create a table of contents and an index, and place test scripts and file attachments in the text of your document. Next, you specify the project data that will be presented in your document. You can select information from the Quality Center modules. For example, from the Test Plan module, you can choose which folders and tests to include from the test plan tree, sort this data alphabetically or in a custom sort order, and display the data as lists or tables. After you have set the formatting instructions and specified the document's content, you can save the document settings as a favorite view for future use and generate the document. After document generation is complete, you can view and edit the document in Microsoft Word. The information for each module that you select is printed in a separate chapter of the project document
Launching the Document Generator

1. To start the Document Generator, click the Tools button on the upper-left of the Quality Center window. Choose Document Generator. The Document Generator opens. 2. Before you can generate a document, you set formatting instructions that control how the document will look and what is included in the cover page. 3. To set formatting instructions, open the Document Generator. By default, the Document link is selected in the Document Generator tree and he Document Settings tab is displayed. 4. After you set formatting instructions and specify project data, you can generate the project document. You save the document as a Microsoft Word file. 5. To generate a project document: a. Click the Full Document button. The Save As dialog box opens. b. In the Save As box, set the location for the document in your network file system. c. In the File name box, assign the document a name. d. Click the Save button.
Advanced Reporting
C a s e S t u d y 4 | 18
6. Quality Center begins generating the document and a dialog box displays document creation progress. When the process is complete, Microsoft Word opens and displays the document.
Instructor Demos
4. Create a report using the Document Generator Notes
Advanced Reporting
C a s e S t u d y 4 | 19
Activity 1: Generate a Document

1. Ensure you are logged into the ALM_Demo project. 2. From the Tools menu, select Document Generator 3. In the Document Generator window, use the table below to fill in the required information: Title Mercury Tours Phase 1 Name (Your Name) Initials (Your Initials) 4. Click the Checkbox beside Requirements and select the Requirements node.
5. Click the Selected radio button, followed by Filter & Sort.
6. Set the Req Parent filter to the Mercury Tours Application folder.
7. Checkmark the first two graphs at the bottom of the Document Generator window.
8. Use the table below to click the required check boxes: Test Plan Subject Tree Subject Tests 9. The Document Generator tree should resemble the following:
Advanced Reporting
C a s e S t u d y 4 | 20
10. Ensure the Subject Tests node is selected. 11. Click the Design Steps check box.
12. Click the Selected radio button, followed by Filter and Sort. 13. In the Filter Tests window, select the Cross Filter tab.
14. Set a Requirement filter for the Req Parent to the Mercury Tours Application folder.
15. Set the Type filter to MANUAL test cases and click OK. 16. Click the Full Document button. 17. Save the document as MTours Phase 1 to the Desktop. 18. Review the contents and close Microsoft Word.
Advanced Reporting
C a s e S t u d y 4 | 21
Excel Reports
You can export Quality Center data to Microsoft Excel. This enables you to analyze your data using any of the capabilities available in Excel. An Excel report consists of a set of data defined by SQL queries on the project database. You can also run a Visual Basic script on the extracted data to process and analyze the data. Once you have added an Excel report in the Dashboard module, you define which project data you want to include in the report. This data is defined by creating SQL queries. You can create multiple queries for an Excel report. When you generate the report, the results of each query are displayed in separate Excel worksheets. For advanced users, they can enter the SQL query directly in the Query tab You can include parameters in the SQL queries for your Excel reports. For each query parameter, you can assign a default value. When you generate the report, you are prompted to enter the value of the parameter, or confirm the default value. Alternatively, you can choose to always use the default value, without being prompted by Quality Center each time you generate the report. You can create a Visual Basic script to run after the data is exported to Excel. You use this script to manipulate the data in Excel. For example, you can present requirements data in Excel as a pivot table, you could perform calculations on defects data to calculate the average time an open defect takes to be fixed, or you could create a graph based on exported data. Before you run a post-processing script, you must configure your Microsoft Excel security settings so that Excel can run the script.
Creating Excel Reports

1. In the Dashboard module, click the Analysis View tab. 2. In the analysis tree, select the folder under which you want to add the Excel report. 3. Click the New Item button and select New Excel Report. The New Excel Report dialog box opens. 4. Under Excel Report Name, type a name for the Excel report. 5. Click OK. The Excel report is added to the analysis tree. 6. Click the Details tab. Add or update the details. 7. Create one or more SQL queries to define the data that is extracted. 8. Optionally, create a post-processing script that runs in Excel after the data is exported. 9. Export the data to Excel.
Advanced Reporting
C a s e S t u d y 4 | 22
Instructor Demos
1. Create an Excel report Notes
2. Creating SQL queries Notes
Advanced Reporting
C a s e S t u d y 4 | 23
Activity 1 - Creating an Excel Report

1. In the Dashboard module, click on the Analysis View tab. 2. In the analysis tree, select the "Training" folder 3. Click the New Item button
This activity will generate an Excel report to display the count of the Requirements by the status.
and select New Excel Report. 4. The New Excel Report dialog box opens. 5. Under Excel Report Name, type Requirements Coverage 6. Click the Query Builder button. The Excel Report Query Builder window opens. 7. In the Query1 tab, type the following SQL queries to extract the requirements coverage data: SELECT REQ.RQ_REQ_STATUS as Status, Count( REQ.RQ_REQ_STATUS ) as Num FROM REQ GROUP BY REQ.RQ_REQ_STATUS 8. On the toolbar, click TEST QUERY to test the SQL query syntax. The query results appear in the Query Results tab at the bottom of the window.
9. Click OK to close the Excel Report Query Builder window 10. Click the Generation Settings tab. 11. Change the status to Ready. 12. Click the Generate button 13. Type a name for your Excel report and click SAVE to save the report on your computer. 14. The PROGRESS dialog box appears. After the process is complete, the Excel report appears. Close Excel.
Advanced Reporting
C a s e S t u d y 4 | 24
Activity 2 - Create an Excel Report

2. The report will have these characteristics Excel Report Name SQL Execution Status Summary
SELECT TEST.TS_EXEC_STATUS as Execution_Status,
This activity will generate an Excel report to display the count of the Test Execution status. 1. Create an Excel report to display a summary of the Execution status of the tests.
Count( TEST.TS_EXEC_STATUS ) as Num FROM TEST /*Test*/ GROUP BY TEST.TS_EXEC_STATUS /*Test.Execution Status*/
3. Create the query in the Query Builder window, and test the query before generating the report. 4. Set the status of the report to Ready. 5. Generate the report.
Advanced Reporting
C a s e S t u d y 4 | 25
Activity 3 - Advanced Excel Report

Part 1 - Create an Excel report
1. In the Analysis tree, select the Training folder 2. Click the New Item button and select New Excel Report. 3. The New Excel Report dialog box opens. 4. Under Excel Report Name, type Defect Status 5. Click OK. The Excel report is added to the Analysis tree. 6. Click the Details tab.
7. Add the following description: Description This report will include two queries to display the defect status and description.
Part 2 - Creating SQL Queries

8. Select the Configuration tab. 9. Click the Query Builder button. The Excel Report Query Builder window opens. 10. In the SQL pane, enter the asterisk next to SELECT. The first line should be read: SELECT * 11. Move the cursor to the end of FROM. 12. Scroll the Entities View until you find the Defect (BUG) entity. Select it.
13. Click the Add Entity to Query button.
14. The SQL query should look like: SELECT * FROM BUG /*Defect*/
Advanced Reporting
C a s e S t u d y 4 | 26
15. Click the Test Query button.
16. You should see the results in the Query Results pane. Note: You may need to resize some of the panes.
Note: The Test Query button displays a max of 10 queries. 17. Click the Add Query button.
18. A new tab, Query 2, will be added to the SQL Pane
19. In the Entities View, expand the Defect (BUG) entity by clicking on the plus sign next to the table. 20. Select the value Defect ID (BG_BUG_ID) 21. Click the Add Entity to Query button. 22. Add a "," (comma) at the end of the first line. (without the double quotes)
SELECT BUG.BG_BUG_ID /*Defect.Defect ID*/
23. Add a blank line after the SELECT ... line, and position the cursor on the blank line. 24. In the Entities Pane, select Description (BG_DESCRIPTION) 25. In the drop-down menu of the Add Entity to Query button (the downward pointing arrow to the right of the button), select Add Entity to Query with Entity Title as Alias.
26. Move the cursor to the end of FROM. Advanced Reporting C a s e S t u d y 4 | 27
27. Scroll the Entities Pane until you find the Defect (BUG) entity. Select it.
28. Click the Add Entity to Query button.
29. Your SQL should look something like the following: SELECT BUG.BG_BUG_ID /*Defect.Defect ID*/,
BUG.BG_DESCRIPTION as Description FROM BUG /*Defect*/
30. Click the Test Query button. 31. Verify that the Query Results is populated with the results from the query.
Part 3 - Adding Query Parameters to the Parameter List

32. Select the Query Parameters tab
33. In the Query Parameters tab, click the New Parameter button.
34. The New Parameter dialog box opens. In the Parameter Name box, type BG_STATUS_PARAM In the Default Value, type Open Check Global Parameter In the Description, enter Parameter for the field BG_STATUS
35. Click OK to close the dialog box. The parameter is added to the Parameter list.
Advanced Reporting
C a s e S t u d y 4 | 28
Part 4 - Adding a Parameter to an SQL Query

36. Make sure the Query1 tab is selected. 37. Enter a blank line after the FROM statement. 38. On the blank line, type: WHERE BUG.BG_STATUS = 39. From the parameter list (Query Parameters), select the parameter you added earlier. 40. Click the Add Parameter to Query button. 41. Your SQL query should look like the following: SELECT * FROM BUG /*Defect*/ WHERE BUG.BG_STATUS = @BG_STATUS_PARAM@ 42. Click the Test Query button. Notice in the Query Results, the BG_STATUS column shows all Open defects. 43. Click the Run Query button. A Report Parameters dialog opens up. In the Value column, change 'Open' to 'Reopen'. Click OK. Notice the different results.
44. Click OK to close the Excel Report Query Builder window.
Part 5 - Post Processing Scripts

45. Select the Configuration tab. Under it, click the Post-processing tab. 46. Enter the following code in the Script Editor box: (note some of the code will already be there)
Sub QC_PostProcessing() Dim MainWorksheet As Worksheet ' Make sure your worksheet name matches! Set MainWorksheet = ActiveWorkbook.Worksheets("Query1") Dim DataRange As Range Set DataRange = MainWorksheet.UsedRange ' Now that you have the data in DataRange you can process it.
'To demonstrate post-processing change the first cell
DataRange.Range("A1") = "DEFECT ID"

End Sub
Advanced Reporting
C a s e S t u d y 4 | 29
47. To run the post-processing script after the data is exported to Excel, select Run post-processing. If you do not select this option, the script is not run when you generate the report.
Part 6 - Running Excel Reports

48. Select the Configuration tab. Under it, click the Generation Settings tab. 49. To instruct Quality Center to open the report in Excel after it is generated, select Launch report in Excel. 50. In the Status box, change the status to Ready. 51. Click the Generate button to generate the Excel report 52. Save the report on the Desktop. 53. Once the report is generated, open up the Excel document. 54. Go to worksheet Query 1. 55. Verify cell A1 has the value DEFECT ID". 56. Review the spreadsheet and then close Excel.
Advanced Reporting
C a s e S t u d y 4 | 30
Activity 4 - Requirements Excel Report (Optional)

1. Create an Excel report with the following characteristics.
Query 1
Rename the Query "RequirementsInfoWithParentID" SELECT REQ.RQ_FATHER_ID as Parent_Folder, REQ.RQ_FATHER_ID as Parent_Folder_ID, REQ.RQ_REQ_NAME as Requirement_Name, REQ.RQ_REQ_ID as Requirement_ID FROM REQ Where REQ.RQ_NO_OF_SONS = 0
Query 2
Rename the Query "RequirementFoldersWithChildren" SELECT REQ.RQ_REQ_ID as Folder_ID, REQ.RQ_REQ_NAME as Folder_Name From REQ where REQ.RQ_REQ_ID in (select REQ.RQ_FATHER_ID from REQ)
Post Processing Code (listed on next page)

Make sure the Run post-processing checkbox is selected:
Advanced Reporting
C a s e S t u d y 4 | 31
Sub QC_PostProcessing() Dim lookupSheet as Worksheet set lookupSheet = ActiveWorkbook.Worksheets("RequirementFoldersWithChildren") dim countFolders, countReqs countFolders = lookupSheet.UsedRange.Rows.Count Dim mainSheet as Worksheet set mainSheet = ActiveWorkbook.Worksheets("RequirementsInfoWithParentID") countReqs = mainSheet.UsedRange.Rows.Count mainSheet.Cells(1,1).Value="Parent Folder" Dim vlFormula as string for row = 2 to countReqs vlFormula = "=VLOOKUP(B"&row vlFormula = vlFormula &",RequirementFoldersWithChildren!A2:B" vlFormula = vlFormula & (countFolders + 1) vlFormula = vlFormula &",2,FALSE)" mainSheet.Cells(row, 1).Value = vlFormula next 'change focus to RqequirementsInfoWithParentID sheet ' and autofit columns for readability mainSheet.Activate dim countColumns countColumns = mainSheet.UsedRange.Columns.Count for col = 1 to countColumns mainSheet.Columns(col).EntireColumn.AutoFit next End Sub
Advanced Reporting
C a s e S t u d y 4 | 32
Case Study 5 Requirements Traceability
Requirements Traceability
Case Study 5|1
Overview
Requirements traceability defines a relationship between two or more requirements. When analyzing the impact of a change proposed in a specific requirement, the traceability links indicate the other requirements that the change might affect. You can add traceability links to and from a selected requirement. Trace from links indicate requirements that affect a selected requirement. Trace to links indicate requirements that are affected by a selected requirement. When a requirement changes, HP Application Lifecycle Management (ALM) can alert the affected requirements.
Traceability Matrix
The traceability matrix enables you to determine the extent of relationships between requirements and other requirements, and between requirements and tests. It helps you verify that all requirements are met, and identify changes to the scope of your requirements when they occur. The traceability matrix lists source requirements and their associated requirements and tests. The total number of relationships is listed for each source requirement. A low value may imply that the source requirement is not associated with enough requirements or tests. A high value may imply that the source requirement is too complex and can perhaps be simplified. A zero value indicates that no relationship exists.
Case Study 5|2
Instructor-Led Demo
1. Define traceability links.
2. View traceability impact.
3. View Traceability Matrix.
Case Study 5|3
Activity Summary
Requirements
Define traceability links. View traceability impact. View Traceability Matrix.
Case Study 5|4
Activity 1 Creating Traceability Links

1. 2. Select the Requirements module. Select View > Requirements Details. 3. The table below describes the various website page requirements and UI standards that they depend on.
Documentation Help Screens Insurance Page Mortgage Page X X X Forms Navigation X X X X Reports
For example, the Insurance page depends on the Forms, Navigation and Reports standards, while the Home page is only affected by the Navigation standards. 4. Select requirement CIBC Website Development > Help Screen.
5.
Navigate to the Requirements Traceability tab.
6.
Click on the Add Requirement Traceability button On the right hand side, a Requirements tree folder will be shown.
Case Study 5|5
7.
Locate the CIBC Standards > User Interface standards > Documentation requirement.
8. 9. 10. 11.
Click the Add To Traceability button to add it to the Tools requirement (
).
Locate the CIBC Standards > User Interface standards > Navigation requirement. Click the Add To Traceability button to add it to the Tools requirement ( Your Requirements Traceability should look like the following: ).
12.
Repeat the above steps to set up the relationship defined in the table above for the Insurance Page and Mortgage Page requirement. Verify the relationships are set up correctly by viewing the Impact Analysis for the CIBC Standards requirements. Look in the Trace To links area.
13.
Case Study 5|6
Activity 2 View the Traceability Matrix

1. 2. In the Requirement module, select View > Traceability Matrix. Click on create a configuration. 3. In the Configure Traceability Matrix window, limit the matrix to requirements authored by user "training".
Hint: Click on the filter and select the Author field.
4.
In Filter by linked requirements, identify the requirements that have an impact on the defined source requirements.
Case Study 5|7
5.
Click OK to close the Configure Traceability Matrix window. The traceability matrix grid displays the source requirements and number of traced from requirements. Click Generate Traceability Matrix.
6.
7. 8.
When prompted, enter File name UI Standards and click Save. The saved file will resemble the following example.
Case Study 5|8
Case Study 6 Requirements Risk
Requirement Risk
Case Study 6|1
Discussion Requirement Risk

Be prepared to review this with the class. Time: 20 min and then class review.
1. You want to assign your most important requirements to be tested by your most experienced testers. Using the table below, make a list of criteria you would use to differentiate the importance of a requirement. A suggestion is included in the table.
Criteria Change type
Scale New Feature Changed Feature Unchanged Feature
Requirement Risk
Case Study 6|2
Requirement Risk
Calculating Requirement Risks About Calculating Requirement Risks
Risk-based quality management can assist you in determining testing strategy for your requirements.
When planning how to test your requirements, you generally do not have unlimited resources available and are not able to fully test every requirement. You must make compromises and only partially test requirements that have low criticality to the business, or those that have only a minor risk associated with their implementation. The risk-based quality management feature enables you to calculate at which level to test each requirement, based on the nature of the requirement and the resources you have available. You can then plan your testing process based on these recommendations. Each requirement type can be enabled for risk-based quality management. Each requirement type with risk-based quality management enabled can support either risk analysis which is referred to as an analysis requirement, or an individual risk assessment which is referred to as an assessment requirement. An analysis requirement is a requirement belonging to a type that represents higher levels in the requirements tree hierarchy, such as the Folder type. You perform risk analysis on an analysis requirement based on the assessment requirements under it in the requirements tree. The risk results of multiple assessment requirements are aggregated to give an overall risk analysis which can then be used to determine testing effort and test strategy. An assessment requirement is a requirement belonging to a type that represents requirements that are children of analysis requirements and at a lower level in the requirements tree hierarchy. Assessment requirements under a particular analysis requirement form the basis for risk analysis on that analysis requirement. You can work with risk-based quality management in the Requirement Details view of the Requirements module. You can also work with risk-based quality management in the Risk view of the Requirement Details dialog box.
Requirement Risk
Case Study 6|3
Instructor-Led Demo
1. Complete Activity 1 before proceeding with any demos
2. Set Requirement risks
3. Perform Risk Analysis
Requirement Risk
Case Study 6|4
Activity Summary
Requirements
Create new requirements Perform Risk Analysis
Requirement Risk
Case Study 6|5
Activity 1 Creating new Requirements

Requirement Name Parent Windows Fundamentals Child Perform primary functionality and maintain stability Child Any kernel-mode drivers that the application installs must pass verification testing Child Any device or filter drivers included with the application must pass Windows testing Child Perform Windows version checking correctly Parent Install_Remove Child Do not attempt to replace files that are protected by Windows File Protection Child Migrate from earlier versions of Windows Child Do not overwrite non-proprietary files with older versions Child Do not require a reboot inappropriately 2. You Requirements tree should resemble the following Folder Functional Functional Functional Functional Folder Functional Functional Functional Functional
1. In the Requirements module create a new folder called User Interface Requirements and add the following requirements Requirement Type
Requirement Risk
Case Study 6|6
Activity 3 Assigning Risk Value

1. Select the Requirements module 2. Ensure Requirement Details is selected from the view menu 3. Select the Risk Assessment tab
4. Select the Assessment Questions tab
5. For each child requirement, select Business Criticality, Failure Probability, and Functional Complexity tabs and enter values for each Criterion (for this activity any value will suffice).
6. Navigate to the parent requirements and in the Risk Analysis tab and click on the Analyze button ( )
7. Identify the three most critical requirements listed in the graph (Note this will depend on the values you chose for the criterion)
1 2 3
Requirement Risk
Case Study 6|7
Requirement Risk
Case Study 6|8
Case Study 7 Business Models
Business Process Models
Case Study 7|1
One of the most important aspects of Quality Center is its ability to tie in all departments that are potentially in a company into a single cooperative workflow database. All of the different modules within Quality Center are built around tying everything and everyone together in the process of software development as to ensure a cohesive, efficient team. In the Business Components module, the user has the ability to import a business process model and integrate it into either the requirement or test entities. As a result, the coverage of the requirement or test gets expanded to include the business model. When a business model is imported into Quality Center, each block of the flow is given its own entity in the tree structure in order to attach details such as fields, descriptions, attachment and linkage to that single item. Items in the business model such as decisions are not given their own entity within Quality Center. As well each parent entity of the Business Model can be linked to a baseline.
The user has the ability to view the details of any part of the business model. By right clicking on any item in the flow chart, the user can bring up the details of that specific part of the business model.
Case Study 7|2
From the Model Activity Details window, the user can also link the item to any requirement or test
After a business model in imported into Quality Center, if the user navigates to the Requirements module, they will notice the Business Model is also visible in the Requirements tree structure
Case Study 7|3
Instructor-Led Demo
1. Import A Business Model
2. Tie The Model To Entities
Case Study 7|4
Activity Summary
Business Models
Analysis Business Model
Import a BPM file into Quality Center Tie Business Model to Requirements and Tests View Coverage of Business Process Models
Case Study 7|5
Activity 1 Import a Business Model

Part 1 Create Tree Structure 1. Navigate to the Requirements module. 2. Select the Requirements root folder and create a new folder called Process Complaint. 3. Click the New Requirement button and use the table below to create several new requirements. Requirement Name Process Notification Update Vendor Qualifications Create Complaint Perform Automatic Creation Of Notification Requirement Type Functional Functional Functional Functional
4. The Requirements tree should resemble the following:
Part 2 Convert Requirements to Test Cases 5. Right-click on the Process Complaint requirement folder and select Convert To Tests
Case Study 7|6
6. In the Step 1 of 3: Choose an automatic conversion method window, select Convert lowest child requirements to tests and click Next. 7. Select the Process Notification node.
8. Click the Exclude from Conversion button and click Next.
9. Click Finish, followed by OK in the Information dialog box. 10. Navigate to the Test Plan module and verify the test cases were successfully created.
Part 3 Import Business Model 11. Navigate to the Business Models module
12. Ensure the top folder Models is selected and create a new folder called Cloud DB.
13. Click the Import Model button.
14. In the Import Models window, click the ellipsis button.

Business Process Models Case Study 7|7
15. Click the My Documents button and select Sample BPM.xml and click Open. 16. Click the Import button.
17. In the Importing Models window, click OK.
Case Study 7|8
Activity 2: Link BMP To Entities

Part 1 Create Paths
1. Select the Process complaint node. 2. Click the New Path button. 3. In the New Model Path window, use the table below to fill in the required information: Name Path Path 1 2 > 4 > 6 > 8 > 9 > 10 > 11 > 12 > 13 > 20 > 23 > 27 > 30
4. Click OK. 5. Click the Refresh button.
Part 2 Create Linkage

6. Select the Linkage tab.
7. Ensure the Requirements sub-tab is selected.
8. Click the Select Requirements button. 9. In the Requirements tree, select the Process Complaint folder and click Add To Linkage.
10. Select the Create complaint node. 11. Select the Linkage tab.
Case Study 7|9
12. Expand the Process Complaint requirement folder and select the Create Complaint requirement, followed by Add To Linkage.
13. Select the Tests sub-tab.
14. Click the Coverage drop down menu and select Linked Requirement Coverage.
Part 3 Analyze Linkage

15. Click the View menu and select Model Analysis.
16. Select the Quality Analysis tab. 17. Review the graph information and note the Test Cases that are linked to the Create complaint node of the business model.
C a s e S t u d y 7 | 10
Case Study 8 HP Sprinter
HP Sprinter
Case Study 8|1
Sprinter
Sprinter allows the user to access the Quality Center server and download the details of a test (such as steps, parameters, descriptions and expected results) and run the test on any machine with Sprinter installed. Depending on the settings of a given project, if a manual test is launched within Quality Center, Sprinter will automatically load. Otherwise Sprinter can be launched from the Start Menu or any other shortcut medium that is present. While Sprinter may have some automation features, it does not turn a manual test into an automated one. With Sprinter there are simply more features enabled to the user in order to provide better documentation for the results of the test run. The automation features can be turned on or off depending if Power Mode is enabled. If Power Mode is turned off, the user will not have access to these features. Before a test is run, the user has the ability to review Test Steps, General Settings and Parameters before executing the test. They also have the abilty to export, print or E-Mail the Test Steps.
HP Sprinter
Case Study 8|2
Instructor-Led Demo
1. Overview of HP Sprinter
2. Run manual test with Power Mode off, show Defect creation
3. Return to Quality Center and show details that are now attached to test entity
HP Sprinter
Case Study 8|3
Activity Summary
Sprinter
Select the tests to run Run test with Sprinter, capture screens, use annotations Run test and open smart defect Modify Smart Defect settings Run another test with Sprinter, set up a defect reminder Launch Sprinter results viewer
HP Sprinter
Case Study 8|4
Activity 1 Select the Tests

Connection settings.
1. If you are logged into ALM, log out of the project and close any open browser windows.
2. Start HP Sprinter by clicking on the shortcut on the desktop or from the Start menu. 3. Click on the HP ALM button (in the top right corner) to configure your HP ALM
4. In the HP ALM Connection window, enter your credentials to log into ALM. Begin by entering the Server information and then by entering the Domain and Project information. 5. To choose the tests you will run, click the Open button in the Run Setup area.
6. The Open window is a view of the Test Set tree. Expand the Root folder and any child folders until you see CIBC.com/Sanity Tests test set and the First Contact Website/Website Forms test set.
7. Expand CIBC.Com and then select all the tests by clicking on the checkbox beside each test. 8. Expand First Contact Website and then select all the tests by clicking on the checkbox beside each test.
HP Sprinter
Case Study 8|5
9. When all the tests are selected, press the Open button. The tests will be displayed in the Tests List.
10. Review the steps in the test by clicking on the Steps link. Note: Just read the steps, DO NOT attempt to complete the steps.
HP Sprinter
Case Study 8|6
Activity 2 Run one Test

1. Make sure Power Mode is turned off. 2. Select the test Learn More About Credit Cards. 3. Right click on the test and select Run This Test Only.
4. Begin following the instructions in the Steps tool window. After completing step 1 click on the Pass Selected Steps button ( successfully. 5. Follow each step and complete the test. Remember to pass each step as you complete it. 6. When the test is complete, click on the End Run button from the Run Control tool bar. ) to indicate that the step was completed
7. When the main Sprinter screen is displayed, review the results by clicking on the Run Summary.
HP Sprinter
Case Study 8|7
Activity 3 Add a Defect Reminder

1. Make sure Power Mode is turned off. 2. Select the test Travel Insurance. 3. Right click on the test and select Run This Test Only. 4. Begin following the instructions in the Steps tool window. 5. Complete steps 1 and 2, passing each step. Before completing step 3, you notice that links for the different insurance products are not in the correct sequence on the page. You want to add a defect reminder so that you can add a defect once you verify what the correct sequence should be. 6. From the Steps toolbar, select Add Defect Reminder.
7. In the Defect Reminder window, type the following description: Verify the correct sequence on the page for the insurance products. 8. Click OK to save the Defect Reminder. 9. Complete the rest of the test. Remember to pass each step as you complete it. 10. When the test is complete, click on the End Run button from the Run Control tool bar. 11. When the Sprinter window appears, click on Defect Reminders (1) from the Results group. 12. Verify that the Defect Reminder is correct. 13. Click on Submit Defect.
. 14. Click Submit Defect again, and create a defect choosing any options. Remember to supply values for all the mandatory fields.
HP Sprinter Case Study 8|8
Activity 4 Run a test and Open a Defect

1. Make sure Power Mode is turned off. 2. Select the test Loan Calculator. 3. Right click on the test and select Run This Test Only. Part 1 Run the steps 4. Follow each step and complete the test. Remember to pass each step as you complete it. DO NOT end the test. 5. On Step 7 in the test, notice the Expected Result: links for Payment Amount and Total Interest.
6. Click on the words No Value. When the link becomes an edit field, enter the payment amount calculated by the website.
7. Repeat the above step to enter the Total Interest amount. Part 2 Capture the screen image 8. Click on the Actual results button.
The Actual Result window is displayed.
HP Sprinter
Case Study 8|9
9. Click on the Save Annotate as Actual Result button.
A screen capture of your current screen is displayed. 10. Using the Annotation Tools, select the rectangle and the color blue.
11. Draw a square around the Personal Loan Amount. 12. Click the Save to Actual Results button.
13. Click Close to close the Sprinter message window.
14. Click Close to close the Annotation workspace.
15. Click OK to close the Actual Result window.
HP Sprinter
C a s e S t u d y 8 | 10
Part 3 Open a defect 16. You notice that the font colour should be green, not red. Open a defect by selecting the Smart Defect link.
17. In the Smart Defect Settings window, choose these settings:
Options
Check -- Current step Check -- Include last steps actual result information Check -- Current Screen Capture
18. In the Smart Defect Settings window, click Submit Defect. 19. In the New Defect window, select values for any mandatory fields (fields with red labels), and click OK. 20. Click on the End Run button from the Run Control tool bar. 21. When the Sprinter window appears, click on Steps (7) from the Results group. 22. In the list of steps, verify that Step 7 has the screen capture. (You may need to scroll to the right to see the Screen Capture column.)
HP Sprinter
C a s e S t u d y 8 | 11
Activity 5 Run the remaining tests

1. Make sure Power Mode is turned off. 2. Select the test GIC Calculator. 3. Right click on the test and select Deactivate Test. 4. In the same way, deactivate test What you Can Afford. 5. Verify two tests are active: Branch Locator and First Contact Staff Data Attachment. 6. In Run Setup area, click on the Run button.
7. Complete the steps for the first test. Remember to pass each step as you complete it. 8. In the Run control tool bar, select Next Test to advance to the next active test in the list.
9. Complete the steps for the second test. 10. When the test is complete, click on the End Run button from the Run Control tool bar.
HP Sprinter
C a s e S t u d y 8 | 12
Activity 6 Verify the Results in ALM

1. Close Sprinter. 2. Open ALM and log into your project. 3. In the Test Lab, open the test sets you were working on. 4. Make sure the Execution Grid tab is selected. 5. Select a test with a PASSED status, and click on the Launch Sprinter Results Viewer button. The Results Viewer Sprinter window launches, 6. Verify the data and close the Sprinter Results Viewer.
HP Sprinter
C a s e S t u d y 8 | 13
HP Sprinter
C a s e S t u d y 8 | 14
Case Study 9 HP Sprinter Power Mode
HP Sprinter Power Mode
Case Study 9|1
Sprinter Power Mode Overview

With this information, Sprinter can:
When you run a test in Power Mode, Sprinter learns your applications display and identifies its objects. This information enables Sprinter to track your activity during your test run and perform some user actions for you on your application.
Create and run macros to allow Sprinter to perform a set of actions in your application for you. Automatically enter data into fields in your application. Replicate your user actions on multiple machines. Keep a record of your user actions. Add comments and reminders to the recorded user actions in your run, for later review. Keep a record of the defects you submitted for each action. Automatically include the list of your steps or user actions in any defect you submit to create a defect scenario for you.
Data Injection During the testing process, it is often necessary to enter pre-defined data into a form in the application being tested. To make the data entry process faster and less error-prone, data injection enables you to automatically enter data contained in an .xls, .xlsx, or .csv file (data set) into fields in your application. You can store data sets in your file system or in HP ALM. To store data sets in HP ALM, upload them to the Resources folder for your project. After you create the data set, you associate it with your application in the Data Injection pane of the main window. When you associate a data set with an application, it is available for use in any test that is configured to use the currently defined application. Macros A macro is a recorded action that can be placed within a given manual test in the form of a drop down menu. To record an action, click on the Start Recording button and initiate the actions you wish to take and then click on the Stop Recording button. The user will be asked to name the saved marco and it will be placed in a drop down menu for the user to pull out the next time the user runs with test with Sprinter.
Case Study 9|2
Mirroring A common testing requirement is the need to test your application's compatibility with different computer configurations, and in the case of Web applications, with different browsers. Sprinter's Mirroring feature enables you to run your test simultaneously on multiple machines with different configurations. A test run with mirroring has a primary machine and secondary machines: Primary machine. The machine on which you manually perform all the user actions in your test. Secondary machine. The machines on which Sprinter replicates your user actions.
To run a test with Mirroring, you configure each of the secondary machines with the specific configuration you want to test. After you perform each user action on your primary machine, Sprinter replicates that user action on your secondary machines. When you configure your secondary machines, consider that Sprinter replicates your user actions the same way they were performed on your primary machine. You need to configure your secondary machines in such a way that there will not be a conflict between the actions that are performed on all the machines.
Case Study 9|3
Instructor-Led Demo
1. Record and Run a macro
2. Data Injection
3. Mirroring
Case Study 9|4
Activity Summary
Sprinter
Create a manual test from Sprinter Create and use a Sprinter Macro Use Sprinter Data Injection Run a manual test with Sprinter using Cross-Browser Mirroring
Case Study 9|5
Activity 1 Using Sprinters Power Mode To Design Manual Tests

Part 1 Create A Blank Manual Test 1. 2. 3. 4. Log in to Quality Center. Navigate to the Test Plan module. Create a folder called Vanguard (that is Subject > Vanguard) With the Vanguard folder selected, create a new MANUAL test named ETF Links.
5. Navigate to the Test Lab module. 6. Create a folder called Vanguard Tests (that is Root > Vanguard Tests) and create a test set called Website.
7. Add the ETF Links test to the Website test set. 8. Logout of Quality Center. 9. Close the Quality Center window (and any other open browser). Part 2 Load the test with Sprinter 10. Launch HP Sprinter 11. Connect to your assigned project in Quality Center. 12. Click on the Open button.
13. In the Open window, expand the Root folder, followed by Vanguard Tests > Website. 14. Checkmark the (1) ETF Links test and click Open. Part 3 Add an Application 15. Ensure Power Mode is set to On.
Case Study 9|6
16. Select the Application link.
17. Click on the Add button. 18. In the Add Application window, use the table below to fill the required information. Name: Type: URL: Browser: checked Vanguard Web Application www.vanguard.com Internet Explorer Start the application when the run begins
unchecked Record on any open application
19. Click OK to close the Add Application window. Part 4 Run the tests and complete some ad-hoc steps 20. Click on the Run the active test button.
21. When the Vanguard website opens, complete the following steps: a) Click on Learn more about Vanguarding b) Click on each link from Mutual Funds to Personal Services c) Close Internet Explorer. 22. From the Run Control tab, click on the End Run button.
Case Study 9|7
Part 5 View the User Actions 23. In the HP Sprinter window, click on User Actions.
24. From the User actions toolbar, select Export > Export to Excel.
25. Save the file as ETF Test Steps to the Desktop. 26. Close HP Sprinter. Part 6 Copy User Actions To Export Template 27. Open the ETF Test Steps file. 28. Modify the file as follows: a. Add a column and type Subject in the first row b. Starting in Row 2 of the Subject column, type Vanguard c. Add a column and type Test Name in the first row d. Starting in Row 2 of the Test Name column, type ETF Links e. Rename the value Action to Step Name (Design Steps) f. Rename the value Description to Description (Design Steps) g. Delete columns Time and Comment.
Case Study 9|8
Part 7 - Export Data to Vanguard Project 29. Highlight all rows containing data except row 1. 30. Select Tools > Export to HP ALM. 31. Enter the URL and click Next. 32. Enter your username and password click Next. 33. Select your domain and project and click Next. 34. Ensure Tests is selected and click Next. 35. Select Temporary and click Next. 36. Click on the Map fields by label button.
37. In the Map Fields By Labels window, enter 1 and click OK.
38. Click on Export. 39. When the wizards displays the worksheet was successfully exported to ALM, click Finish. 40. Close the Excel files, save the changes. Part 8 Verify The Data Was Exported Successfully 41. Open ALM and login to your project. 42. Navigate to the Test Plan module. 43. Select the ETF Links test. 44. Select the Design Steps tab and verify the excel data was successfully exported into the test.
Case Study 9|9
Activity 2 Create a Sprinter Macro

Part 1 Open the test and enable Power Mode 1. Open Sprinter and connect to your ALM project 2. Open the CIBC.com\Sanity Tests\[1]Branch Locator test instance 3. Turn Sprinter Power Mode on
Part 2 Setup the Application in Sprinter 4. Click the Application link under Power Mode 5. Click the Add button to define a new Application in Sprinter
6. Using the following values: Name: Type: URL: Browser: CIBC Website (IE) Web Application www.cibc.com Internet Explorer Start the application when the run begins checkbox is checked
C a s e S t u d y 9 | 10
7. Press OK to save the Application definition 8. Ensure that the CIBC Website (IE) application is selected in the Application: list box. 9. Begin the test run by pressing the Run button Part 3 Record the Macro 10. Read the instructions for the Step 1 of the Branch Locator test carefully. DO NOT perform any actions yet, you will record them in a macro. Note: This is a good place to use a macro because it is a set of steps that are not essential to the outcome of the test and will have to be repeated for any test that evaluates the Branch Locator utility. 11. Click the Macros tab and click the pushpin icon to pin the tab open. 12. Press the Record Macro button to begin recording
13. Navigate to the CIBC Branch Locator pop-up applet by following the Suggested method: in the first step of the Branch Locator test Click on the Contact Us link in the top menu, enter M2N5W9 in the search field and press Find.
14. Press the Stop Recording button on the Macros tab.
C a s e S t u d y 9 | 11
15. In the Macro Details window, enter Open Branch Locator M2N5W9 in the Name: field and press OK to save the macro.
16. Continue the Run and complete the remaining test Steps. Remember to pass each step. 17. Stop the test Run in the Run Control tab Part 4 Use the Macro in a test Run 18. Right click the Branch Locator test and select Replace with New Run 19. Press the Run button to begin a new test Run 20. Minimize the Steps tab 21. To complete Step 1 of the Branch Locator test, click on the Macros tab 22. Use the drop down list to select the Open Branch Locator M2N5W9 macro 23. Press the Run button to complete Step 1 of the test 24. Click on the green checkmark icon on the Macros tab to view the Macro Status details
C a s e S t u d y 9 | 12
25. Close the Macro Status window
26. Complete the test Steps 27. Stop the Run and close any open Browser windows.
C a s e S t u d y 9 | 13
Activity 3 Use Sprinter Data Injection

1. Open Sprinter and connect to your ALM project Attachment test. 3. Turn Sprinter Power Mode on Part 1 Setup the Application in Sprinter 4. Click the Application link 5. Click the Add button to define a new Application in Sprinter. Use the following values: Name: Type: URL: First Contact (IE) Web Application www.firstcontactconsultants.com Start the application when the run begins checkbox is checked 6. Press OK to save the Application definition 7. Ensure that the First Contact (IE) application is selected in the Power Mode area. Part 2 Setup Data Injection 8. Click on the Data Injection link in Sprinter under Power Mode 9. Press the Add Data Set button and select Add from HP ALM 2. Open the First Contact Website\Website Forms\[1] First Contact Staff Data
Browser: Internet Explorer
C a s e S t u d y 9 | 14
10. In the Data Set Details dialog press the Browse button to open the Test Resources for your ALM project. 11. Expand out the Resources tree to locate the First Contact Staff Data for Contact Form data source
12. Select the data source and press Open 13. Press OK in the Data Set Details dialog to define the new data set Part 3 Begin the Test Run 14. Start the Run in Sprinter 15. Follow the test Steps until you reach the Contact Us form (complete Step 2) Part 4 Inject Data 16. Click on the Data Injection tab and press the pushpin icon to pin it open 17. Adjust the scroll of the browser so that the Submit button is visible. 18. Click the Display Field Mapping button on the Data Injection tab
19. Review where the spreadsheet data will be entered into the form (fields are highlighted in yellow) 20. Click on the yellow yield sign on the Data Injection tab to open the Data Injection Status dialog
C a s e S t u d y 9 | 15
Note: Not all of the columns in the spreadsheet can be matched to fields on the form, specifically the Street2 and Province columns do not have corresponding fields.
21. Close the Data Injection Status dialog 22. Press the Customize Fields button on the Data Injection tab
23. In the Customize Fields dialog un-check the Street2 and Province fields, as they are not needed for this form, and press OK to save the changes 24. Press the Display Field Mapping button again Note: This time a green check mark is displayed on the Data Injection tab 25. Select the line of data containing Milan Danrels contact information 26. Press the Inject Data button and wait for Sprinter to complete the form
Part 6 Complete the Test Run 27. Follow the remaining test Steps 28. Stop the test Run and close any open browser windows.
C a s e S t u d y 9 | 16
Case Study 10 Libraries and Baselines
Libraries and Baselines
Case Study 10|1
Pre-Discussion
You are on working on a Quality Center project that has a need to be able to run the same testcase against two different versions of the application which are slightly different, so that the testcases are slightly different too. For instance, you have completed Version 1 of the application, and the developers are enhancing the functionality in Version 2 of the application. Now you need to support testing of version 1 and version 2 of the application using the same test cases. How would you organize this in Quality Center?
Case Study 10|2
You can create libraries in the Libraries module. After a library is created, you can create and compare baselines for the library to track changes in your project.
In the Libraries module, you can define a hierarchical libraries tree to create and manage your libraries. A library represents a set of entities in a project and the relationships between them. The entities in a library can include requirements, tests, test resources and business components.
After you create a library, you can create a baseline. A baseline is a snapshot of your library at a specific point in time. You can use a baseline to mark any significant milestone in the application development life cycle. A baseline includes all the entities defined in the library, including requirements, tests, and test resources. Baselines also include the relationships between the entities in the library, such as traceability and coverage. Baselines enable you to keep track of changes made to your project over time.
When you create a baseline for a library, you have a snapshot of the library at a specific point in time. Baselines enable you to keep track of changes made to your project over time. You can use baselines in the following ways: Compare two baselines to view the changes in a library at different stages of development. You can compare baselines at all stages of the application development life cycle. For example, you can compare two baselines in a library to review changes made to requirements in the library over time. You can also compare a baseline to the current entities in the library. Pin a test set to a baseline. This ensures that when you run the test set, Quality Center runs the versions of the tests stored in a baseline you specify. For more information, see Pinning a Test Set to a Baseline
Libraries and Baselines Case Study 10|3
Instructor-Led Demo
1. Create a Library and Baseline
2. Comparing Baselines
3. Pinning a Test set to a Baseline
Case Study 10|4
Activity Summary
Management
Create a Library Create a Baseline Making changes to Baseline Creating another Baseline Comparing Baselines
Test Lab
Pinning a Test set to a Baseline
Case Study 10|5
Activity 1 Create a Library & Baseline

1. Navigate to the Libraries module 2. Press the Create Library ( yet!) 4. In the Requirements tab, expand the Requirements folder and select the CIBC Standards and CIBC Website Development folders by checking the check-box to the left of the folder. ) button 3. In the New Library window enter the name Banking Website (Do not close the window
5. In the Tests tab, select all the tests in the CIBC.com folder by checking the checkbox to the left of the folder.
6. Press OK to close the New Library window. 7. Select the library that was just created. 8. Click on the Create Baseline ( ) button
9. Name the Baseline SnapShot1 and Press OK to create the baseline.
Case Study 10|6
Activity 2 Modify & Compare Baselines

1. Navigate to the Requirements Module 2. Select View > Requirements Detail. 3. Navigate to the CIBC Website Development > Help Screen requirement 4. Change the following fields of the requirement Field Name Priority Reviewed 5. Navigate to the Test Plan module. steps. 7. To make sure all the changes are saved, log out of the project and then log in again. Compare Baselines 8. Navigate to the Libraries module 9. Select the library created in the previous activity 10. Create a new Baseline and name it SnapShot2 11. Select the SnapShot1 baseline that you previously created and right click on it. 12. Click on Compare to Select Baseline 13. In the Select Baseline window, expand the tree and select the baseline SnapShot2 and click OK. 14. Click OK to close the Select Baseline window. 15. Expand the Requirements tree and Test Plan tree and verify that the changes that you made are listed as Modified 16. Close the Compare Baselines Tool window. New Value 4-Very High Reviewed
6. Make changes to the Learn More About Credit Cards test by adding two additional
Case Study 10|7
Activity 3 Pinning a Test Set to a Baseline

1. Navigate to the Test Lab Module 2. Create a new Folder named Baseline Test 3. Create a new Test Set using the following options: Test Set Name Baseline Regression SnapShot1
4. Click OK to close the New Test Set window. 5. Add the Learn More About Credit Cards test to the Baseline test set.
6. Run the test and verify that the additional steps that you added in Activity 2 are not included in the list of steps
Case Study 10|8
Case Study 11 Version Control
Version Control
Case Study 11|1
Version Control
other users.
To make changes to an entity in a version control enabled project, you must first check out the entity. When you check out an entity, Quality Center locks the entity, preventing other users from overwriting any changes you make. The checked out version of the entity is not visible to
When you finish making changes, you check in the entity. The new version of the entity is then available to the other users. The default version number for a new entity is 1. Prior to Quality Center 10.00, version numbers consisted of three segments separated by periods, such as 1.7.4. From Quality Center 10.00, version numbers consist of a single segment, such as 12. When an entity is checked in, the version number is increased by one. When an entity is checked out, you can undo the checkout to cancel your changes. You can view all previous versions of an entity, or check out an earlier version. You can also compare two versions of an entity to view the changes between versions. Note: To maintain usability and data integrity, Quality Center stores previous versions of an entity without most data related to relationships between entities. The following data is not stored for previous versions: requirements and tests coverage, requirements traceability and defect linkage. In addition, risk data is also not stored for previous versions of an entity. You can view the list of all entities that you have checked out in your project. You can create and manage entities in a version control enabled project in both tree and grid views. In the tree view, an entity checked out by the current user is displayed with an open green lock icon. An entity checked out by another user is displayed with a red lock icon. Grid views contain additional version control fields, such as Version Status, indicating whether the entity is checked in or checked out.
Version Control
Case Study 11|2
Instructor-Led Demo
1. Check out a test
2. Make changes to the test and check it in
3. Comparing two versions of the Test
Version Control
Case Study 11|3
Activity Summary
Tests and Requirements
Check out a test Check in the Requirement and the Test Comparing two versions of the Test Check out a requirement
Version Control
Case Study 11|4
Activity 1 Change a Requirement

1. Select the Requirements module Quote requirement 3. Right click on the selected requirement and select Version > Check out
2. Expand the Progressive.com requirements folder and select the Request a Homeowner
4. Under the Check out comments, type in Version 1 and click OK 5. Note the requirement now has an open green lock beside the requirement 6. Make changes to the requirement such as changing the field values or descriptions 7. Click on the Check In button ( ) and click OK in the Check In window
8. Repeat Steps 3 - 7 for three other requirements. Select one from the Navigation folder, one from the Report Claim and the other from the Site Search folder. Note: You will notice that the Version number has increased by 1
Version Control
Case Study 11|5
Activity 2 Change a Test

1. Select the Test Plan module 2. Select the Invalid Login test you previously created 3. 4. Click on the Check Out button ( )
5. Under the Check out comments, type in Version 1 and click OK 6. Make some changes to the test (for example the description or expected result) 7. Right click on the test and select Version > Check In
8. Using the steps above, make changes to three other tests (again for example the description or expected result)
Version Control
Case Study 11|6
Activity 3 Comparing two versions

1. Select the Requirements module
2. Expand the Progressive.com requirements folder and select a requirement (make sure Requirement details is selected under the View menu).
3. Navigate to the History tab
4. Holding down the CRTL button, select two versions and click on the Compare button
5. The Compare Entities Requirement window appears, review the changes that have been listed
6. Click on the Close button after reviewing the changes
Version Control
Case Study 11|7
Activity 4 Challenge
1. Check out a test and make changes to it.
2. After checking it back in, try and revert back to the original test.
Version Control
Case Study 11|8
Case Study 12 Automated Tests (Optional)
Automated Tests
Case Study 12|1
Automated Tests
Manual software testing is performed by a human sitting in front of a computer carefully going through application screens, trying various usage and input combinations, comparing the results to the expected behavior and recording their observations. Manual tests are repeated often during development cycles for source code changes and other situations like multiple operating environments and hardware configurations. An automated software testing tool is able to playback pre-recorded and predefined actions, compare the results to the expected behavior and report the success or failure of these manual tests to a test engineer. Once automated tests are created they can easily be repeated and they can be extended to perform tasks impossible with manual testing. Because of this, savvy managers have found that automated software testing is an essential component of successful development projects. Test planning involves deciding which tests to automate. If you choose to automate a test, you can generate a test script and run the test using WinRunner, QuickTest Professional, LoadRunner, or Visual API-XP.
Automated Tests
Case Study 12|2
Instructor-Led Demo
3. View the test in Quality Center
1. Create an Automated test in QuickTest Pro 2. Add the automated test to Quality Center Project
4. Define the Host computer where the tests will be run. 5. Run an automated test
Automated Tests
Case Study 12|3
Activity 1 Create and run Automated tests

Part 1 Create Manual tests
1. Select the Test Plan module 2. Create the following MANUAL tests
Test Name
Login Create Order
Steps
1. Open the application home page 2. Enter your username and passwords 1. Select Create Order link 2. Enter data for a new order 3. Submit order and record the order number 1. Search for order number 2. Update the order details 3. Save the order 1. Click the logout link
Update Order
Logout
Part 2 Convert the tests to VAPI tests

3. Select the Login test. 4. Click on the Design Steps tab. 5. Click on the Generate Script button and select VAPI-XP TEST.
6. Convert the remaining tests to VAPI-XP tests.
Part 3 Add the tests to a Test Set

7. Select the Test Lab module 8. Create a new folder and test set Folder Training Test Set Automated Tests
Automated Tests
Case Study 12|4
Part 4 Run the test

9. Add all the tests to the Automated Tests test set. 10. Select Tests > Order Tests Instances 11. In the Order Tests Instances window, use the Move Up and Move Down buttons to set the test instance order as follows:
12. Click the Run Test Set button. 13. Select the Run All Tests Locally checkbox 14. Click on the Run All button 15. Wait for the tests to run. When all the tests have a Status of Passed, the test execution is complete. 16. Close the Automatic Runner window.
Automated Tests
Case Study 12|5
Automated Tests
Case Study 12|6

QC Using

Uploaded by

Document Information

Original Description:

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

QC Using

Uploaded by

Copyright:

STUDENT WORKBOOK

Using Quality Center v11 STQC-155

How this Course is Organized

Using Quality Center

Concepts and Overview| 1

Introducing Quality Center

Using Quality Center

Concepts and Overview| 2

Specifying Releases and Cycles

Using Quality Center

Concepts and Overview| 3

Adding and Tracking Defects

Analyzing the Testing Process

Using Quality Center

Concepts and Overview| 4

Quality Center Administration

Using Quality Center

Concepts and Overview| 5

Login to Quality Center

User Name Password

Using Quality Center

Concepts and Overview| 6

Case Study 1 Standard Implementation

Quality Center Implementation

Case Study 1|1

Releases and Cycles

1. Create the Releases folders

Quality Center Implementation

Case Study 1|3

Activity 1: Create the Releases Folders

Part 2 Create Release Tree

Quality Center Implementation

Case Study 1|4

Activity 2: Create Releases and Cycles

Part 2 Add Cycles

Quality Center Implementation

Case Study 1|5

Quality Center Implementation

Case Study 1|6

Activity 3: Complete Release Tree

2. The releases tree should resemble the following:

Quality Center Implementation

Case Study 1|7

1. Create a Requirement folder

Quality Center Implementation

Case Study 1|8

Activity 4: Create a Requirements Tree

Part 2 - Create the Requirements Structure

9. The requirements tree should resemble the following:

Quality Center Implementation

Case Study 1|9

Activity 5: Create Requirements

Part 2 Finish Requirements for Get A Quote Folder.

Part 3 - Create Requirements For Remaining Folders

Quality Center Implementation

14. The requirements tree should resemble the following:

Quality Center Implementation

Creating Manual Tests

Quality Center Implementation

Activity 6: Create a Test Plan Structure

2. Select the Subject folder. 3. Click the New Folder button.

10. The subject tree should resemble the following:

Quality Center Implementation

Activity 7: Create Tests

Part 2 - Create additional Tests

Test Plan Folder