The Bug lifecycle within Sanplex follows this workflow: Create Bug -> Confirm Bug -> Resolve Bug -> Verify & Close Bug.

How do testers verify and close Bugs in Sanplex? Check out the video explanation:

【视频介绍】

I. Verifying a Bug

After a Bug is submitted, developers need to confirm whether the Bug actually exists to avoid situations where a Bug only occurs in a personal environment and cannot be reproduced elsewhere. After clicking Confirm to verify the Bug, the developer can begin resolving it.

图1

II. Closing a Bug

Once the developer confirms the resolution for a Bug, the tester needs to verify the Bug again. After confirming it has been resolved, click Close.

图2

At this point, the lifecycle of a Bug is complete.

III. Activating a Bug

If a certain Bug reappears or was not completely and thoroughly resolved, you can edit the Bug or click the Activate button on the Bug details page. This activates the Bug and assigns it back to the developer for further processing.

图3

IV. Copying a Bug

You can quickly submit a new Bug by using the Copy button. This is useful, for example, when the same Bug appears in different projects.

图4

V. Batch Editing Bugs

By selecting multiple Bugs on the Bug list page, you can perform batch operations, including editing, confirming, closing, activating, and selecting resolutions.

图5