Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Test Planner

A heuristic for analysing requirements and brainstorming test ideas
by

Louise Perold

on 24 January 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Test Planner

Test Planner
A heuristic for analysing requirements and brainstorming test ideas
How it helps me
Some things I try think about..
Test Planner
History



?
Test requirements

Test Scenarios

Test cases
Highlight any requirements not yet identified
Help clarify requirements – identify issues
Help to identify possible ideas
Help to clarify the scope – figure out what I don’t know
Helps me to plan the logistics for testing
Have used in planning reviews
I have no stupid questions*
Let me think of the 'improbable failures'
I can make it a working document - for my eyes only
I focus on 'What is the business problem to be solved'?
I try to let my mind go lateral and worry about it later
I try to always go back - never 'done'
No fear
I try and state things both broadly and specifically
I try and use at multiple levels
I try not to restate requirements - rather try re-frame
Description
Outstanding issues
How?
Success
Process

Talk to the function in my own words
What does the function do?
What was the business problem it was intended to solve?
How does it solve it?
Are there any open questions at this stage?
Placeholder
Keep adding to this section
What techniques might be applicable in testing this functionality?
What are the practical considerations in testing the function?
Identify the ways in which you would recognise the application was working
What are all the identifiable features or aspects of the function that could highlight that the requirement had been successfully implemented?
Identify the ways in which I would recognise the application was working
What are all the identifiable features or aspects of the function that could highlight that the requirement had been successfully implemented?
Free thinking brainstorm of all the ways that the application could fail
How could I make it fail?
How could it break?
What are some of the characteristics by which I would recognise that it wasn't working?
Pre-conditions
Post conditions
And then.......
Test data
What needs to be in place? - From a function point of view, from a testing logistics point of view
What is the end state? Where will we end up? Anything we need to do to rerun?
Identify all the data needed for - techniques identified, success, failure
Cross check with requirements, rinse and repeat
Identifying techniques
Functional
Domain
Negative
Combination
UI / Visual state transition
Insert your toolbox here
Confirmation of the rules
Works for all paths - success, alternate, error
Boundaries of business rules
Input field validations
Field validations on messages/ interfaces
Parameter
How could I break it?
How could it not work?
How could we fool it?
Combination of variables together
Does the screen look and work as specified?
Usability
Every action from every screen
Failure
CopenhagenContext
Full transcript