Alpha Testing

Alpha testing allows the system to be tested in a way that is likely to be similar to real usage. It involves potential users using the system on the developer's site. This can lead to the discovery of failures which did not become apparent in testing, possibly because a certain type of usage was not initially anticipated.

Beta Testing

Beta testing involves the system being tested on the customer's site. Testing in this way can be very effective in that it enables the customer to use the system in the context of the business and discover any problems with how it functions. Beta testing can also be used as a chance to initiate some staff training in the system.

Regression Testing

Regression testing involves re-testing the system with all previous tests after introducing a new change to the system (either within the code or in the system's environment). This is a particularly useful type of testing as fixing a fault in one part of the system has the potential to introduce a fault in another part of the system. This process of regression testing would be an unreasonably time-consuming task if not automated for large systems. Different testing tools have been developed which allow the "recording" of tests in order for them to be executed instantly at any later time.

Stress Testing

Some systems have variable loads depending on how many users or customers can access it simultaneously. It is vital to know what level of "stress" the system can handle otherwise unexpected failures or performance degradation can occur after final implementation and installation has occurred. Stress testing involves running the system under an extremely heavy load and assessing how it performs.

Search for "Alpha, Beta, Regression and Stress Testing" on: Google | Kelkoo | Amazon | eBay (UK) | eBay (US)

Search for "Alpha, Beta, Regression and Stress Testing" on the rest of Computing Students: Alpha, Beta, Regression and Stress Testing