The following are a few resources that I personally use and recommend others use as well. Some of these are guides, lists or tools.
The report writer’s job is to describe the bug in a way that helps get it fixed. No one wants to read a bug report that doesn’t make sense, requires too much work to understand or is offensive. This document lays out some advice to help improve that process.
The following are some mindmaps (in xmind format) that I use regularly. Feel free to use them as a template to make your own changes to:
A list of tools that I use on a regular or semi-regular basis. This is both a look at what kinds of tools help make me productive but also a good reference for myself when I get a new computer.
Templates for Test Design
- Classic Equivalence Class table
- Risk Equivalence Class table
- What to Automate Worksheet (by Angie Jones)
Test Idea Catalogs
Test Idea Catalogs are a list of related items that are effective at finding information (or bugs) that are efficient to use. Here is a hopefully useful list of public ones:
- Elisabeth Hendrickson’s Test Heuristics Cheat Sheet
- Michael Hunter’s You are Not Done Yet Checklist
- My own Testing Guides (feel free to fork this)
- Context Driven Testing
- LAWST – The Los Altos Workshop on Software Testing
- Association for Software Testing
- A list of Software Testing Conferences