Quality Assurance and Testing Jargon clarified in simple English with examples, by experts with years of experience in testing
Showing posts with label B. Show all posts
Showing posts with label B. Show all posts
business process-based testing
An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes.
buffer overflow
A memory access failure due to the empt by a process to store d beyond the boundaries of a fixed length buffer, resulting in overwriting of adjacent memory areas or the raising of an overflow exception. See also buffer.
buffer
A device or storage area used to store d temporarily for differences in rates of d flow, time or occurrence of events, or amounts of d that can be handled by the devices or processes involved in the transfer or use of the d . [IEEE 610]
branch testing
A white box test design technique in which test cases are designed to execute branches.
branch coverage
The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.
branch
A basic block that can be selected for execution based on a program construct in which one of two or more alternative program paths is available, e.g. case, jump, go to, if- then-else.
boundary value
An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge, for example the minimum or maximum value of a range. boundary value analysis A black box test design technique in which test cases are designed based on boundary values. See also boundary value.
bottom-up testing
ISTQB Glossary definition
An incremental approach to integration testing where the lowest level components are tested first, and then used to facilitate the testing of higher level components. This process is repeated until the component at the top of the hierarchy is tested. See also integration testing.
In simple English:
Test one small piece at a time starting with the lowest level.
Field notes:
Most often this is the approach taken when both the development and testing are done by the same company.
This approach in principle is the basis of several other famous approach like test driven development, agile and that family of processes.
In some cases this approach might not be very appropriate.
For example:
when the property being tested it's an implementation of a established stable product like people soft, this approach makes no sense as all the components are already tested and proven.
blocked test case
A test case that cannot be executed because the preconditions for its execution are not fulfilled.
black box testing
Testing, either functional or non-functional, without reference to the internal structure of the component or system.
Subscribe to:
Posts (Atom)