Your QA department has published the following set of user guidelines for the next user acceptance test (UAT) session.
Do you see any problems with any of them (in other words, which of these guidelines should NOT be published)?
- There will be a training class before you begin to use the software during this testing session. We’ll also give you instructions on what to do should the tests fail for any reason.
- Come prepared to ensure the software works as designed. We’ll fill you in on what functions should work and which should not for the purposes of this test.
- Come prepared to find as many bugs as possible. We need this final QA check to ensure we’re really ready for production.
- Come prepared to focus. You will be doing the testing and approving!
You Answered: C
Correct Answer: C
Correct! Any good UAT session will have a training session at the beginning to bring users up-to-speed on how the software should work in its current condition. This ensures that as they enter the data into the system they will be focusing on how the system works and not so much that it may not be fully operational. If tests do fail then there should be a set of agreed-upon actions to take regarding stopping/suspending or resuming the UAT.
The purpose of every user acceptance test is to show compliance to business objectives, not to find bugs. If bugs are found, there needs to be an agreed-upon set of actions to either suspend and/or to resume UAT if the defect can be resolved quickly. Any known defects should be discussed openly before UAT begins.
