WEB Testing with

HP ALM/Sprinter

SCANA Corporation | 2012 Updated 07/2012

Table of Contents

I. Testing Preface I. Importance of HP ALM/Sprinter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 II. Testing Terms/Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 III. Testing Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

II. Preparing Sprinter for Testing I. Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 II. Opening Test Sets and Sprinter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 III. Starting Up Sprinter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 IV. Configuring Power Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

III. Testing with Sprinter I. The Sprinter Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 II. Using Sprinter – the Steps Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 III. Using Sprinter – the Tools Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 IV. Using Sprinter – the Run Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 V. Subtitles Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

IV. Reporting Defects with Sprinter I. Reporting Defects – Standard Web Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 16 II. Assigning Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 17 III. Post Run Actions – Run Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

V. Testing and Reporting Defects for Mobile Devices I. Device Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 II. Reporting Defects – Smartphones and Tablets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 - 21 III. Assigning Defects from Mobile Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 IV. Saving Mobile Screenshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Importance of HP ALM/Sprinter

• Supports business goal of IST/BSM efficiency • Clearer reporting of defects • Better coordination between departments

• Establishes a repository for all BSM test cases • Facilitates an organized and controlled testing atmosphere • Provides metrics to better prepare future testing efforts

3

Training Objectives

4

Testers will learn the following:

1. How to navigate HP ALM and start Sprinter

2. The important screens and functionalities within Sprinter

3. How to log defects and take screenshots with Sprinter

4. The testing methodology for devices

Testing Terms/Definitions

Term Definition

HP ALM software that helps to organize and manage the testing process.

Sprinter an add-on to HP ALM that assists the user in manually testing requirements. It adds functionality such as screenshots, storyboards and annotations.

Browser an application program that provides a way to interact with information on the web. Examples include: Internet Explorer, Safari and FireFox.

Test Set a collection of test cases within HP ALM.

Test Case a set of conditions under which a tester will determine if an application is working correctly or not.

Ribbon relative to Subtitle Mode, a long bar on the bottom half of a computer screen displaying instructions for executing test cases.

Device a piece of electronics that has internet capabilities. This includes both Smartphones and Tablets.

Smartphone a hand-held device that typically will have internet capabilities.

Tablet a portable device used primarily for its internet browsing capabilities.

Desktop a computer that employs the full versions of most browsers in today’s industry and maximizes internet window size and space.

Annotation a note or comment added to a particular set of text, or in this testing environment, a screenshot.

Smart Defect a method of reporting a defect where user actions and test steps will automatically be recorded in the comments section of the defect report. An annotated or plain screenshot can also be included.

New Defect a method of reporting a defect where information such as details about the defect, passed/failed test steps and screenshots must be manually entered.

Screenshot a picture of the current browser window. It can be taken on any desktop computer, and some devices.

5

Navigation

1

2

Once the user is logged in, a test set must be opened up. To open up a test set: 1. Click on the Testing

navigation bar on the left side.

2. Click on the Test Lab subcategory.

3. The beaker symbol represents a test set. Select the test set assigned by the Testing Coordinator.

3

6

1

Opening Test Sets and Sprinter

By clicking on the test set, you are almost ready to start Sprinter. Next, 1. Click on the Execution Grid

tab where you can view all the loaded test cases in the test set. The testing coordinator will already have the appropriate tests cases loaded in the set.

2. Ensure that the correct test case is highlighted. If not, simply click on it.

3. Above the Execution Grid tab, click Run and Sprinter will load.

1

3

2

7

Starting Up Sprinter

1

2

After the Sprinter window has appeared on the screen, 1. Verify that the correct test case

has loaded. 2. Verify that the Power Mode

button is On. If it is not, then simply click it to On.

3. Click Application under Power Mode to configure. The view will change and at the top of the screen, click the “Add” icon:

(turn to next page for further configuring instructions)

4. Once Power Mode has been

configured, click the green play button to launch.

8

Configuring Power Mode To properly configure Power Mode, execute the following: 1. Name the application the same

as what browser you are testing (e.g. IE8).

2. Select the Type of application you have: • For IE/FireFox, click Web

application • For Safari, search in the

program files for the “safari.exe” file.

3. For IE/FireFox only, enter the URL indicated in the test case and select the appropriate browser for which you will be testing.

4. Check the appropriate boxes that will be specified by the Testing Coordinator or a Developer.

5. To finish configuring Power Mode, click OK.

1

2

3

4

5

9

The Sprinter Window

Macros

Once the green play button is pressed, you will be up and running with Sprinter. The images to the right introduce Sprinter’s four main tabs within the window. However, our testing efforts will only require the use of three tabs:

• Steps • Tools • Run Control Note: Testers will not need to have an in-depth understanding of the Macros tab so it will not be explained in this instruction guide.

Tools Run Control

Steps

10

2

Using Sprinter – the Steps tab

1 2 3 4

The following numbers identify a functionality and correspond to a marker on the diagram at the right:

1. Pass Step – Simply click to pass

the current step 2. Fail Step – Simply click to fail the

current step. 3. Report Defect – For our

purposes, either a Smart Defect or a New Defect will be used. • Smart Defects are used for

Desktop testing • New Defects are used for

Device testing *Click the down arrow next to the icon to select either option.

4. Show Subtitles – see page 14 for details.

11

Using Sprinter – the Tools tab

1

2 The following numbers identify a functionality and correspond to a marker on the diagram at the right: 1. Report Defect – For our purposes,

either a Smart Defect or a New Defect will be used. • Smart Defects are used for

Desktop testing • New Defects are used for

Device testing *Click the down arrow next to the icon to select either option.

2. Annotated Screen Capture – for any

situation requiring a screen capture, click the paintbrush icon and follow these directions

a. Use the tools labeled at the right, in the Additional Tools tab, to annotate the screen capture that pops up.

b. Add the screen capture to a smart defect if necessary.

2a

2b

12

Using Sprinter – the Run Control tab

1 2 3 4

The following numbers identify a functionality and correspond to a marker on the diagram at the right: 1. User Action Capturing – FYI

ONLY: Captures user actions and can be reported to a developer. This button defaults to ON and should ALWAYS be ON.

2. Test Details – click to show details of the test case.

3. Test Status – Allows tester to assign a status (fail, pass, etc.) to the overall test case. In most cases, tester should not do this and instead pass/fail individual steps of the test case.

4. End Run – Click to end the test case run and return to the Sprinter test setup window.

13

Subtitles Mode

1

2

3 4 5 6

1. Show Subtitles – click to enter Subtitles Mode.

2. Subtitle Ribbon – shows the current test step and the expected result. If cursor is placed on ribbon, a toolbar will appear on top of the ribbon.

3. Step Navigation – can go forward/backward in step sequence.

4. Pass Step – click to pass the step 5. Fail Step – click to fail the step 6. Hide Subtitles – click to exit

Subtitles Mode. 7. In some cases, the ribbon

cannot display all of words with the step*. Simply exit Subtitles Mode to view in the regular Steps tab.

*The use of dual monitors, with HP ALM on the right screen makes things more efficient.

7

14

Reporting Defects – Standard Web Method

While there are a few different ways to report a defect, to simplify the process we will establish a standard method of reporting: 1. In the Tools tab, click the Annotated

Screen Capture icon (paintbrush) to pull up the current screen as a picture.

2. Use the Additional Tools tab (pictured to the right) to do any sort of appropriate annotations to help document the defect.

3. Once you are done annotating the screen capture, click the down button on the Report Defect icon, and select Smart Defect.

Note: While there is a New Defect option as well, this functionality will only be used for mobile device testing. The Smart Defect option will only be used for Standard Web testing.

15

1

2

3

3

Reporting Defects – Standard Web Method Once you are done annotating the screen capture, continue to follow these directions: 1. In the new window, ensure the first

three boxes are checked. • First box should be “All Steps to

Current” 2. In the same window, ensure that the

“Current Screen Capture” box is checked.

3. Click “Submit Defect” 4. The next window that pops up will

prompt the user to enter a Summary. For this, enter what browser you are using, followed by a hyphen and a short description of the defect.

(e.g: “IE8 – Outage Map Not Working”) 5. In the details tab, fill out the following

information into the blank fields: • Clarity ID: PROJ 633 (under web) • Severity: Ask Testing Coordinator • Defect Status: New • Functional Area: Standard Web

(folder under Outage Map) 6. Type relevant info in the description

box if needed 7. Click Page 2 tab to continue

1

2 3

4

5 7

16

6

Assigning Defects Assigning the defect is very important because we need to get the correct people started on fixing the defect. Navigate to the Page 2 tab to do this. 1. For newly reported defects, the

Assigned To field will be blank. Click the down arrow to assign it to the testing coordinator. Do so by typing in his/her user ID.

2. Testers can also double check to verify that the annotated screenshot taken early is attached to the defect.

3. Click ok to complete the reporting process.

17 *See page 21 for further details

1

2

3

1

2

3

Post Run Actions – Run Summary After the test run has completed, the Run Summary window is displayed. All testers should first alert the Testing Coordinator for further instructions. Some actions the tester can do include: 1. Tester can look to see number

of steps passed, failed, not completed, etc. (view will be different than from image at right).

2. Tester can check the duration. 3. Tester can go to the Results

menu to reexamine Submitted Defects, or to view all screenshots on the Storyboard.

4. Tester can email/print results.

3

4

18

Device Testing

19

• We will also be using Sprinter in our testing efforts on mobile devices such as Smartphones and Tablets. • Each tester will be assigned a Smartphone or Tablet • The Testing Coordinator will ensure that all assigned devices are pointing to the DEVL region • The testers will not have to capture screenshots while testing on the devices, except when reporting defects.

4

Reporting Defects – Smartphones and Tablets We will have only two uses for Sprinter in relation to device testing: 1. Defect Reporting 2. Efficiency Tracking (time

keeping) After Sprinter is running with a mobile test case, the user will navigate through the actual steps on their mobile device, but Pass, Fail, or report a defect using Sprinter. *If a defect is found, report it by clicking the Report Defect icon in the Steps tab, and selecting New Defect. Note: Remember to take appropriate screenshots on your device if it has that functionality.

20

*

Reporting Defects – Smartphones and Tablets After the New Defect window has appeared, execute the following instructions:

1. In the Summary bar, enter what device you are using, followed by a hyphen and a short description of the defect.

(e.g: “iPad – Outage Map Not Working”)

2. In the details tab, fill out the following information into the blank fields: • Clarity ID: PROJ 633 (under

web) • Severity: Ask Testing

Coordinator • Defect Status: New • Functional Area (under the

Outage Map folder): *If on a Smartphone,

select Smartphone **If on a Tablet, select

Tablet 3. Type relevant info in the description

box if needed

*Continue to next page to Assign the defect.

21

1

* **

3

4

2

Assigning Defects from Mobile Devices

22 *See page 21 for further details

1

2

3

Assigning the defect is very important because we need to get the correct people started on fixing the defect. Navigate to the Page 2 tab to do this. 1. For newly reported defects, the

Assigned To field will be blank. Click the down arrow to assign it to the testing coordinator. Do so by typing in his/her user ID.

2. If needed, testers can also attached a screen shot taken on a mobile device. Click the Attachments link, then when the screen changes, click the paperclip button to upload a file. It is similar to attaching a document on an email.

3. Click ok to complete the reporting process.

Saving Mobile Screenshots When testing on devices, we will include a screenshot with the defect report when necessary. The only devices that have screenshot taking capabilities are the iPhone, iPad and the Samsung Galaxy Tab. Look to the right for instructions on how to take screenshots. After the screenshot has been taken, email the picture to yourself and save it on the computer that you are working from. That way, there is a physical copy on the hard drive. *Attaching Screenshots to Defects: • Once the Attachments link is clicked,

select the icon (pictured at the right) to browse the hard drive and then upload the desired screenshot.

• Click back to the Details link to verify other assignment details.

23

iPhone/iPad Samsung Galaxy Tab

Press the home button and the lock button at the same time.

Press the button indicated by the picture below.

Screenshot taking Instructions

Questions?

SCANA Corporation | 2012