top-down testing | ||||
subject | fact |
top-down testing | has definition An incremental testing strategy in which you start by testing only the user interface, with the underlying functionality simulated by stubs, then you work downwards, integrating lower and lower layers | |
finds defects in the layer that was most recently integrated | ||
has disadvantage the cost of writing the stubs | ||
has procedure
| ||
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 | involves thinking of what could go wrong without actually studying the software | |
requires attention to detail | ||
process | see also process^2 |