Domain User Valuable Test Report - iks-gmbh-tools/SysNat GitHub Wiki
Test reports generated from most testing tools either lack low level information about the test execution (i.e. which UI component was clicked and which value was entered in which field) or they contain many technical information which overload the report from the domain point of view.
Important for domain users is to understand retrospectively what exactly happened during test execution. This is true both for successful and failed executions. In the later cases it is important to understand where exactly a problem occurred during execution and to gain information about the problem (ideally the plain reason). Many problems (but of course not all) can be foreseen and the task for developers is to provide available information in the test report in a way that the problem becomes understandable for domain users without technical skills.
The SysNat test report tries to reach this goal. It allows a transparant overview of all non-technical details during execution. In case of a failure, SysNat differentiates between technical failures and failed assertions. The later represent an unexpectated outcome of a system behaviour, the former tell that the execution was terminated due to other reasons. Typical for those other reason is, that the graphical user interface was modified (e.g. an optional field has become mandatory or a completely new UI element has been introduced). Those problems lead to technical execptions and SysNat tries to translate these kind of problems into a non-technical error message so that a domain user is able to understand the problem. In such cases (when a technical problem reflects a non-match between actual system behaviour and corresponding Executable Example) domain users may solve the problem without help from developers by adapting the test data or the Natural Language Scripts. Prerequiste is that natural language scripts are used for the low level description of the system behaviour. If the low level behaviour is described only in program code (and not in natural language scripts) then developer help is needed anyway.
To conclude, a valuable test report of a XXDD-Tool avoids any technical information but simultanously provides all execution details which are relevant from the business point of view. SysNat test reports should do this job for you.