Verify and Close Bugs

2025-12-27 13:03:34

Sanplex Content

162

Last edited by WANG JING on 2025-12-27 13:03:34

Share links

Summary : This section describes the standard bug lifecycle in Sanplex: create, confirm, resolve, verify, and close. It explains how developers confirm reproducibility, how testers validate fixes before closing, and how to reactivate recurring bugs. It also covers copying bugs and batch editing actions.

1. Verify Bugs
2. Close Bugs
3. Reactivate Bugs
4. Copy Bugs
5. Batch Edit Bugs

In Sanplex, the bug workflow is:

Create Bug → Confirm Bug → Resolve Bug → Verify and Close Bug

1. Verify Bugs

After a bug is submitted, developers need to confirm whether the bug actually exists and is reproducible. This helps avoid cases where an issue occurs only in an individual environment and cannot be reproduced in other environments. After clicking OK to confirm the bug, developers can begin resolving it.

图1

2. Close Bugs

After developers confirm the resolution, testers must verify the bug again. Once the fix is verified, click Close.

图2

At this point, the bug lifecycle is complete.

3. Reactivate Bugs

If a bug occurs again and has not been fully resolved, you can edit the bug or click Reactivate on the bug detail page to reopen it and hand it back to developers for further processing.

图3

4. Copy Bugs

Use Copy Bug to quickly submit a new bug. For example, when the same bug occurs in different projects, you can copy an existing bug to create a similar record.

图4