Beta Testing





Prior to any major software release it is standard practice to conduct a comprehensive cycle of Beta Testing to validate that the application or system is ready for general availability to the target user population, and to identify any failure or defects that may hinder release. QA Valley is contracted by numerous development companies and software publishers to Beta Test pre-release software. These engagements are QA Cycles that are farmed out to QA Valley for a multitude of reasons including the desire by publishers to have the Beta QA performed by an external independent party that has no affiliation to the original developers.

QA Valley implements an environment that emulates that of the user community including hardware, software, interfaces, databases, operating systems, and the correct version of these. Test cases that demonstrate the total functionality of the software are cycled through in an orchestrated sequence reflective of typical use by routine users. These test cases encompass the combinations and permutations of transaction workflows that users can possibly traverse during daily usage of the software. QA Valley’s ultimate intent is to achieve comprehensive usage by touching every legitimate aspect of the software execution.

Beta Testing results in the creation of an extensive Defect Repository, commonly called the Beta Test Defect Sheet assimilated with tools such as Bugzilla and Mantis, or more appropriately bug tracking tools that are used by the respective clients. These defects are classified based on Severity Schemes that comply with the standards embraced by our clients, and represent recommended orders for remediation and reintegration into the codebase. Defects that do not hinder the accurate completion of workflows and transactions may be attributed lower priority, and are left to discretion whether these should be address immediately.

After our clients have rectified the bugs reported in the Beta Test Defect Sheet, QA Valley is reengaged to run a final cycle against the remediated software to validate and mark as complete defects that have been rectified. This is a final sanity check independently performed to render a stamp of approval that the software is ready for prime time. In cases where there are differences in opinion between our testers and the respective development parties, QA Valley will demonstrate the actual transactions that are in dispute and may venture to assist developers by providing artifacts such as data dumps and port traffic logs.