Documenting errors: Difference between revisions

From Lifeguide Wiki
Jump to navigation Jump to search
(Created page with "It is a good idea to provide all testers with a copy of this test spreadsheet for them to report all errors that they find. This way the person who made the website can more e...")
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
It is a good idea to provide all testers with a copy of this test spreadsheet for them to report all errors that they find. This way the person who made the website can more easily identify where the problem might be, and can use user data to take a closer look at what might have gone wrong.
It is a good idea to provide all testers with a copy of the test table below for them to report all errors that they find. This way the person who made the website can more easily identify where the problem might be, and can use user data to take a closer look at what might have gone wrong.


It is helpful for testers to use a shared file, such as using Google Docs, so that the fixer has a list of all the errors in one place.
The first row of the table provides an example of the details that testers should provide.
 
It is helpful for testers to use a shared spreadsheet, such as using Google Docs, so that the fixer has a list of all the errors in one place.
 
It is worth taking the time to format the spreadsheet so that high/medium/low priority errors can be coloured red, amber and green, and errors that have been fixed can be scored through.
 
<table border="1px" cellspacing="0" cellpadding="3px">
  <tr>
    <th>Importance<br>  (HIGH/MED/LOW)</th>
    <th>Intervention<br>  tested</th>
    <th>Tested<br>  by (initials)</th>
    <th>Date Tested</th>
    <th>Time<br>  Tested (approx if not sure)</th>
    <th>Tested<br>  on laptop/PC/Ipad?</th>
    <th>Version<br>  of intervention tested (URL) OR Authoring tool version (if preview mode):</th>
    <th>Intervention<br>  shortname (if downloaded)</th>
    <th>Browser<br>  used to test (please don't forget to put the version number/details here too)</th>
    <th>Username</th>
    <th>Email<br>  address used</th>
    <th>Time<br>  of error</th>
    <th>Page<br>  name where error found (name on tab, not in address bar)</th>
    <th>Error<br>  details</th>
    <th>Other<br>  information</th>
    <th>Fixed<br>  (Yes/No)</th>
  </tr>
  <tr valign="top">
    <td>MED</td>
    <td>example intervention</td>
    <td>kas</td>
    <td>03/02/2018</td>
    <td>10:30</td>
    <td>Windows 8.1 laptop</td>
    <td>Authoring tool version 1.1.2</td>
    <td>recontest</td>
    <td>Chrome Version<br>  65.0.3325.181 (Official Build) (64-bit)</td>
    <td>kas</td>
    <td>kas@test.com</td>
    <td>10:41</td>
    <td>s_intro_p7</td>
    <td>back button didn't work</td>
    <td>clicked forwards twice then clicked back twice, clicking the back button<br>  didn't do anything.</td>
    <td>No</td>
  </tr>
  <tr>
    <td>&nbsp;</td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
  </tr>
  <tr>
    <td>&nbsp;</td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
  </tr>
  <tr>
    <td>&nbsp;</td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
    <td></td>
  </tr>
</table>

Latest revision as of 11:37, 1 March 2019

It is a good idea to provide all testers with a copy of the test table below for them to report all errors that they find. This way the person who made the website can more easily identify where the problem might be, and can use user data to take a closer look at what might have gone wrong.

The first row of the table provides an example of the details that testers should provide.

It is helpful for testers to use a shared spreadsheet, such as using Google Docs, so that the fixer has a list of all the errors in one place.

It is worth taking the time to format the spreadsheet so that high/medium/low priority errors can be coloured red, amber and green, and errors that have been fixed can be scored through.

Importance
(HIGH/MED/LOW)		 Intervention
tested		 Tested
by (initials)		 Date Tested Time
Tested (approx if not sure)		 Tested
on laptop/PC/Ipad?		 Version
of intervention tested (URL) OR Authoring tool version (if preview mode):		 Intervention
shortname (if downloaded)		 Browser
used to test (please don't forget to put the version number/details here too)		 Username Email
address used		 Time
of error		 Page
name where error found (name on tab, not in address bar)		 Error
details		 Other
information		 Fixed
(Yes/No)
MED example intervention kas 03/02/2018 10:30 Windows 8.1 laptop Authoring tool version 1.1.2 recontest Chrome Version
65.0.3325.181 (Official Build) (64-bit)		 kas kas@test.com 10:41 s_intro_p7 back button didn't work clicked forwards twice then clicked back twice, clicking the back button
didn't do anything.		 No
 
 
 
Retrieved from "https://wiki.lifeguideonline.org/w/index.php?title=Documenting_errors&oldid=22325"