Patrice M. Anderson Instructional Designer

Transcription

1 Patrice M. Anderson Instructional Designer Portfolio Sample Instructor-Led Training This sample contains the ToC and one chapter from the instructor-led student workbook for HP Quality Center (QC) software. I was responsible for working with Subject Matter Experts and stakeholders to develop all training for the Quality Center portfolio, including instructional design, writing, editing, lab design, virtual lab set up and publishing.

2 Application Lifecycle Management/Quality Center 11.x Essentials For version 11.0 Revision C2 HP Software Education Student Guide

3 APPLICATION LIFECYCLE MANAGEMENT/QUALITY CENTER 11 ESSENTIALS Copyright Information The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. This is an HP copyrighted work that may not be reproduced without the written permission of HP. You may not use these materials to deliver training to any person outside of your organization without the written permission of HP. Printed in the United States of America. Application Lifecycle Management/Quality Center 11 Essentials For version 11.0 Revision C2 Student Guide June 2012 If you have any comments or suggestions regarding this document, please send them via

4 Table of Contents Introduction to Application Lifecycle Management/ Quality Center Course Objectives Class Introductions Course Outline Lesson Objectives Application Lifecycle Management/ Quality Center Overview Application Lifecycle Management (ALM) Editions The Application Lifecycle Management Roadmap An End-to-End Example Logging on The ALM/Quality Center Modules The Quality Center Toolbars Shortcut Menus Tools and Help Using Favorite Views Summary Working with Releases The Application Lifecycle Management Roadmap Definitions A Sample Release Tree Tools for Creating a Release Tree Specifying Cycle Details Adding Attachments to a Cycle Types of Attachments Assigning Requirements to Releases and Cycles Assigning Tests to Cycles Summary Working with Requirements Application Lifecycle Management Roadmap Advantages of a Clearly Defined Requirement Characteristics of a Useful Requirement Requirement Types What is a Requirements Tree? Using the Requirements Tree View Tools for Building a Requirements Tree TOC-1

5 Creating a Requirement Specifying Requirement Details Requirement Details Toolbar Buttons in the Requirements Module Viewing Requirement Details Description and Comments Tabs Requirement Templates Using Rich Text Viewing Multiple Requirements Editing Multiple Requirements Assigning Requirements to Releases and Cycles Assigning Requirements to Releases Assigning Requirements to Cycles Summary Analyze Requirement Risks Using Traceability Requirement Relationships Adding Traceability to Requirements Impact Analysis The Traceability Matrix Using Risk-Based Testing The Risk-Based Quality Management Analyze and Assess Risks Establishing Business Criticality Establishing Failure Probability Establishing Functional Complexity Performing Risk Analysis Viewing Analysis Results Drilling Down into Results Generating a Risk Report Test Coverage Linked Defects Mailing Requirements Summary Test Planning Application Lifecycle Management Roadmap Test Planning Overview Opening the Test Plan Module The Test Plan Tree Creating the Test Plan Tree TOC-2

6 Converting a Requirement to a Test Selecting an Automatic Method for Conversion Making Changes to the Automatic Conversion Selecting the Destination Path Creating a Subject Folder Key Pointers for Defining Tests Adding a Test Test Types Populating the Details Tab Knowledge Check Adding Test Steps Considerations for Designing Test Steps Calling a Test Test Parameters Defining a Parameter Calling a Test with Parameters Editing the Values of Called Parameters Creating Template Tests Generating a Test Script Test Configurations Defining Test Configurations Adding Configurations to Req Coverage Generating a Live Analysis Graph from the Test Plan Modifying the Appearance of a Live Analysis Graph Summary Requirements Coverage Requirement and Test Coverage Creating Test Coverage Creating Requirement Coverage Coverage by Test Configuration Analyzing Coverage Tracking Cycle Progress Summary Test Execution Application Lifecycle Management Roadmap Using the Test Lab Module - Test Sets Tab Test Runs Tab Test Execution Overview Test Sets TOC-3

7 Test Sets Tree Creating a Test Set Folder Creating a Test Set Building Test Sets Adding Test Set Details Adding Tests to a Test Set Adding Test Configurations to a Test Set Test Configurations Based on Requirements Coverage Assigning Test Set Folders to Cycles Linking Test Set Folders to Cycles Using the Execution Flow Tab Defining Test Run Sequence and Conditions Scheduling Execution Date and Time Additional Options for Scheduling Knowledge Check Setting On-Failure Rules Setting a Test Set Notification Running Tests Running Manual Tests with Sprinter Running Tests Using the Manual Runner Tools for Recording Results of Manual Tests Automated Tests Running Tests Automatically Key Guidelines for Running Automated Tests Host Manager Viewing Test Run Results Reviewing Release Cycle Progress Summary Manual Testing with HP Sprinter HP Sprinter Overview Launching HP Sprinter Opening a Test Set Preparing to Run a Test Starting a Test Running a Basic Test Stopping the Test Setting Parameters Using Subtitles Recording Actual Results Submitting a Defect Editing Steps TOC-4

8 Annotating a Screen Capture Viewing Run Results Working with Power Mode Using Macros Using Data Injection Storyboards Working with Mirroring Summary Defect Tracking Application Lifecycle Management Roadmap Using the Defects Module Logging a Defect Defect Status Associating Defects with Other Entities Defect-Requirement Relationship Adding Defects to a Requirement Associating Existing Defects with a Requirement Defect-Test Relationship Adding Defects to a Test Defect-Test Instance Relationship Navigating to the Test Instance Details Dialog Box Linking a Defect to a Test Instance Logging Defects During a Test Run Updating a Defect Summary Using Version Control Version Control Overview Discussion: User Scenarios Using Version Control Version Control Tasks Checking Out Entities Manually Checking Out Entities Automatically Undoing Check Outs Checking In Entities Viewing Checked Out Entities Viewing Version History Compare Versions Promote Older Version Summary TOC-5

9 Library Management The Libraries Module The Libraries Menu Bar The Libraries Toolbar Creating a Libraries Tree Creating Libraries Filtering Entities Adding Tests Covering Selected Requirements Creating a Baseline The Library and Baseline Fields The Compare Baselines Tool Comparing Entities Configuring the Comparison Settings Modifying the Libraries Tree Library Elements Pinning a Test Set to a Baseline Summary Exporting from Excel Exporting Data Steps for Exporting Data Installing the Excel Add-In Verifying the Add-In Installation Formatting Excel Files Formatting Requirements in Excel Exporting Data Requirements from Excel to Quality Center Verifying Results Formatting Tests in Excel (Example) Exporting Tests Summary Reporting and Analysis Application Lifecycle Management Roadmap Reporting Options Overview Pre-Defined Reports and Graphs Example Analysis Report Project Report Launching the Document Generator Setting the Document Options Selecting the Data TOC-6

10 Generating the Document Custom Reports and Graphs New Standard Reports Customizing Standard Reports Adding Sub-Reports Quality Center Graph Types Graph Wizard Creating a Graph without the Wizard Configuring a Graph Elements of the Graph Window Displaying Graph Data Excel Reports Managing Reports Sharing Graphs Without QC Client Dashboard View Create a Dashboard Page Dashboard Configuration Guidelines Configure a Dashboard Page View a Dashboard Page Viewing Options Dashboard Detail Summary Course Summary Evaluation References Course Objectives TOC-7

11 TOC-8

12 8 Manual Testing with HP Sprinter Objectives After completing this lesson, you will be able to: Open a test and prepare it to run. Run a basic test. Submit a defect. Annotate a screen capture. View run results. Work with Power Mode. Use macros. Use data injection. Work with mirroring. 8-1

13 HP Sprinter Overview HP Sprinter runs manual tests in QC from the Test Lab module. In basic mode, Sprinter provides a variety of tools to assist in the manual testing process. You can: Change display options to allow you to see more of your application. Edit parameters during your test run. Submit defects to ALM or set a default reminder if you don t want to interrupt your test run. Create and annotate screen capture and capture movies of your run. In add it on to running basic manual tests, Sprinter s POWER MODE also allows you to: Record and run macros on your test application. Automatically enter data into fields in your application. Use Storyboards that display each action you performed in your test. Replicate your user actions on multiple machines with different configurations. 8-2 HP Sprinter Overview

14 Launching HP Sprinter There are two ways to open a test in Sprinter. Either select a test in ALM s Test Lab module and launch Sprinter from there. Or you can open Sprinter on your desktop, connect to ALM and open the test from ALM s Test Lab module. Note: QuickTest Professional needs to be closed prior to launching Sprinter. To launch HP Sprinter from the desktop: 1. Click on the SPRINTER shortcut on the desktop. HP SPRINTER opens showing the OPEN A TEST window. Close the OPEN A TEST window. 2. The first time you run the application, the GETTING STARTED PAGE can be seen. Double-click on the HP ALM CONNECTION button in the lower right portion of the main window. 3. In Sprinter s main window, click the OPEN button. 4. Enter the ADDRESS, USER NAME and PASSWORD and click on the AUTHENTICATE button. 5. Enter the DOMAIN and PROJECT and check the RECONNECT ON STARTUP check box since you would always work on the same HP ALM server. Launching HP Sprinter 8-3

15 6. Click the LOGIN button. Sprinter connects to HP ALM and the OPEN dialog box appears. 8-4 Launching HP Sprinter

16 Opening a Test Set To open a test: Figure 8-1 Opening a Test 1. In the OPEN dialog box expand the test plan tree until you find the test set that you want to execute. 2. Select the test set, then check the appropriate boxes to select the tests to run, or click the SELECT ALL button to select all the tests. 3. Click the OPEN button. The Sprinter window appears. Opening a Test Set 8-5

17 Preparing to Run a Test Figure 8-2 The Sprinter Window The Sprinter window contains the following elements: The TESTS list displays the tests to be included in the next run. The Status bar shows how many tests from the Tests list will be included. The right hand pane shows the DEFINITIONS group containing three nodes: GENERAL SETTINGS, STEPS and PARAMETERS. GENERAL SETTINGS node displays the name of the test, the name of the test set, the name of the configuration, the test owner, the test description, the name of the run, the name of the tester, the status of the run, the date, and time of the run start and stop, and any attachments. The STEPS node is used to confirm the steps in the test. The PARAMETERS node is used to confirm the parameters in the test. 8-6 Preparing to Run a Test

18 The RESULTS group contains all the options for evaluating the success of your test. Preparing to Run a Test 8-7

19 Starting a Test Figure 8-3 Sidebars To start a basic test: 1. Open your Application Under Test. 2. Click the RUN button in the RUN SETUP area. The main Sprinter window minimizes and several sidebars appear along the edges of the Windows Desktop. 3. Verify that you see the following sidebars: The TOOLS sidebar at the top edge of the Windows Desktop The RUN CONTROL sidebar also at the top edge The STEPS sidebar at the bottom edge 8-8 Starting a Test

20 Running a Basic Test You perform the user interactions as specified in the Steps window, evaluate the expected results, pass or fail the step, and make annotations for the actual results as necessary. To execute the test: 1. The STEPS sidebar should open automatically. If not click the STEPS tab. 2. Follow the instructions for the first test step. In this example we enter the Agent Name. 3. Evaluate whether the application is responding as expected, then select either PASS or FAIL from the tool bar. 4. Continue to proceed through the steps until you have finished. Running a Basic Test 8-9

21 Stopping the Test To stop the run and review test results: Figure 8-4 Stopping the Test 1. Expand the RUN CONTROL sidebar and click the END RUN button to stop test execution. The Sprinter main window restores. 2. Review your test results in the RUN SUMMARY area of the Sprinter main window Stopping the Test

22 Setting Parameters Figure 8-5 Setting Parameters To specify parameters: 1. Select the test, in this example the second test SEARCH BY ORDER NO. 2. Click the PARAMETERS link in the DEFINITIONS group. 3. Enter the ACTUAL VALUE of the Parameter. Setting Parameters 8-11

23 Using Subtitles Figure 8-6 Subtitles For the next test, we will run it using the Subtitle feature. This will allow us to run the test with a minimum of testing interface interfering with our application windows. To show subtitles: 1. Click the RUN button to activate the next test in the test set. 2. Click on the SHOW SUBTITLES button in the STEPS sidebar. Subtitles mode displays the description of each step as a subtitle on your screen instead of the sidebar. 3. Click on the subtitle and the Subtitle menu bar appears. You can pass or fail each step as well as selecting additional options 4. Click the SUBTITLES SETTINGS button. The SUBTITLES SETTINGS dialog box opens. Use this to change the settings for the subtitles for viewing convenience. 5. Mark each step's status using the Pass or Fail buttons. You can also use the drop down with the Status button. The possible values for status are PASSED, FAILED, BLOCKED, NOT COMPLETED, NO RUN, N/A Using Subtitles

24 Recording Actual Results To record the actual result: Figure 8-7 Actual Result Dialog Box 1. When the actual result is not the same as the expected result, click on the ACTUAL RESULT button. The ACTUAL RESULT dialog box opens. Enter the text to describe the actual result. 2. To add an image to the actual results, click on the SAVE SCREEN CAPTURE AS ACTUAL RESULT button and click on OK button in the ACTUAL RESULT dialog box. Recording Actual Results 8-13

25 Submitting a Defect To enter a smart defect: Figure 8-8 Submitting a Defect 1. Click on the drop down for SMART DEFECT button. Select SMART DEFECT option. This includes the list of user actions and a movie of the run that lead to the defect. 2. When the run is in progress, if you find a defect but do not want to disrupt the run, you use ADD DEFECT REMINDER. The reminder is included with the test results and can be viewed at the end of your test. You can then submit the defect later from the test results. The same information you have available during the test is also available to you from the results. So you can include annotated screen captures, movies, and step or action information in the defect at that time. To add a defect reminder: 1. Click on the drop down for SMART DEFECT button. Select ADD DEFECT REMINDER option. 2. In the DEFECT REMINDER dialog, type the description of the defect and click on OK button Submitting a Defect

26 Editing Steps To add a new test step or to edit an existing test step: 1. Select a test step. 2. Click on the EDIT STEPS menu drop-down from STEPS sidebar. 3. To add a new step, select the INSERT BEFORE or INSERT AFTER option. The EDIT STEPS dialog opens. Enter the NAME, DESCRIPTION and EXPECTED RESULTS and click OK to close the EDIT STEPS dialog box. The new step is added to the list of steps in the STEPS sidebar. 4. To edit the existing step, select EDIT STEPS option. The EDIT STEPS dialog opens. Change the NAME, DESCRIPTION or EXPECTED RESULTS and click OK to close the EDIT STEPS dialog box. Editing Steps 8-15

27 Annotating a Screen Capture Figure 8-9 Annotating a Screen Capture Annotations are used to highlight the problem in the images that are attached to a step, run, actual result or defect. To annotate a screen capture: 1. Click on SAVE ANNOTATION AS ACTUAL RESULT button in the ACTUAL RESULT dialog box. The ANNOTATION WORKSPACE opens. 2. Use the ANNOTATION TOOLS to mark up the screen capture. 3. Click on SAVE TO ACTUAL RESULT button. 4. Click on CLOSE button. The annotated image appears in the image section of the ACTUAL RESULT dialog box Annotating a Screen Capture

28 Viewing Run Results To view the run results: Figure 8-10 Viewing Run Results 1. Click the STOP button in the RUN CONTROL sidebar to end the run. The sidebars close and the RUN SUMMARY pane opens in the main window. 2. The summary includes: test and run information, the number of actions you performed (Power Mode tests only), the number of defects you submitted, the number of defect reminders you created, the number of comments you added (Power Mode tests only), and the status of each step performed. 3. Select the SUBMITTED DEFECTS node to view a list of the defects you submitted during your test. Click on DEFECT ID NUMBER to open the HP ALM DEFECT DETAILS dialog box for that defect. 4. Select the DEFECT REMINDERS node to view a list of the defect reminders created during the test. You can select a reminder and click SUBMIT Defect, to submit the defect to HP ALM. 5. Select the USER ACTIONS node and view a list of the user actions performed during the run. This list of user actions can be exported to an Excel spreadsheet. If you had run an informal test without predefined steps, you could modify them for use as steps, and then import them to a test in HP ALM. Viewing Run Results 8-17

29 Working with Power Mode Figure 8-11 Power Mode In Power Mode, Sprinter captures each user action on the application and stores the list of these user actions in the form of descriptive sentences. The user actions that Sprinter learns can be included in defects and viewed in the Storyboard in the test results. Sprinter remembers the Power Mode settings every time the application is tested. Sprinter provides macros to quickly run through some of the initial screens to get to the area that requires rigorous testing. Sprinter provides data injection to fill out forms Working with Power Mode

30 To use Power Mode: 1. Click the OFF button in the POWER MODE group under the TESTS list. The WELCOME TO POWER MODE! dialog box opens. 2. Click the CLOSE button in the dialog box. 3. Click the ADD button to manually define an application. 4. Enter the name of the application. 5. Choose the type of the application by clicking on one of the available types. 6. For a desktop application, enter the LOCATION and additional settings. For web applications, provide the URL and select a browser. 7. Choose the appropriate technologies used in the application. 8. Choose START THE APPLICATION WHEN THE RUN BEGINS or RECORD ON ANY OPEN APPLICATION, if required. 9. Click the OK button. Working with Power Mode 8-19

31 Using Macros Figure 8-12 Recording a Macro Macros allow you to record procedures so that you can quickly go through some of the initial screens to get to the area that requires rigorous testing. To record a macro: 1. Click on the MACROS sidebar. 2. Click on the RECORD MACRO button. 3. Perform the steps that you want to record in the macro. 4. Click on the MACROS sidebar again. 5. Click on the STOP RECORDING button. The MACRO DETAILS dialog box opens. 6. Enter the NAME and DESCRIPTION for the macro. 7. Click the OK button Using Macros

32 Figure 8-13 Running a Macro To run a macro: 1. Click on the MACROS sidebar. 2. Select a macro from the drop down list of macros. 3. Click on the RUN button. Once the macro runs successfully, a green tick mark is placed in the MACROS tab. If the macro does not run successfully, a red cross mark is placed in the MACROS tab. 4. Double-click on the green tick mark or the red cross mark. The MACRO STATUS dialog box is displayed, showing the status of the macro run. 5. Click the CLOSE button to close the MACRO STATUS dialog box. Using Macros 8-21

33 Using Data Injection Figure 8-14 Data Injection Data Injection enables the selection of rows of data to be sent automatically to the relevant locations in a form. To create Data Injection Data Sets: 1. Click on the DATA INJECTION node under the POWER MODE group. The DATA INJECTION frame opens on the right hand side. 2. To add a data set from HP ALM, click on the ADD DATA SET drop down and select ADD FROM HP ALM. The DATA SET DETAILS dialog box opens. 3. Click on BROWSE button. The RESOURCES tree opens. Expand the RESOURCES tree and locate the DATA SET on your system. 4. Click the OPEN button. The name of the resource appears as the default name. 5. Click the OK button. The DATA SET is added to the DATA INJECTION frame Using Data Injection

34 Figure 8-15 Data Injection To run in Power Mode using Data Injection: 1. Click the RUN THE ACTIVE TEST button. The DATA INJECTION sidebar appears on the perimeter of the display. 2. Click on the DATA INJECTION sidebar. 3. Click on a row of data and click on the INJECT DATA button. 4. The screen grays out and shows ANALYZING until the data injection completes. If the data injection completes successfully, a green tick mark is placed in the DATA INJECTION tab. If the data injection does not complete successfully, a red cross mark is placed in the DATA INJECTION tab. 5. Double-click on the tick mark or cross mark. The DATA INJECTION STATUS dialog box opens and shows the status. Using Data Injection 8-23

35 Storyboards Sprinter includes a Storyboard feature that displays each action you performed in your test. For each action, you can see a screen capture of the action, any defects that you reported, and defect reminders and comments you added to your run. If you ran the test with multiple configurations you can view the differences between the displays of different computers. To view the storyboard: Figure 8-16 Storyboard 1. Select the STORYBOARD node and the STORYBOARD opens. The top of the Storyboard displays a screen capture of the application as it appeared after the selected user action in the TIMELINE was performed, and an ACTION SUMMARY pane. The bottom of the STORYBOARD displays a TIMELINE of the run. 2. In the ACTION SUMMARY pane you view a description of each action and any defects that were submitted, defect reminders or comments that were added, and if you ran your test with mirroring, any differences that were found between the primary and secondary machines Storyboards

36 3. Click the links in the ACTION SUMMARY pane to open the HP ALM DEFECT Details dialog box, create a defect from your defect reminder, or open the DIFFERENCES VIEWER. You can also submit a new defect from the STORYBOARD. 4. The bottom of the STORYBOARD displays the TIMELINE of the test. The TIMELINE contains a thumbnail screen capture of each user action in your test. You can filter the thumbnails that are displayed in the TIMELINE using the FILTER DEFECTS button to show only those actions where you submitted a defect, using the FILTER DEFECT REMINDERS button to show only those actions where you created a DEFECT REMINDER, using the FILTER COMMENTS button to show only those actions where you added a comment, using the FILTER DIFFERENCES button to show only those actions where differences were found. Storyboards 8-25

37 Working with Mirroring Figure 8-17 Mirroring Mirroring is used to run the same test scenario on different configurations. With mirroring, every user action you perform in your application on your primary machine is replicated on the defined secondary machines. To work with mirroring: 1. Select the MIRRORING node in the POWER MODE group. 2. Click the ADD button to add a new machine for your application. 3. In the GENERAL tab, provide a NAME, DESCRIPTION and MACHINE NAME or IP ADDRESS for the machine which would be used as secondary machine. 4. In the RUN CONFIGURATION tab, choose an option for CONFIGURE HOW SPRINTER WOULD LAUNCH THE APPLICATION ON THE MACHINE and choose a browser Working with Mirroring

38 5. If you want to open a remote desktop connection to the machine during the test, in the REMOTE DESKTOP CONNECTION tab, enter the DOMAIN NAME, USER NAME and PASSWORD. 6. Click OK. Working with Mirroring 8-27

39 Summary In this lesson, you learned how to: Open a test and prepare it to run. Run a basic test. Submit a defect. Annotate a screen capture. View run results. Work with Power Mode. Use macros. Use data injection. Work with mirroring Summary