Software testing terminology – part 2 in a series

In recent weeks we started a new series of articles based around software testing terminology. More specifically, we set out to break the jargon down because, put simply, software testing is complex enough. Last week we went from A to C and this week we’ll take you all the way to H. Do let us know if you feel we miss anything important out, we’re aiming for comprehensive yet succinct.

Read through the testing terms featured last week (A-C).

D

Data driven testing: This is a type of testing in which a script is written to store test input and expected results in a table or spreadsheet. A single control script can then execute all tests.

Data flow test: A technique where test cases are designed to execute definition and use pairs of variables.

Decision testing: This technique sees test cases executing decision outcomes.

Defect masking: A term used when one defect prevents another from being detected.

Dynamic testing: A testing type involving the execution of the software of a system or component.

E

Elementary comparison testing: Test cases execute input combinations using the concept of condition determination coverage. This latter term describes the percentage of all single condition outcomes tested which then independently affect a decision outcome.

Emulator: A device, program or system that accepts the same inputs and produces the same outputs as a given system.

F

Fault tolerance: The ability of a software product to maintain a specified level of performance in the case of a fault(s) or infringement of the specified interface.

Functional testing: A testing type based upon an evaluation of the specification of the functionality of a system / component.

G

Glass box testing: This is another name for white box testing… Which we will get to in good time!

H

Heuristic evaluation: This is a static usability test technique. It is used to determine the compliance of a user interface with recognised usability principles.

Horizontal traceability: This term describes the tracing of requirements for a test level through test documentation layers.

So then, we’re almost a third of the way through our A-Z of software testing terminology! One thing for sure is that there are a lot of terms to listen out for the next time you speak with a tester. Maybe that will be one of our own testers – if you are looking for help then we’ll certainly be more than happy to assist.