UAT Testing
In this section you will learn how to:
General Testing Information
Sprint Testing Compared to Release testing
There are two testing cycles:
UAT testing happens in 2 week sprints. This testing is done in the lowest environment. Typically on Tuesday, you will be invited to a Sprint Review meeting, where the developers will talk about what they worked on for the last two weeks. On Wednesday, you will be invited to a sprint planning meeting, in which the developers will talk about what they will be developing for the next two weeks. Then traditionally on Thursday, the UAT environment is refreshed, meaning the new code is brought into the system, old data is blown out of the system, and tests are assigned to testers. On Friday is the official kickoff meeting. This meeting reviews what will be tested and reminds tests of the open offices times and when tests need to be complete.
Total time: 2 week cycles
_____________________________________________________________________________________________________
Release testing happens less often. Traditionally it starts about a month and a half before a new software release is scheduled. There is about a month to complete testing, however we want to complete our tests sooner, so that KL&A can go back into the code and fix the bugs, and have them re-tested before the end of testing. Release testing traditionally has longer tests with more steps. You are also often asked to check for screen size responsiveness.
Sometimes you will be asked to participate in group testing for release testing.
Below you can see an example of the timeline for Release testing.