When should a tick be submitted for testing? - briefly
Submit a tick for testing immediately after detection and before it is deployed in any production environment. If its functionality is uncertain or could impact compliance, testing must be performed without delay.
When should a tick be submitted for testing? - in detail
A tick should be entered into the tracking system only after the issue has been observed and reproduced consistently. The initial step is to verify that the behavior is not a known defect by consulting the existing database of resolved tickets. If the problem is not listed, the reporter must capture the exact steps required to trigger it, including environment details such as software version, configuration settings, and hardware specifications.
Before submission, the reporter should assess the impact on users. High‑severity incidents—those causing data loss, security breaches, or complete service interruption—must be logged immediately, regardless of the stage of the development cycle. Medium‑severity problems that affect functionality for a significant portion of users should be entered as soon as the reproduction steps are documented. Low‑severity anomalies, such as minor UI inconsistencies, can be deferred until a scheduled backlog refinement session.
The ticket must contain the following elements:
- Clear, concise title that identifies the core symptom.
- Step‑by‑step reproduction instructions.
- Expected versus actual results.
- Screenshots, logs, or traces that illustrate the failure.
- Environment information (OS, browser, version numbers).
- Classification of severity and priority according to the project’s matrix.
If the issue arises during a sprint, the ticket should be created before the sprint review meeting to allow the team to estimate effort and decide on inclusion. For defects discovered after a release, the ticket must be submitted promptly to enable hot‑fix planning or inclusion in the next patch cycle.
In summary, submit a ticket when the problem is reproducible, not already documented, and its impact has been evaluated. Include all necessary data to allow the development team to triage, estimate, and resolve the issue without additional clarification cycles.