Test factoring can use structural properties inferred from static analysis on the code base and
tests, and dynamic information obtained by running an instrumented version of the original test.
The Introduce Mock procedure can be outlined as follows:
1. Transformation: The code undergoes an semantics-preserving transformation to facilitate
dynamic instrumentation.
2. Trace capture: The original test is executed(we assume it passes), and traces are collected
of calls from the tested realm into the mocked realm and vice versa.
3. Mock code generation: The traces are analyzed and code generated for the mock objects, which
will simulate the mocked realm in the final factored test.
'Papers > Others' 카테고리의 다른 글
| 추상 클래스 (0) | 2006.12.02 |
|---|---|
| event handler (0) | 2006.11.22 |
| doxygen (0) | 2006.11.21 |
| documentation (0) | 2006.11.19 |
| namespace (0) | 2006.11.18 |