August 16, 2008

Different Types of Testing




  • Black Box Testing
Tester only knows that what the software is supposed to do NOT how software operates.

  • White Box Testing (Clear Box Testing)
Tester has access to programming code and can examine it for cases to help him with his/her testing.

  • Statis Testing
Testing something that is not running - Examine and review it

  • Dynamic Testing
Running the software and testing it

  • Unit Testing
Smallest tested part of application, called units, are individually and independently tested for proper operations. Testing at lowest level.

  • Capability Testing
Testing that your software interacts with and share information correctly with other software.

  • Regression Testing
Testing changes to computer program to make sure that older program still works with new changes. The process of rerunning your tests.

  • Automated Testing
Drivers: Tools used to control and operate the software being tested.
Stubs: Receive and Respond to data that the software needs.

  • Beta Testing
External testing process in which the software is sent out to a select group of potential customers, who uses it in real world environment towards the end of production development cycle.

  • Integration Testing
Program units are combined and tested as group in multiple ways. It can be done through Top-Bottom or Bottom-Top approach.

  • System Testing
Testing to confirm that all module work as specified, and system as a whole perform adequately on the platform on which it will be deployed

  • Acceptance Test
The test performed by users of a new or changed system in order to approve the system and go live.

  • Alpha Test
The first testing of a product in the lab. Then comes beta testing.

  • Fuzz Test
Testing for software bugs by feeding it randomly generated data.

  • Gray Box Test
Testing software with some knowledge of its internal code or logic. Contrast with "white box test" and "black box test."

  • Negative Test
Using invalid input to test a program's error handling.

  • Passive Test
Monitoring the results of a running system without introducing any special test data. Contrast with "active test" (above).

  • Recovery Test
Testing a system's ability to recover from a hardware or software failure.

  • Smoke Test
Turn it on and see what happens

No comments: