The user interface being complicated and confusing is not an appropriate part of an incident report covering the observation of a failure during testing, as it is a subjective opinion and not a factual description of the failure. An incident report should include objective and relevant information that can help to identify, reproduce, and resolve the failure3 defines an incident report as follows:
An incident report is a document that records the occurrence of an abnormal or unexpected event during testing, such as a deviation from expected results, a defect in the system under test, or a problem in the test environment. An incident report typically includes the following information:
Identifier: A unique identifier for the incident report.
Summary: A brief description of the incident.
Incident details: A detailed description of the incident, including the inputs, expected results, actual results, environment, date and time, severity, priority, and any other relevant information.
Steps to reproduce: A sequence of steps that can be followed to reproduce the incident.
Attachments: Any screenshots, logs, files, or other artifacts that can help to understand or reproduce the incident.
