Friday, October 28, 2016

Alpha Testing | David Tzemach

Alpha Testing

Alpha testing is one of the most important testing strategies that companies use prior to releasing the application to the wider market as a ‘Beta’ version.  It is used to validate that all defects and concerns are removed and that the application is capable to handle the complexity of a massive environment.

Testing Goals
  • Remove any open concern that the engineering has after the testing cycles.
  • To Ensure that from a customer point of view, we have a functional application without any open issues that can affect the software release timelines or quality.
  • Validate that the application is capable to run on the massive environment.
  • Approve that the software can be released as a Beta version.
  • Help the team to gain further confidence in the application.

Test Environment 
The tests are performed in a very complex environment, some companies will install the application in a real production environment (believe it or not…) and some companies will use an environment that simulates a real customer site. 

Performed By
Alpha tests are performed by many types of resources, in most cases by testers, but in some companies the application is installed and access is granted to all resources (Technical support, Product Managers, developers, and End users) that can use the application and report for any defect/issue that they found during the time of use.

Alpha testing in the software development life cycle
Alpha testing is used toward the final stages of the development process, when implemented in the test environment the product must be in a fully-usable state (There are no obvious bugs/critical issues).

Entry Criteria
The entry criteria for alpha testing must include the following considerations:
  • The environment setup is based on the application requirements.
  • The software is tested and ready for implementation.
  • There is no show stopper/Critical bugs.
  • The Build is available and tested.

Exit Criteria 
  • The application is running and functional throughout the testing process.
  • All bugs that found are fixed and implemented.
  • A test summary report is sent and approved.
  • All tests are done and passed.

Why should you run it? 
  • Help to identify defects that the QA teams cannot find on virtual environments.
  • Performed on a complex environment that simulates the customer site.
  • Will help to determine that the application meets the design criteria.
  • Increases the reliability, stability, and confidence in the application.

No comments:

Post a Comment

My Presentations