You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Human testers need certain information in order to run tests successfully and generate usable result data. This includes, but is not limited to:
resetting screen reader settings to their defaults;
providing screen reader output;
executing setup scripts (including when to refresh the test case page);
determining what does and does not constitute unexpected output; and
only executing the commands as described by each test, and
not attempting to trigger screen reader behaviour that will change the result of a test, in any way other than that proscribed by the test.
To ensure that testers are provided with this information and can acknowledge that they've read it, it is proposed that:
The app should display a documentation page, with a button to continue at the bottom, to all new testers as soon as they try to execute a test plan for the first time.
If a tester does not use the provided button to acknowledge that they have read and understood the information, it should be presented again the next time they try to access a test plan as a tester (even if they are an admin opting to test as someone other than their signed in account).
When the underlying documentation is updated, the page should be re-presented automatically to all testers the next time they attempt to execute a test, regardless of whether they have executed tests before or not. All testers will have to re-acknowledge their comprehension of the information.
To assist previous testers in understanding changes to the documentation, a change log section should be included which describes those changes. This can be brief, e.g. by describing the change at a high level, and then linking to the updated section so users can read it in more detail.
The documentation should be easily accessible to all testers wishing to manually consult it, not only presented automatically. For instance, it could be linked to from the App's main nav, and/or the instructions presented for each individual test.
The text was updated successfully, but these errors were encountered:
Human testers need certain information in order to run tests successfully and generate usable result data. This includes, but is not limited to:
To ensure that testers are provided with this information and can acknowledge that they've read it, it is proposed that:
The text was updated successfully, but these errors were encountered: