Develop
Acceptance Testing
Acceptance Testing
Acceptance testing is conducted on the complete solution with the objective to verify alignment of product/solution to the Scope and User's need, by the Customers or Users themselves. This forms the basis of approval for release of the product/solution to the market.
Development Testing ensures that the Product/solution is built based on the agreed scope and that all its features and functionalities are working properly without any bugs or errors. Subsequently, the solution is offered to the user or user's representative for testing, so that the solution can be verified to meet user's requirement. Based on the alignment, the decision for the Product release are taken.
Alpha testing
Alpha testing is a form of internal user acceptance. For software product, it is performed in development environment, to identify bugs and errors before offering the product to the external User for Acceptance testing.
The goal of Alpha Testing is to uncover any bugs by having internal team members use the feature as if they are external users. We simulate the experience a user would have with the new product so that the development team can go back and address any issues or defects before it is offered to the external User or User representative for acceptance testing.
User Acceptance Testing (UAT)
User Acceptance Testing (UAT) is a type of testing performed by the user/user's representatives to verify if the features of the product is in line with the requirements and accordingly accept the product for releasing it to the market.
After Alpha Testing, the solution is offered to the User or User's representative for verifying that the product/solution meets the user requirement, as specified in the agreed scope. Based on the testing feedback, the solution is further enhanced to arrive at the Final Solution. With all the previous efforts put during Empathize, Define, Ideate, and Development phases, it is expected that the solution offered for UAT is more or less in line with the User's requirement and the feedback received during UAT are of minor feature enhancements that doesn't need significant development effort. If the feedback received at UAT consists of new features requirement, or the enhancements that need high development effort, Product backlog is revisited for prioritization of features in next sprint. The product development team goes for changes in the product only if the severity of the issue or risk is very high.
User Testing or Pilot testing
User Testing (UT) is testing performed by set of End Users to verify if the product is working as intended, just before releasing the product in the user environment.
Pilot testing is the type of testing where a group of users uses the product/solution in totality before the final deployment of the software, in a replica of the real environment. The purpose of this final testing before the release of the product in real-environment, is to check for any bugs and errors, and verify if all thee features of the product is working as intended. There is no scope for feature enhancement or new feature request during this testing.