Article Options

A closer look at the manual test capabilities of HP Sprinter

 
BrianPalagyi| February 21, 2013
2 Comments

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.

 HPblogfooter.jpg

Tags: application testing| exploratory testing| testing ability
Labels: HP Agile| HP Application Lifecycle Management| HP Sprinter| Manual Testing
Labels:
Comments
KA11 ‎04-03-2013 05:55 PM - edited ‎04-03-2013 05:56 PM
Options

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

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

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.

0
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.
 
Search
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About the Author(s)
  • 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 consultant for Mercury/HP. Additionally, I am the Regional Practice Lead for the Quality Management Strategy and Solutions organization which helps drive inovation in the areas of Best Practices and constancy of delivery.
  • Bruce Randall is a Sr. Manager Product Marketing for HP’s Project and Portfolio Management and Application Portfolio management software solutions, has presented at numerous industry forums and continually works with HP PPM/APM customers, prospects and other luminaries within the PPM community.
  • This account is for guest bloggers. The blog post will identify the blogger.
  • Kelly has over 20 years experience with enterprise systems and software in individual contributor and manager roles across product management, business development and product marketing. A majority of my focus has been in areas directly related to applications spanning from developer environments, enterprise Java, integration middleware, SOA infrastructure, SOA Governance and now application lifecycle management. Kelly has a B.S. in Computer Science from California Polytechnic State University, San Luis Obispo and an MBA from the University of Santa Clara.
  • Malcolm is a functional architect, currently focusing on best practices and methodologies in automated testing.
  • Matthew Morgan is Vice President of Product Marketing for HP Software and serves as the marketing business owner for the Hybrid IT and Cloud product lines. His 20 year tenure in the Application Lifecycle Management industry includes a decade at Mercury Interactive, where he led product management and product marketing teams that created and commercialized many generations of Quality and Performance Center products. You can follow Mr. Morgan on twitter @forwardtension, connect with him on LinkedIN., or check out his personal blog at http://forwardtension.com
  • Michael Deady is a Pr. Consultant & Solution Architect for HP Professional Service and HP's ALM Evangelist for IT Experts Community. He specializes in software development, testing, and security. He also loves science fiction movies and anything to do with Texas.
  • HP IT solution architect in the Product Development IT organization. Working on HP internal usage of ALM and SDLC processes and tools.
  • WW Sr Product Marketing Manager for HP ITPS VP of Apps & HP Load Runner


Follow Us