Hello and Namaste…………Welcome to yet another post for software testing. In this post, we are going to know about how a typical test cycle functions.
After software requirements are understood and analysed well, developers write code. When development is completed, software developed is released to QA team for testing. A software is released as “build”. Build refers to process in which programs are compiled together to make tangible software component or product so that it can be tested for functional and non functional requirements.
A typical functional test cycle consists of smoke testing,testing change requests, regression testing, ad hoc testing, and retesting if applicable.
Smoke testing : Whenever software build with new features or enhancements or bug fixes is released, build is validated for critical functionality of application . If smoke scenarios aka critical functionality of application is working, then smoke test status is said to be pass and build is accepted for further QA examination. Otherwise if build fails smoke test is fail and build is rejected
Regression testting : In regression testing , software components influenced by new changes or features are tested in detail. Impact area is determined by scope of changes done. If changes done are limited to few components, then only relevant modules are tested otherwise whole system is tested to verify wheather changes done have affected any other functionality
Ad hoc testing : Ad hoc testing validates system in general. End to end scenarios are tetsed across application without focusing on any particular feature or module. Ad hoc testing is preferred if test cycle has limited time and impact of new changes is less
Retesting : Retesting of fixed issues is carried out for any of bug fixed and given for QA verification