I remember in my early days of testing I was given the task of creating a test plan. I had little experience and the only guidance I got was being handed a word template to base the plan on.  Basically, I was expected to fill in the blanks.  I’m glad that’s behind me!

The problem with test planning in many cases is the lack of flexibility testers are given, not to mention the fact that the actual Test Plan Documents hardly get looked at once completed.

This is why I created this MindMap.  I did it kind of quickly, so I’m hoping fellow testers will kindly help expand on this.  I am sure there are valuable points missing.

The MindMap image is below. Followed by downloadable files. Followed by a text checklist. Enjoy!

Download  - ZIP File includes – png, PDF, smmx, text, opml and mm file types.

Interesting links we came across during our research:

• http://lisacrispin.com/wordpress/2011/02/28/using-mind-maps-for-test-planning/
• http://www.bettertesting.co.uk/content/?p=635
• http://googletesting.blogspot.co.uk/2011/09/10-minute-test-plan.html
• http://www.satisfice.com/tools/satisfice-cm.pdf
• http://www.satisfice.com/testmethod.shtml

Test Planning

Types and approaches to testing to consider

• Performance
• Load
• Stress
• Functional
• Usability
• Security
• Accessibility
• User Testing
• UAT
• Compatibility
• Exploratory
• Scenarios
• Alpha/Beta
• Prototypes
• Unit Testing
• Regression
• Specification Based Testing

Test Plan Formats

• Written documents
• MindMaps
• Wiki
• Spreadsheets
• Checklists
• Flow diagrams
• White boards
• Post it notes

Resources

Test lab

• Platforms
• Tools
• Issue Tracker
• Test Library
• Test Management

People

• Test Team
• Users
• Product Team
• Clients

Information

• Documents
• Requirements
• User Guides
• Web materials
• Product history

What are the requirements?

• Achieve standards?
• What is the goal or mission?
• Find important problems?
• Accountability
• Satisfy stakeholders
• Cost effectiveness
• Effectiveness
• What testing outputs need to be created, and how? Test Cases, Test Plan, Test Strategy, Bug Management & Exploratory testing results
• When is testing done?

Project Management

• Plans change – Adapt!
• Get feedback
• Time
• What’s the schedule?
• Releases
• Availability of people
• Availability of documentation
• Anything that could block testing?
• Relationships
• Collaborate
• Share knowledge
• Teach others
• Learn from other product team members

Analyse Product

Attributes – What is testing and the product meant to deliver?

• Functional?
• Secure?
• Usable?
• Fast?
• Innovative?

Think of the product in terms of ‘components’

• Features
• Stories
• Modules
• Classes
• Design

Capabilities

• What can the user do?
• Who are the users?
• What can’t the users do?

Data – what does the product process?

• What goes in?
• What goes out?
• What pre-exists?
• How does it change over time?
• Large or small amounts of data
• Order of data – the sequence

Use of software

• Who are the users?
• What environments will it be exposed to!?
• How will it likely be used?
• Negative use
• Malicious
• Ignorant
• Mistaken
• Carelessness

Structure – what is the product made of?

• Interface
• Code
• Hardware
• Informational Products
• Internal factors
• External Factors
• What does time have to do with testing? Input/output; Speed – fast, slow, changing pace; Concurrency