From 4e18ca5b051d9b5388da3cee6894c3a4a5ba4bd2 Mon Sep 17 00:00:00 2001 From: Sally Date: Thu, 25 Jan 2018 14:26:39 +1100 Subject: [PATCH] Updated Feature Testing Handbook (markdown) --- Feature-Testing-Handbook.md | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/Feature-Testing-Handbook.md b/Feature-Testing-Handbook.md index b5af76a..fd57b53 100644 --- a/Feature-Testing-Handbook.md +++ b/Feature-Testing-Handbook.md @@ -52,15 +52,10 @@ Does the new code interact accurately with other features, like private shopfron Testing notes are recorded in google documents. Use this as a template - https://docs.google.com/document/d/16UZXJdemEI3EmcpFzJeuLchzkWKaaLoiJThr4cROig0/edit?usp=sharing -Your notes should include: -Tester: Put your name and github handle. -Environment: e.g Staging1 -Browser: e.g Chrome, PC -Devise: e.g. PC - -Use cases +*Use cases* Give a description of what scenario you tested the code in. For each use case, indicate whether it passed (everything was good), or if it failed (did not meet the spec). 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. -Screenshots- A picture says 1000 words. You can capture what's on your screen with the Prt Scr button on your keyboard. If it's possible to show a bug in action, get a screenshot and illustrate it. \ No newline at end of file +*Screenshots* +A picture says 1000 words. You can capture what's on your screen with the Prt Scr button on your keyboard. If it's possible to show a bug in action, get a screenshot and illustrate it. \ No newline at end of file