| Display title | Obvious Beta |
| Default sort key | Obvious Beta |
| Page length (in bytes) | 90,047 |
| Namespace ID | 0 |
| Page ID | 140653 |
| Page content language | en - English |
| Page content model | wikitext |
| Indexing by robots | Allowed |
| Number of redirects to this page | 0 |
| Counted as a content page | Yes |
| Number of subpages of this page | 2 (0 redirects; 2 non-redirects) |
| Page image |  |
| Edit | Allow all users (infinite) |
| Move | Allow all users (infinite) |
| Delete | Allow all users (infinite) |
| Page creator | m>Import Bot |
| Date of page creation | 21:27, 1 November 2013 |
| Latest editor | Agiletek (talk | contribs) |
| Date of latest edit | 06:28, 21 January 2023 |
| Total number of edits | 39 |
| Recent number of edits (within past 180 days) | 0 |
| Recent number of distinct authors | 0 |
| Transcluded templates (5) | Templates used on this page:
|
Description | Content |
Article description: (description)
This attribute controls the content of the description and og:description elements. | Before bringing out a product—in this case, specifically a game or program—it must be tested. The stages of testing are typically called Alpha and Beta, but may include Gamma in some companies. Alpha testing is done by the developers themselves, while Beta testing is done by a specific, outside team called Quality Assurance. In late phases of beta testing (this phase rarely called "Gamma" or "Open Beta"), select members of the public are allowed to test the game. During Alpha and Beta tests, those doing the testing seek out bugs, note them down, and forward them to the parties responsible for fixing them. Those developers then either fix the bug, delay the fix due to whatever time or business constraints, or declare it as "will not be fixed". Ideally, testing will last long enough to fix the most noticeable bugs. |
