The document outlines a 6 step process for writing test cases: 1. Use exploratory testing methods to initially document an application. 2. Find and document defects during the first run. 3. Clearly define test expectations and criteria. 4. Parameterize and modularize test scripts to make them reusable. 5. Automate tests that were initially performed manually. 6. Make test suites enterprise-ready by enabling sharing and reuse across teams.

1. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
6 Easy Steps to Write
Test Cases
Using Exploratory testing methods and how they can be leveraged
in automation leading practices

2. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
2
APP’s 12
ALM 12
ALI 12
AGM 2
PC 12
LR 12
Sprinter
UFT 12
HPA
Defect
Mobile
Mobile
IDE
SCM
Adoption
Readiness
Tool
Business
Process
Testing
Functional
API
Security
Data &
Web
Security
PPM
HPA
Issue
Management
Test Planning
& Execution
Release
Management
Build
Integration
Design
Management
Release
Management
Support
Professorial
Services
Center of
Excellence
Solutions &
Tools
Training
SaaS
Lab
Manager VTS
Service
Virtualization
CDA
Best
Practices
APP’s Map
Accelerators
Score
Card
HP
Community

3. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
3
Testing in 6 Easy Steps
When it comes to testing, why not take the easy road.. In just 6 little steps..
Enterprise
• Share
• Reuse
• Do more!
Automate
• Manual is
quick and dirty
• Automation is
in there in the
long haul.
Harden
• Make sure we
are clear and
consistent with
our results
• Allows for
others to
understand
what we did.
Defects
• Defects are a
good thing in
QA, so find
them and
document them
Explorator
y
• Get it
documented
• Get it tested
early!
Results
• Save it,
• Put in checks
• Use Data
What could be easier!? Well, yes, a lot of things. Okay, let’s have a breakdown

4. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
4
Step 1 – Ad-Hoc/Exploratory Documentation
You need the initial groundwork of the app,
but you can start with the basics and ‘fresh
from the oven’ software to get you started.
Leverage Sprinter to perform the initial
documentation for you while you relax and
get back to what you wanted to do, testing
the application.

5. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
5
Step 2 – First Run Defects
• Humans are
imperfect.
• Software is
developed by
Humans.
• Software is
imperfect.. So
find them defects.

6. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
6
Step 3 – Clearly Define Expectations
Take the time to clearly
define your entry and exit
criteria for each step.
• Provides an audit trail of
what you were testing
• Allows easy reading of
results to prove out issues
• Documentation for the
other resources that will
have to pick up your tests
when you leave and are
big and famous

7. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
7
Step 4 – Harden your Script
Do the work and get credit for it!
You now have something that
works, now make it workable
• Parameterize
• Error handling
• Modularization
• Inputs and Outputs
This is where you save it and
make sure that it is usable for
others, then you get the ROI
credits you deserver.

8. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
8
Step 5 – Automation Nation
Manual for first
iteration, but
transfer to
automation as
soon
• Better speed on
iteration +1
testing
• Spend your
time doing
something you
like, more
testing usually

9. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
9
Step 6 – Make it Enterprise Ready
Take what you know, and
make it available for the rest
of the organization
Get your Reuse on!

10. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Demo

11. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Thank you
Exploratory
Defects
Results Harden
Automate
Enterprise

12. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.