Documenting errors - Revision history

KirstenSmith at 11:37, 1 March 2019

2019-03-01T11:37:47Z

← Older revision		Revision as of 11:37, 1 March 2019
Line 35:		Line 35:
	<td>Authoring tool version 1.1.2</td>		<td>Authoring tool version 1.1.2</td>
	<td>recontest</td>		<td>recontest</td>
	<td>Version<br> 65.0.3325.181 (Official Build) (64-bit)</td>		<td>Chrome Version<br> 65.0.3325.181 (Official Build) (64-bit)</td>
	<td>kas</td>		<td>kas</td>
	<td>kas@test.com</td>		<td>kas@test.com</td>

KirstenSmith at 15:07, 10 April 2018

2018-04-10T15:07:01Z

← Older revision		Revision as of 15:07, 10 April 2018
Line 1:		Line 1:
	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 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">		<table border="1px" cellspacing="0" cellpadding="3px">
Line 24:		Line 27:
	</tr>		</tr>
	<tr valign="top">		<tr valign="top">
	<td>~~Low~~</td>		<td>MED</td>
	<td>example intervention</td>		<td>example intervention</td>
	<td>kas</td>		<td>kas</td>

KirstenSmith at 15:01, 10 April 2018

2018-04-10T15:01:20Z

← Older revision		Revision as of 15:01, 10 April 2018
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 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 ~~row~~</td>		<td>example intervention</td>
	<td>kas</td>		<td>kas</td>
	<td>03/02/2018</td>		<td>03/02/2018</td>
	<td>10:30 AM</td>		<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>

KirstenSmith at 14:56, 10 April 2018

2018-04-10T14:56:57Z

@@ Line 5: / Line 5: @@
 <table border="1px">
-<tr>
+  <tr>
-<td>sss</td>
+    <th>Importance<br>  (HIGH/MED/LOW)</th>
-<td>sss</td>
+    <th>Intervention<br>  tested</th>
-<td>sss</td>
+    <th>Tested<br>  by (initials)</th>
-</tr>
+    <th>Date Tested</th>
 </table>

KirstenSmith at 14:53, 10 April 2018

2018-04-10T14:53:45Z

← Older revision		Revision as of 14:53, 10 April 2018
Line 2:		Line 2:

	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">
			<tr>
			<td>sss</td>
			<td>sss</td>
			<td>sss</td>
			</tr>
			</table>
			</div>

KirstenSmith: 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..."

2018-04-10T14:49:25Z

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..."

New page

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 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.