Archive for the ‘Geek Terminology’ Category

What is Testing Evidence?

The results of all tests must contain sufficient evidences (snapshots, files, printouts etc) indicating the successful or failed testing scenarios.

The evidence required must be stated in the Test Script, and all evidence documents (printouts, files etc) must be cross referenced to the step at which they were produced.

Evidence needs to be auditable, that means it could be examined and verified by an independent person (e.g. FDA Inspector) after the event. It can be in the form of formally approved documents or signed records.

What is Sanity/Smoke Testing?

Sanity/Smoke testing is performed after the unit testing and the test environment set-up for system testing. Sanity/Smoke testing should be performed to ascertain if the test environment is in a good state to begin system testing.

Based on the size, complexity and risk involved, Test Leads should chose an appropriate means of performing this task. One way is to select some Unit test scripts which, if passed indicates that the test environment is in a good state for System Testing.

What is Challenge Testing?

Challenge Testing ensures that incorrect data or data entry is correctly managed, with correct error handling. This should also include breaches of security.

What is Boundary Testing?

Boundary Testing ensures that the system performs correctly at the boundary conditions specified in the requirements.

Example – If the specification calls for different processing, depending upon whether an order quantity is above or below 100, separate cases should be listed for quantities of 99, 100 and 101.

What is Load Testing?

Load testing ensures that the system performance is satisfactory with maximum expected volumes of data, transactions and simultaneous users.