Acceptance testing: Acceptance testing formal testing conducted to determine whether or not
a system satisfies its acceptance criteria (the criteria the system must satisfy to be accepted
by a customer) and to enable the customer to determine whether or to accept the system
Black box testing: Black box testing (also called functional testing or behavioral testing)
testing that ignores the internal mechanism of a system or component and focuses solely on the
outputs generated in response to selected inputs and execution conditions
Boundary value: Boundary value data value that corresponds to a minimum or maximum input,
internal, or output value specified for a system or component
Defensive Testing: Testing which includes tests under both normal and abnormal conditions
Error: The difference between a computed, observed, or measured value or
condition and the true, specified, or theoretically correct value or condition
Failure: Failure the inability of a system or component to perform its required
function within the specified performance requirement
Failure path: A test case that intentionally forces an error condition to occur
Fault: Fault an incorrect step, process, or data definition in a program
Integration testing: Integration testing in which software components, hardware components,
or both are combined and tested to evaluate the interaction between them.
Input/output oracle an oracle that specifies the expected output for a
specified input
Mistake human action that produces an incorrect result of any program, process, or body of
data that specified the expected outcome of a set of tests as applied to a tested object.
Performance testing: Testing conducted to evaluate the compliance of a system or component
with specified performance requirements.
Regression testing: Selective retesting of a system or component to verify that modifications
have not caused unintended effects and that the system or component still complies with its
specified requirements.
Robustness Testing: Testing whereby test cases are chosen outside the domain to test
robustness to unexpected, erroneous input
Scaffolding: Code computer programs and data files built to support software development
and testing but not intended to be included in the final product
Smoke Tests: Group of test cases that establish that the system is
stable and all major functionality is present and works
under “normal” conditions
Stress Testing: Testing conducted to evaluate a system or component at or beyond the limits
of its specification or requirement.
Stubs computer program statement substituting for the body of a software module that is or
will be defined elsewhere.
Success path a test case that execute some desirable functionality (something the customer
wants to work) without any error conditions.
System Testing: testing conducted on a complete, integrated system to evaluate the system
compliance with its specified requirements.
Test case: Set of test inputs, execution conditions, and expected results developed for
a particular objective, such as to exercise a particular program path or to verify
compliance with a specific requirement
Test driver: Software module used to involve a module under test and often, provide
test inputs, controls, and monitor execution and report test results
Test plan document describing the scope, approach, resources, and schedule of intended
test activities. It identifies test items, the features to be tested, the testing tasks,
who will do each task, and any risks requiring contingency plans
Unit Testing: Testing of individual hardware or software units or
groups of related units
Usability Testing: Testing conducted to evaluate the extent to which a
user can learn to operate, prepare inputs for, and
interpret outputs of a system or component
Validation Testing: The process of evaluating a system or component during or at the
end of the development process to determine whether it satisfies specified requirements
Verification: The process of evaluating a system or component to determine whether the
products of a given development phase satisfy the conditions imposed at the start of that phase.
White box Testing: Testing that takes into account the internal mechanism of a system
or component.
Related articles
- Difference between System Testing and System Integration Testing (tfortesting.wordpress.com)
- Black and White Testing – What is it? (softwaretestinggrasshopper.wordpress.com)
my testing world 