Test Data Management

Quality and reliability of software applications has been very vital due to increase in applications complexity and scalability. However, it is challenging for Testers to deliver reliability. Test team not only have to follow proper test process and methodologies, but also ensure accuracy of test data. Testers also need to ensure that test data correctly reflects production environment, both functionally and technically.

A well documented Test Data Management (TDM) can help to increase efficiencies and provide greater values. These test datas can be made available with in organization in secure, organized, consistent and controlled manner.

By documenting right test data and test data management strategy, QA teams can get one step closer to reliable testing.

Release Life Cycle

The term release candidate refers to a version with potential to be a final product, ready to release unless fatal bugs emerge. In this stage, the product features all designed functionalities and no known showstopper-class bugs. At this phase the product is usually code complete.

Microsoft Corporation often uses the term release candidate. During the 1990s, Apple Inc. used the term "golden master" for its release candidates, and the final golden master was the general availability release. Other terms include gamma (and occasionally also delta, and perhaps even more Greek letters) for versions that are substantially complete, but still under test, and omega for final testing of versions that are believed to be bug-free, and may go into production at any time. (Gamma, delta, and omega are, respectively, the third, fourth, and last letters of the Greek alphabet.) Some users disparagingly refer to release candidates and even final "point oh" releases as "gamma test" software, suggesting that the developer has chosen to use its customers to test software that is not truly ready for general release. Often, beta testers, if privately selected, will be billed for using the release candidate as though it were a finished product.

A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There may still be source code changes to fix defects. There may still be changes to documentation and data files, and to the code for test cases or utilities. New code may be added in a future release.

Origin of Alpha and Beta Test

The term beta test applied to software comes from an early IBM hardware product test convention dating back to punched card tabulating and sorting machines. Hardware first went through an alpha test for preliminary functionality and small scale manufacturing feasibility. Then came a beta test to verify that it actually correctly performed the functions it was supposed to and could be manufactured at scales necessary for the market, and then a c test to verify safety.

With the advent of programmable computers and the first shareable software programs, IBM used the same terminology for testing software. Beta tests were conducted by people or groups other than the developers. As other companies began developing software for their own use, and for distribution to others, the terminology stuck and now is part of our common vocabulary.

Testing definition

Testing is a process used to help identify the correctness, completeness and quality of developed computer software.

Performance Management

Performance Test Management is both practical and robust which can assist in defining and planning of overall test strategy, infrastructure and framework.