Application Lifecycle Management and Application Transformation Blog
Sharing HP’s point of view on Application Lifecycle Management, sharing customer best practices and advice on managing the lifecycle of applications from concept to retirement.

A closer look at the manual test capabilities of HP Sprinter

While I was at HP Discover Frankfurt I had the opportunity to discuss manual testing and HP Sprinter with Michael “Doc” Deady.  HP Sprinter is the manual testing functionality of HP Application Lifecycle Management. If you have ALM, then you have Sprinter.


We sat and discussed how Sprinter enhances the abilities of your testers, thereby increasing their speed—and your project speed in the process.  And we all know that everything is about speed these days.


I also got the chance to ask him about:

  • How Sprinter works in an Agile environment
  • Exploratory testing
  • Testing documentation
  • User case studies
  • Plus, many more topics



Watch the video of our conversation here:



Feel free to reach out to me if you have any additional questions about Sprinter or ALM in the comments section below.


KA11 ‎04-03-2013 05:55 PM - edited ‎04-03-2013 05:56 PM

Being a new HP contractor, this video series was a great introduction to HP  tools used for software development Script creation, testing and analysis. This is a big aide to on boarding  the Complex IT environment. Thanks

QCresearcher | ‎04-24-2013 07:14 AM

Brian, great introductory video but I have a question about reporting on Sprinter results. Our team uses an Execution Report that we built in the Dashboard/Analysis View module to send to our customer for their signoff. It is very simple. It lists the Test, Test Description, Test Steps, and Test Step Attachments(screen shots). The report works fine if we ran the test using Manual Runner. If we use Sprinter for one of the tests, the same report will NOT give the test steps or the attachments for the test run using Sprinter. I know from researching this that Sprinter does not store its results in the database like Manual Runner does so I understand why we're not seeing these things on the report. My question is, is there any way we can create a report that gives us this same information we were getting on the Manual Runner report, in other words, can a report be created that will list the Test Name, Test Description, Test Steps(Description, Expected, and Actual boxes), and the Test Step Attachments(screen shots) after running the test using Sprinter? Thanks for your help. Keep up the good work.

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Showing results for 
Search instead for 
Do you mean 
About the Author
I have more than 12 years in IT, with over 10 years working with the HP Quality Management suite of tools—seven as a Professional Services c...

Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.