Documenting errors: Difference between revisions
Jump to navigation
Jump to search
KirstenSmith (talk | contribs) No edit summary |
KirstenSmith (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
It is a good idea to provide all testers with a copy of | It is a good idea to provide all testers with a copy of the test spreadsheet 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. | 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. | ||
<table border="1px"> | <table border="1px" cellspacing="0" cellpadding="3px"> | ||
<tr> | <tr> | ||
<th>Importance<br> (HIGH/MED/LOW)</th> | <th>Importance<br> (HIGH/MED/LOW)</th> | ||
| Line 23: | Line 23: | ||
<th>Fixed<br> (Yes/No)</th> | <th>Fixed<br> (Yes/No)</th> | ||
</tr> | </tr> | ||
<tr> | <tr valign="top"> | ||
<td>Low</td> | <td>Low</td> | ||
<td>example | <td>example intervention</td> | ||
<td>kas</td> | <td>kas</td> | ||
<td>03/02/2018</td> | <td>03/02/2018</td> | ||
<td>10:30 | <td>10:30</td> | ||
<td>Windows 8.1 laptop</td> | <td>Windows 8.1 laptop</td> | ||
<td>Authoring tool version 1.1.2</td> | <td>Authoring tool version 1.1.2</td> | ||
| Line 60: | Line 60: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td></td> | <td> </td> | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| Line 78: | Line 78: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td></td> | <td> </td> | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
Revision as of 15:01, 10 April 2018
It is a good idea to provide all testers with a copy of the test spreadsheet 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.
| 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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Low | example intervention | kas | 03/02/2018 | 10:30 | Windows 8.1 laptop | Authoring tool version 1.1.2 | recontest | 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 |