bottom-up testing | ||||
subject | fact |
bottom-up testing | has definition A incremental testing strategy in which you start by testing the very lowest levels of the software using drivers, and then work upwards, as you integrate successive layers | |
has disadvantage the cost of writing the drivers | ||
has procedure start by testing the very lowest levels of the software using a driver | ||
is a subtopic of 10.9 - Strategies for Testing Large Systems | ||
is a kind of vertical incremental testing | ||
integration testing | has advantage when you find a problem, you can find the defect more easily because you have a better idea in which subsystem to look | |
is better than big bang testing for large systems | ||
testing | can find defects whose consequences are obvious but which are buried in complex code, and thus will be hard to detect when inspecting | |
involves thinking of what could go wrong without actually studying the software | ||
requires attention to detail | ||
process | see also process^2 |