Test Blueprints - Exposing Side Effects in Execution Traces to Support Writing Unit Tests

Writing unit tests for legacy systems is a key maintenance task. When writing tests for object-oriented programs, objects need to be set up and the expected effects of executing the unit under test need to be verified. If developers lack internal knowledge of a system, the task of writing tests is non-trivial. To address this problem, we propose an approach that exposes side effects detected in example runs of the system and uses these side effects to guide the developer when writing tests. We introduce a visualization called Test Blueprint, through which we identify what the required fixture is and what assertions are needed to verify the correct behavior of a unit under test. The dynamic analysis technique that underlies our approach is based on both tracing method executions and on tracking the flow of objects at runtime. To demonstrate the usefulness of our approach we present results from two case studies.

Myth creation in textbook writing : the case of randomised controlled trials in medical research

Textbooks, across all disciplines, are prone to contain errors; grammatical, editorial, factual, or judgemental. The following is an account of one of the possible effects of such errors; how an error becomes entrenched and even exaggerated as later textbooks fail to correct the original error. The example considered here concerns the origins of one of the most basic and important tools of to­ day's medical research, the randomised controlled trial. It is the result of a systematic study of 26 British, French and German history of medicine textbooks since 1996.