Testing a product the desktop way
During production we release at least three versions of a product for testing and feedback:
Alpha release
This is a partial implementation of the product that is used 'internally' to test critical functionality against agreed criteria.
Usually, we deliver our alpha to you to demonstrate the feasibility and basic structure of the software. This includes a creative treatment (typography / colours; image, video / audio styles etc), so that you can experience - probably for the first time - the 'look 'n feel' of your product and judge its suitability for your audience.
Beta release
A beta release is supposed to be the first version of the product that implements all the features in the technical specification.
In practice, we often issue a series of betas (beta 1, 2, 3 etc.) as the technical specification is honed. Progressively, these include new and improved features and more and more highly developed content. They are used to test technical aspects of the product with end users and to elicit feedback on content presentation, browser compatibility and accessibility.
Gamma release
Often called a release candidate, a gamma is like a "sneak preview" of the final product with the added advantage that it may reveal a serious last minute problem.
Our legacy and 'up-to-date' server / client machines expose release candidates to a rigorous series of technical tests - a process we encourage you to mirror as part of your quality checks.
In this challenge, we have assigned true statements to the software releases we issue. Your task is to decide the reason why a statement applys to a particular release.