UAT in an Agile Development Scenario
The user acceptance test (UAT) is the final stage of testing in application software development. To ensure the software would work well with your business environment and infrastructure we need to test it with user’s perspective, in a form that is proposed to be put in to.
The Testing Strategy and Approach in Agile Development could be very different from a traditional method like Waterfall. But Testing is an important stage, irrespective of which method we are following. In Agile methodology testing happens along the development and that too does by people who don’t have a tag of tester along with their names.
For example in certain Agile development teams Business Analysts could be doing a few rounds of testing each time the software version is released. In a way it is good as Business Analysts understand the Business Requirements of the Software and they can give a ride which is worth. And it is much greater when Agile developers themselves test the software. They tend to understand the system better and can verify the test results in a better way.
Test Coverage in an Agile model is ensured by having Automated Scripts and the right mix/combination of People executing the Test Cases. Each Time Code is changed and Regression Testing is done. Exploratory Testing may also be encouraged. Exploratory Tests are not pre-designed or pre-defined. The Tests are designed and executed immediately. Similarly ad hoc testing may also be encouraged. Ad-hoc testing is done based on the tester’s experience and skills. While automated Test Cases will ensure that the Test Cases scripted are executed as defined, the team may not have enough time to design and script all the test cases.
Testing for Agile Software Development requires innovative thinking and the right mix of people should be chosen for doing the testing. To ensure that delivered product meets the end user’s requirements it is important that sufficient testing is done and all scenarios are tested.