Discrepancy Reports should be completed whenever an unexpected result is obtained during the execution of the ATK. A discrepancy may be a difference in the actual result from the expected result, a system malfunction, an error in the ATK documentation, or an error in the ATK Control Panel or study setup. Complete one report per incident.
Assign each report a unique Discrepancy Report Number. You may want to simply sequentially number the reports starting at 1, or you may want to use a more elaborate numbering system.
Record the particulars about your system. This includes the DFdiscover Release being tested at your site (e.g., 5.3.0 ), the Server Operating System and Version.
Record the Test Number that you were executing when the problem occurred. This is the number that identifies the current step in the plan (e.g., 6.4.5).
Describe, as accurately and as completely as possible, the problem that occurred. Include any error messages that appeared on screen. Can someone who was not sitting at the computer when the problem occurred understand your description?
If you were able to work around the problem and continue, describe the workaround that was used.
Record your name, title, signature and the current date on the report. Sign it.
If the discrepancy appears to be an error that needs resolution by DF/Net Software ULC, forward the report to DF/Net Software ULC via email to
<email@example.com>. Record that a copy of the report has been sent to DF/Net Software ULC and the date that it was sent.
If a resolution to the problem becomes available, either internally, or from DF/Net Software ULC, provide a description of that resolution and the date.