Embedded Files
As a part of the 2-week Sprint, User Acceptance Testing (UAT) is a key time to
- cultivate end-user leaders and power users
- get feedback from end-users
- pave the way for end-user adoption.
Testing Testing 1, 2, 3
Testing Testing 1, 2, 3
- DETERMINE configuration/code “freeze” date
- nothing new (particularly features) should be added in preparation for end-user testing
- IDENTIFY UAT testers and schedule their time for full engagement
- TRAIN testers on new application and process areas
- MIGRATE or CREATE realistic test data
- TRACK issues (bugs/feature requests) identified during testing
- PRIORITIZE issues, estimate and fix highest priority
- FIX, iterate and close issue(s)
UAT Testers Are Also System Advocates
Power users are great testing candidates but are also often the busiest. Keep in mind that every interaction with the new system is “change management” and each UAT testers can be an advocates and trainers for the new system once released.
Thus having a successful UAT is a great first step to adoption
Bugs are a part of the software development process. Expect to find them and fix them. We budget time in the estimate for a normal amount of bugs found and fixed.
However, not every bug necessarily has to be fixed. During the sprint, fix the showstoppers and determine if the others can be resolved through end-user training. Strong Client Leadership is important to making decisions on what gets addressed given any budget constraint.
Expect Bugs, But Fix Judiciously
There Are Multiple Paths to Bugs
Testers should not only test “positive” paths but also “negative paths” to find bugs. But designing and testing for every possible (and unlikely) scenario can get very expensive. Finding the right level of test coverage is important.
Testing needs to represent real-life and so the more the data and scenarios match real-world situations the better the testing. A full sandbox ensures testing on the best data (your full, real data) but loading a good sample of test data can be effective enough for your particular budget
Use Real Data; Not Fake Data
Report abuse