CS-6302 APPLICATION LIFECYCLE MGT

HP SPRINTER 12.0
Page |1

Module 008 HP SPRINTER 12.0

“Quality is never an accident; it is always the result of intelligent effort.”

– John Ruskin

Overview of the Course

Students learn how to manage quality information throughout the

development cycle, from constructing requirements, designing and executing tests,
through monitoring defects.

Students learn how to work with the Desktop client and the new Web client. In
addition, using the HP Sprinter and its new features are discussed, including:

 Using HP Sprinter on manual tests

 Using version control to keep track of changes and also to create and
manage libraries
 Creating and comparing baselines
 Importing and exporting from Microsoft Excel
 Generating reports and graphs using the dashboard
 Using cross-project customization and Project Planning and Tracking
(PPT)

Objectives:
After completing this module, you should be able to:

 Review and understand the manual test lifecycle

 Understand Sprinter features and functionality

 Use Sprinter

 Author tests

 Perform exploratory testing

 Define storyboarding
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
Page |2

 Use Sprinter to long defects

Researching beyond the coverage of this module is highly encouraged to
supplement your understanding of the topics covered. Always, think and see
beyond the box.
The citation provided is a guideline. Please check each citation for accuracy
before use.

So, what are we waiting for? Let us now explore the Lifecycle
Management of Application

Introduction

Adopting the Shift – Manual Testing

Testing is shifting to adopt Agile and Continuous Integration
methodologies.

Manual Testing Today must be Modernized

Minimizing QA – Development Tension

CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
Page |3

Introducing HP Sprinter

Sprinter Overview

HP Sprinter is HP's solution for manual testing. Sprinter provides

advanced functionality and tools to make manual testing more efficient and
effective.
Manual testing often requires that you leave your testing application to
accomplish tasks related to your test. For example, you might need to use
graphic software to take a screen capture of your application, you might want
to record a movie of the application during the test, and you need to switch to
your defect tracking software to report defects.
Sprinter enables you to accomplish these tasks without disrupting your
test flow. With Sprinter, you can also perform many of the repetitive and tedious
tasks of manual testing automatically. Sprinter includes many tools to help you
detect and submit defects. These features ensure that you can perform all the
tasks necessary for your manual test with minimum interruptions to your
testing work.
Sprinter runs manual tests in ALM 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 do want to
interrupt your test run
 Create and annotate screen captures and record movies of your run
In addition 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

Sprinter – New Features in Version 12

 Integration with UFT – When working in Power mode, you can save
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
Page |4

manual Sprinter can import the XML file and convert it to an automated
GUI test.
 Performance Improvements – Performance improvements have been
made in many areas of the product, such as opening, loading, and running
tests.
 Manual Mapping tests as XML files which are compatible with HP Unified
Functional Testing (UFT). In UFT you – In Data Injection, you can
manually map fields in your application to columns in your data set.
 Mobile Application Testing – You can now test Web or Native
applications using a cloud mobile provider (Perfecto Mobile).
 Expanded View – You can now view screen captures, in the Step tab, as
full images in Run mode.
 Link to existing defects – You can now link a test run to an existing defect
 ALM Reporting Capabilities Improvements – You can now see the run
steps of manual tests executed with Sprinter in ALM reports.

Welcome Dialog Box

Welcome dialog box options let you open or create a test or business
component. To access the Welcome dialog box, do one of the following:
 Start Sprinter.
 In the main window, select Welcome Screen from the drop-down menu
next to the Help button.
When you select the Show on startup option, Sprinter displays the Welcome
dialog box each time it is launched. You can configure Sprinter to bypass the
Welcome dialog box in the General Settings pane (Settings dialog box) or you
can just de-select the Show on Start-up checkbox.

Starting to Use 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.
To launch HP Sprinter from the desktop, complete the following steps:
1. Click the Sprinter shortcut on the desktop. HP Sprinter opens showing
the Open a Test window. Close the Open a Test window.
2. Double-click the HP ALM connection button.
3. Enter the address, user name, and password and click the Authenticate
button.
4. Enter the domain and project and check the Reconnect on Startup check
box since you typically work on the same HP ALM server.
5. Click the Login button. Sprinter connects to HP ALM and the Open dialog
box appears.
General Settings
Select your General Settings choices.
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
Page |5

Sprinter Main Window – Plan Area

The main Sprinter window enables you to manage your test and
components, set test and component definitions, view test results, and configure
Sprinter settings.
Test and Component Authoring Overview
Sprinter’s Plan mode enables you to create and edit tests or components
directly in Sprinter and save them to ALM. You can create and edit steps
manually in the Steps tab, or use Steps Capture to automatically generate steps
based on your user actions. You can then add screen captures or attachments to
steps. You can define input parameters for each step, and also output
parameters for components.
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. It allows you to
outline a strategy for achieving your requirements, as defined in the
Requirements module.
Considerations for Planning Application Testing
How should you test your application? – Which testing techniques will
you use (stress tests, security tests, performance and load tests)?
How will you handle defects (severity classification, authorization to open and
close defects)?
What resources do you require? – What resources do you require to test
(personnel, hardware, and so forth)? When will the various tasks be completed?
As an example, consider a flight reservation application that lets you manage
flight scheduling, passenger bookings, and ticket sales. Testing requires
designing both manual and automated tests. You could assign testing personnel
with programming experience the task of designing automated tests, while non-
programmers could design manual tests.
To access the Plan area, complete the following steps:
1. Start Sprinter and close the Welcome window, if open.
2. Select Plan from the main toolbar.
3. Click the New button in the Tests and Components list to create a new
test.
4. In the Test tab, in the Details pane, provide information for the test, such
as description and comments.
5. Add an attachment and Parameters that will be used for the test.
New Button
You use the New button to create a new test or component and add it to
the Tests and Components list.
Drop-down options:
 New HP ALM Test – Adds a new blank test to the Tests and Components
list.
 New HP ALM Business Component – Adds a new component to the Tests
and Components list.
Open Button
You use the Open button to add an existing test or component to the Tests and
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
Page |6

Components list.
Drop-down options:
 Open HP ALM Test (Default) – Displays the Open ALM Test dialog box.
The tests you select are added to the Tests and Components list.
 Open HP ALM Business Component – Displays the Open ALM Business
Component dialog box. The components you select are added to the Tests
and Components list.
Save Button
You use the Save button to display the Save/Save As dialog box, which
enables you to save the selected tests or components in the Tests and
Components list.
Drop-down options:
 Save – Saves the selected test or component.
 Save As – Saves a copy of the selected test or component to the specified
location.
Note: The save options are disabled when more than one test or component is
selected.

Authoring a Test or Component

Creating Test and Business Components

Sprinter's Plan mode enables you to create and edit tests or components
directly in Sprinter and save them to the Application Lifecycle Management. You
can create and edit steps manually in the Steps tab, or use Steps Capture to
automatically generate steps based on your user actions. You can then add
screen captures or attachments to steps. You can define input parameters for
each step, and also output parameters for components.
Creating a New Test
To create a new test, click the New button in the Plan area. The new test
is added to the Tests and Components list. To create a new business component,
select New →New HP ALM Business Component. The new business component
is added to the Tests and Components list.
The New HP ALM Test button opens the Authoring pane and adds a new test
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
Page |7

entry to the Tests and Components list. If you are not connected to ALM, the
ALM Connection dialog box opens to enable you to connect to ALM.
Steps Tab
Use the Steps tab to:
 Add, edit, move, and delete test or component steps
 Import steps from Excel or CSV files
 Format steps using rich text editing capabilities
 Add screen captures and attachments to steps
 Insert calls to an external ALM test
 Insert parameters to steps
Find Section
The ribbon’s Find section lets you search the text associated with the steps.
The UI elements include:
 UI Elements Description <search text> – You can search for text in the
Name, Description, or Expected Results fields, or in any user-defined
field.
 Search Down/Up – You can choose the direction of the search.
 Match whole word – This instructs the search engine to find a whole
word.

The Steps Tab – Manually Add and Edit Steps

The ribbon’s Step section lets you manage steps of the test or component.
The UI elements include:

– Adds a new step to the steps grid. Drop-down options include:

 After Current Step (Default) (Alt+N)
 Before Current Step (Shift+Alt+N)
 After All Steps (Ctrl+Alt+N)

– Starts a Steps Capture session, in which you navigate your application

and perform user actions as you would in a regular run session. Sprinter
captures each user action, converts it to a step, and adds it after the selected step
in the steps grid.

– Cut/Copy/Paste Steps allows you to cut, copy, and paste individual

or multiple steps.

– Move Step Up/Down. Moves the selected step up or down the steps grid.
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
Page |8

– Delete Steps. Deletes the selected steps.

– Insert Parameter. Opens the Insert Parameter dialog box that enables
you to insert a parameter at the cursor’s location in the Description or Expected
Results fields.

– Add Attachment. Adds a file from the file system as an attachment to the
selected step (tests only).

– Screen Capture. Enables you to add a screen capture to the selected

step (alt+C). Drop-down options include:
 Take Screen Capture – Opens the Capture sidebar, allowing you to take a
screen capture of the desktop and attach it to the selected step.
 Delete Screen Capture – Removes the attached screen capture from the
selected step.

The Steps Tab – Steps Capture

You must first identify the application that you will be using. Then you
use the Steps Capture feature to automatically generate test steps based on your
user actions. The actions that you perform on the application during the test are
captured and saved as steps. You have the option to save each single action as a
new step or to group actions into a step.

Authoring Tests – Manage Test Parameters

You add parameters to your tests and/or components using the

Parameters pane of the Test/Components tab. You can then associate these
parameters with steps in the Steps tab.

Authoring Tests – Attachments Pane

CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
Page |9

Running Test Concepts

Running a Test with Steps

Sprinter enables you to run steps that you manually add to your test or
those that you imported from an external file.
When you run your test, the steps are displayed in the Steps sidebar. From the
Steps sidebar you can:
 Navigate your steps
 Mark the status of your steps
 Modify the actual results of your steps ␣ Add attachments to steps
 Add screen captures to the actual results of your steps
 Edit the details of your steps
 Submit defects
 Search in your steps
 View the parameters in your steps (Business Process Testing only)
The Steps sidebar also provides a Subtitles mode, which displays your step
descriptions and enables you to navigate and mark your steps in a one-line
subtitle, while providing more screen real estate for your application.
When you finish your run, Sprinter saves your changes to the run results for
your run. If you made changes to the details of your steps, Sprinter prompts you
to save your changes to the Test Plan module in Application Lifecycle
Management.
If your test is checked-in, Sprinter automatically checks it out, saves your
changes, and checks it back in. If your test is checked-out to another user,
Sprinter warns you that your changes cannot be saved.
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, complete the following steps:
1. Ensure that the Steps sidebar opens automatically. If not, click the Steps
tab.
2. Follow the instructions for the first test step. In this example, you enter
the Agent Name.
3. Evaluate whether the application is responding as expected and then
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 10

select either Pass or Fail from the tool bar.

4. Continue to proceed through the steps until you have finished.

Improving Communication While Running Tests

Enter a Smart Defect

To enter a smart defect, complete the following steps:
1. Click the drop-down menu for the Smart Defect button. Select the 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.
Add a Defect Reminder
To add a defect reminder, complete the following steps:
1. Click the drop-down menu for the Smart Defect button. Select the Add
Defect Reminder option.
2. In the Defect Reminder dialog, type the description of the defect and click
the OK button.

Simplifying and Improving Defect Communication

Annotations highlight the problem in the images that are attached to a

step, run, actual result or defect.
To annotate a screen capture, complete the following steps:
1. Click the Save Annotation As Actual Result button in the Actual Result
dialog box. The annotation workspace is displayed.
2. Use the annotation tools to mark up the screen capture.
3. Click the Save To Actual Result button.
4. Click the Close button. The annotated image is displayed in the image
section of the Actual Result dialog box.

The Test Run Summary

To View the Run Summary, complete the following steps:

1. Click the Stop button in the Run Control sidebar to end the run. The
sidebars close and the Run Summary pane is displayed in the main
window. 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.
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 11

2. Select the Submitted Defects node to view a list of the defects you
submitted during your test. Click Defect ID Number to open the HP ALM
Defect Details dialog box for that defect.
3. 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 ALM.
4. 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.

Running Tests in Power Mode

Power Mode Overview

When you run a Sprinter test in Power mode, Sprinter is able to learn
your application's display and identify its objects. This ability gives you access
to Sprinter's advanced functionality including data injection, recording and
replaying macros, and working with mirroring (replicating user actions on
multiple computers).
When you are in Power mode, Sprinter keeps a record of all your user
actions, which you can view as a list or in the Storyboard at the end of your run.
You can also include the list of your steps or user actions in any defect you
submit to let Sprinter automatically create a defect scenario for you.
You can export the list of user actions at the end of your run to an Excel
spreadsheet, modify them for use as steps, and then import them to a test in the
future.
After a test run, you can use the test steps as a template and automatically
generate a test.
To use Power mode, complete the following steps:
1. Click the Off button in the Power Mode group under the Tests list. The
Welcome to Power Mode! dialog box is displayed.
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 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.

Exploratory Testing

With Power mode enabled, you can navigate your application without
the need to follow predefined steps. While you navigate your application,
Sprinter captures each user action that you perform. You can then export these
user actions to a new manual test or to an Excel file.
If your test does not have steps, you can begin your test run and perform
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 12

exploratory user actions.

Exploring Your Application
Begin the run session and perform any user action in your application. Sprinter
captures all of the user actions that you perform. Use the Run Control sidebar to
manage how you capture user actions and view the status of your exploratory
run.
Reviewing and Exporting the Captured User Actions
At the end of the run session, review the captured user actions in the User
Actions pane of the Results Group.
In this pane, you can export the captured user actions to:
 A new manual test with steps – In the new test, each user action is
converted to a manual step. Before saving the new test to ALM, you can
edit its details, steps, and any user-defined information that your ALM
project requires.
 An Excel or CSV file – This file contains all the user actions that you
performed during the run session. You can edit the content of the file and
then import it into an existing test or component.

Facilitating Agile Testing and Exploratory Testing

You can navigate your application without predefined steps and Sprinter
automatically logs all user actions performed during the test and creates a user
log of those actions. You can then export these actions to a new manual test, to
a UFT, or to an Excel file.

Minimizing Repetitive and Tedious Work

Data injection enables you to select rows of data to be sent automatically

to the relevant locations in a form.
Creating Data Injection Data Sets
To create data injection data sets, complete the following steps:
1. Click the Data Injection node under the Power Mode group. The Data
Injection frame is displayed on the right side.
2. To add a data set from ALM, click the Add Data Set drop-down and select
Add From HP ALM. The Data Set Details dialog box is displayed.
3. Click the Browse button. The Resources tree is displayed. Expand the
Resources tree and locate the data set on your system.
4. Click the Open button. The name of the resource is displayed as the
default name.
5. Click the OK button. The data set is added to the Data Injection frame.
Running in Power Mode Using Data Injection
To run in Power mode using data injection, complete the following steps:
1. Click the Run the Active Test button. The Data Injection sidebar is
displayed on the perimeter of the display.
2. Click the Data Injection sidebar.
3. Click a row of data and click the Inject Data button. The screen grays out
and shows Analyzing... until the data injection completes. If the data
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 13

injection completes successfully, a green tick mark displays in the Data

Injection tab. If the data injection does not complete successfully, a red
cross mark displays in the Data Injection tab.
4. Double-click the tick mark or cross mark. The Data Injection Status
dialog box is displayed and shows the status.

Minimizing Repetitive Tests and Saving Time

Mirroring lets you 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, complete the following steps:
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 being used as the secondary machine.
4. In the Run Configuration tab, choose an option for configuring how
Sprinter would launch the application on the machine and choose a
browser.
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 and click OK.

Running Tests with Macros

During the testing process, parts of your test might require you to
perform a series of user actions that you want Sprinter to perform for you. You
might also have parts of your test that involve performing the same set of
actions in multiple areas of your application. Having Sprinter perform the set of
actions can save testing time and reduce errors.
A macro is a series of actions that you can save and run as a single command.
Sprinter can perform these actions for you when you create and run macros. For
example, you might want to use macros to:
 Automate a login procedure
 Perform a series of introductory steps to set up your application for
testing
Sprinter only saves a macro if it contains at least one user action. Your user
actions are only recorded after they are completed. For edit boxes and combo
boxes, the action is not complete, and will not be recorded until you move the
focus off the box.
Recording a Macro
To record a macro, complete the following steps:
1. Click the Macros sidebar.
2. Click the Record Macro button.
3. Perform the steps that you want to record in the macro.
4. Click the Macros sidebar again.
5. Click the Stop Recording button. The Macro Details dialog box opens.
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 14

6. Enter the name and description for the macro.

7. Click the OK button.
Running a Macro
To run a macro, complete the following steps:
1. Click the Macros sidebar.
2. Select a macro from the drop-down list of macros.
3. Click the Run button. Once the macro runs successfully, a green tick mark
displays in the Macros tab. If the macro does not run successfully, a red
cross mark displays in the Macros tab.
4. Double-click 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.

Defect Scanner Overview

During the testing process, you might want to check that different
aspects of your application behave or display correctly. You can select which
scanners to use both prior to the run session and during the run session. After
each scan is completed, you can see the scan results in the Scan Results Viewer.
In the Scan Results Viewer, you can perform several actions, such as creating
smart defects and defect reminders.
Sprinter includes the following scanners:
 Broken links scanner – This scanner, relevant only for web applications,
checks your application for broken hyperlinks and missing referenced
content. You can set the threshold time. This is the time in seconds after
which the link is considered broken.
 Localization scanner – This scanner checks your application for errors
resulting from translating the application’s UI into different languages.
You can scan for the following issues:
 Incomplete strings – Suppose that after translating the user
interface strings in your application, the main title of the page is
too long to be displayed within the title bar. When this option is
selected, the Localization scanner identifies the string as
incomplete. Make sure to set the target language, as the scanner
performs a check against this language during the scan.
 Untranslated strings – Suppose that after translating the UI
strings of your application, you want to verify that all of the
strings were translated from the source language to the target
language. When this option is selected, the Localization scanner
compares any string that is not spelled correctly with both the
target dictionary and the source dictionary. If the string is found
in the source dictionary, the scanner identifies the string as an
untranslated.eral action, such as creating smart defects and defect
reminders.
 Spell check scanner – This scanner checks your application for spelling
errors. You can define up to two dictionaries for the scanner to use. This
enables you to check spelling for applications that contain strings in
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 15

more than one language.

 Web standards scanner – This scanner checks that the web page
complies with web standards for HTML validity, as defined by the World
Wide Web Consortium (W3C). The scanner detects and reports any web
standard errors that are found in the web page during the run session.
The Web standards scanner is available only if you select a web
application in the Application pane (Power Mode Group).
 Custom scanner – Sprinter allows you to extend the scanner’s
capabilities by defining custom scanners. This allows you to design a
scanner that detects the desired items in your application. You can use a
sample scanner provided with Sprinter as a starting point for designing
your own custom scanner.

Scanner Configuration

To use scanners, you must first enable Power mode and configure an
application for your test.
Configuring Scanner Settings
To configure scanner settings, complete the following steps:
1. Before the run session begins, use the Scanners pane (Power Mode
group) to turn on the relevant scanners.
2. During the run session, in the Scanners sidebar, click the Scanner
Settings button. The Scanner Settings dialog opens. This dialog box
contains all of the available settings that the Scanners pane (Power Mode
group) contains.
Scanning Your Application During a Run Session
In the Scanners sidebar, click the Start Scan button. The progress
window opens, displaying the status of each scanner.
Analyzing Scan Results
After the scan ends, click Continue in the Scan Progress window, to open
the Scan Results Viewer. Handle the results for each scanner by creating a defect
or a defect reminder, or performing a custom action. For example, for spell
check scan results, add the word to a dictionary.
Tip: If you closed the Scan Results Viewer, click the Last Scan Results button in
the Scanners sidebar to display the results of the last scan.

The Scan Progress Window

To access the Scan Progress window, during a run session, click the Start
Scan button on the Scanners Sidebar tab.
By default, only summary information is displayed. You can expand the
window to view detailed information about each scanner. If all scans run
successfully and results are found, this window closes after the scan is
completed, and the Scan Results Viewer opens. If one or more scans fail, the
failure reason is displayed in a tooltip when you hover over the scanner name.
The UI elements include (unlabelled elements are shown in angle brackets):
 <Scan status> – The overall progress of the scan
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 16

 Potential defects found – The total number of scan results, which might
indicate defects in the application
 <Scan status details> – The scanner name, potential defects, and status
for each scanner that you selected to use
 Details – Shows or hides the scan status details

The Scan Results Viewer

After each scan completes, the scan results display in the Scan Results
Viewer. In the Scan Results Viewer, you can perform several actions, such as
creating smart defects and defect reminders.
The Scan Results Viewer also enables you to address the results by
submitting defects to ALM based on the results. You can also create defect
reminders to be submitted after the run session ends.
The Scan Results Viewer displays results only from the last scan that you
performed. The Scan Results Viewer is available only during the run session.
UI elements include (unlabelled elements are shown in angle brackets):

– Opens the Smart Defect Settings dialog box enabling you to

automatically include defect scenario information in your defect. The defect
summary includes a description of the selected results.

– Opens the Defect Reminder dialog box enabling you to add a

reminder to open a defect for the selected results at a later time.
 Add to Target Dictionary – Adds the selected results to the target
dictionary. Available only when localization results are selected.
 Add to Dictionary (<language>) – Adds the selected results to the
primary dictionary. Available only when spell check results are selected.
 Exclude Category – Creates a rule that excludes the selected results
category from future scans. Available only when Web Standards results
are selected.
 Scan Results – The list of results for each scanner: Summary and Action.
1. Click the arrow adjacent to each scanner to expand its results.
2. Select one or more results in the list to perform actions on them using
the right- click menu or toolbar buttons.
3. To perform an action on all results for a specific scanner, select its
parent node and expand the right-click menu.
 <Results display> – The display of the results. The results are indicated
in red boxes. This pane also contains a slider control, which allows you
to zoom in or out.
Note:
 Results are not available when Broken Links or Web Standards
results are selected.
 If the results are located outside of the captured area of the
application, they are not shown in the display.
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 17

 <Results description> – A textual description of the selected results.

Scanning – Spell Check

The Scanners pane and the Scanner Settings dialog box enable you to
select which scanners to use during a run session. You can also configure
settings for each scanner.
The example in the slide shows a Spell Check failure. Departing From and
Service Classes have errors. Spell check runs using the default dictionary. You
can add dictionaries.

The Storyboard Window

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 run the test with multiple configurations, you can view
the differences between the displays of different computers.
You can select the Storyboard node and the Storyboard opens. The top of
the Storyboard displays a screen capture of your 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 your run.
Viewing the Storyboard
To view the storyboard, complete the following steps:
1. Select the Storyboard node to open the storyboard. 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.
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.
5. Use the Filter Defects Reminders button to show only those actions
where you created a defect reminder.
6. Use the Filter Comments button to show only those actions where you
added a comment. 7. Use the Filter Differences button to show only those
actions where differences were found.
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 18

Storyboarding

Accessing the Storyboard Window

To access the Storyboard window, do one of the following:
 During a run, click Tools sidebar
 Storyboard. Select the Results →Storyboard node.
 Right-click a test in the Test Runs list, and select Show All Runs. The Test
<Test Name>: All Runs dialog box is displayed. Click the Storyboard
button.
Exporting Storyboards
You can export a storyboard to a Word or PDF file. This file contains the run
summary, step status, and defect information for the run session.

The New Mobile Settings Pane

Sprinter for Testing Real Mobile Devices

Sprinter software gives you the ability to test web or native applications
using a cloud mobile provider.
The solution:
 Testing is done using real devices all over the world.
 Devices are launched over the cloud with zero setup time and zero time
to maintain.
 The cloud can be either private or public.
Key Benefits:
 Accelerate and improve the efficiency of moblie manual testing
 Expand and minimize floating sidebars, as needed, to maximize real
estate
 Accelerate defect remediation
 Capture and record images of test actions and results
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 19

This is the screen presented after you choose a device and start a test.
Steps, Annotation Tools, and Run Control are the Sprinter main capabilities tabs
that are available during your test run.
The Centered box is the handset itself, a real one, and when you perform
actions, those actions are being executed on the device. You can test on a variety
of smart phones and tables from inside Sprinter.
Complete testing information, including active screenshots and video
recordings, is embedded into the Sprinter report.
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 20

References and Supplementary Materials

Books and Journals

Micro. Customized Application Lifecycle Management 12.0 Essentials

Student Guide
Hewlett-Packard Development Company, L.P.
http://hp.com/software/education

Markov, Georgi and Druzhinina, Olga; 2011; Towards an industrial ALM

(Application Lifecycle) Tool Integration; Blekinge Institute of Technology,
School of Computing
CS-6302 APPLICATION LIFECYCLE MGT
HP SPRINTER 12.0
P a g e | 21