SOFTWARE
TESTING
By MARTIN MBUGUA
, What is software testing?
• This is the process of checking the completeness ,correctness
and quality of developed software.
• It includes a set of activities that are set on finding errors in a
software before it is released to the user.
Software testing basically involves:
•Executing software with inputs representative of actual
operation conditions (or operational profiles)
•Comparing produced/expected outputs
•Comparing resulting/expected states
•Measuring execution characteristics (e.g., memory used, time
consumed, etc.)
, Terminology
1)Fault: an imperfection that may lead to a failure •E.g.,
missing/incorrect code that may result in a failure
•Bug: another name for a fault in code
2)Error : where the system state is incorrect but may not have been
observed
3)Failure: some failure to deliver the expected service that is observable
to the user
4)Test Case: set of inputs, execution conditions, and expected results
developed for a particular objective
5)Test Suite: collection of test cases, typically related by a testing goal or
an implementation dependency
6)Test Driver: class or utility program that applies test cases
7)Test harness: system of test drivers and other tools that support test
execution
8)Test Strategy: algorithm or heuristic to create test cases from a
representation, implementation, or a test model
9)Oracle: means to check the output from a program is correct for the
given input
10)Stub: partial temporary implementation of a component (usually
required for a component to operate)
TESTING
By MARTIN MBUGUA
, What is software testing?
• This is the process of checking the completeness ,correctness
and quality of developed software.
• It includes a set of activities that are set on finding errors in a
software before it is released to the user.
Software testing basically involves:
•Executing software with inputs representative of actual
operation conditions (or operational profiles)
•Comparing produced/expected outputs
•Comparing resulting/expected states
•Measuring execution characteristics (e.g., memory used, time
consumed, etc.)
, Terminology
1)Fault: an imperfection that may lead to a failure •E.g.,
missing/incorrect code that may result in a failure
•Bug: another name for a fault in code
2)Error : where the system state is incorrect but may not have been
observed
3)Failure: some failure to deliver the expected service that is observable
to the user
4)Test Case: set of inputs, execution conditions, and expected results
developed for a particular objective
5)Test Suite: collection of test cases, typically related by a testing goal or
an implementation dependency
6)Test Driver: class or utility program that applies test cases
7)Test harness: system of test drivers and other tools that support test
execution
8)Test Strategy: algorithm or heuristic to create test cases from a
representation, implementation, or a test model
9)Oracle: means to check the output from a program is correct for the
given input
10)Stub: partial temporary implementation of a component (usually
required for a component to operate)
