The value of documentation prepared in structured/waterfall or agile projects is often of dubious value. In structured projects, the planning documentation is prepared in a knowledge vacuum – where the requirements are not stable, and the system under test is not available. In agile projects – where time is short and other priorities exist – not much may get written down anyway. Paul believes the only test documentation that could be captured reliably and be trusted must be captured contemporaneously with exploration and test. The only way to do this would be using a pair tester or a bot…....