skip to main |
skip to sidebar
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.Testing something that is not running - Examine and review itRunning the software and testing itSmallest tested part of application, called units, are individually and independently tested for proper operations. Testing at lowest level.Testing that your software interacts with and share information correctly with other software.Testing changes to computer program to make sure that older program still works with new changes. The process of rerunning your tests.Drivers: Tools used to control and operate the software being tested.Stubs: Receive and Respond to data that the software needs.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.Program units are combined and tested as group in multiple ways. It can be done through Top-Bottom or Bottom-Top approach.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 The test performed by users of a new or changed system in order to approve the system and go live.
The first testing of a product in the lab. Then comes beta testing.
Testing for software bugs by feeding it randomly generated data.
Testing software with some knowledge of its internal code or logic. Contrast with "white box test" and "black box test."
Using invalid input to test a program's error handling.
Monitoring the results of a running system without introducing any special test data. Contrast with "active test" (above).
Testing a system's ability to recover from a hardware or software failure.
Turn it on and see what happens
No comments:
Post a Comment