Articles 
Automation Development Stages Checklist
Automation Development Stages Checklist
Thursday, 07 April 2011 08:04
- Pre-alpha
refers to all activities performed during the software project prior to testing. These activities can include requirements analysis, software design, software development and unit testing. In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the functionality is complete. - Alpha
the first phase to begin software testing (alpha is the first letter of the ancient Greek alphabet, used as the number 1). In this phase, developers generally test the software using white box techniques. Additional validation is then performed using black box or gray box techniques, by another testing team. Moving to black box testing inside the organization is known as alpha release. - Beta
generally begins when the software is feature complete. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it. - Release Candidate (RC)
all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug - General Availability
is the point where all necessary commercialization activities have been completed and the software has been made available to the general market either via the web or physical media
| < Prev | Next > |
|---|
