From ee6fb2df3807bef3d7b408a15b202a2e487d1d3e Mon Sep 17 00:00:00 2001 From: Sally Date: Tue, 22 Jan 2019 10:40:25 +1100 Subject: [PATCH] Updated Feature Testing Handbook (markdown) --- Feature-Testing-Handbook.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Feature-Testing-Handbook.md b/Feature-Testing-Handbook.md index 193cbe3..53f1764 100644 --- a/Feature-Testing-Handbook.md +++ b/Feature-Testing-Handbook.md @@ -125,10 +125,10 @@ Testers should record their detailed "Testing notes" in a Google doc in the glob The testing template is designed to be broken down into all the user cases which were tested, and the tester should describe what they tested and what the result was. The more detail the better. -**If the test passed colour the box green. ** +**If the test passed colour the box green.** Describe what worked, and perhaps put a screenshot if you think it's a good record. -**If it failed colour the box red. ** +**If it failed colour the box red.** Give a description of what didn't work. Include as much detail as you can such as what kind of user was involved and what actions led up to the error occurring. This helps the developer when they try to replicate the problem. Are there some situations where the error occurs, and others where it doesn't? If the errors is hard to replicate include this in the notes. **If you’re unsure, colour the box orange.**