Bug Reporting Module
Explore these guides to optimize your bug tracking and reporting processes in Crosscheck.
Bug Reporting Module
Contents
How to Retest a Bug?
Date Updated: 01 July, 2024
Easily retest your bugs in Crosscheck from the Action column or by right-clicking. Choose a status, specify the version you're testing, add evidence and notes as necessary, and click save to update.
Who can use this Feature?
- Except for Developers, all roles (Admin, Owner, Project Manager, and QA) have access to retest bugs from both projects and bugs.
How to retest a bug?
Step 1: Choose a Project
- Log in to the Crosscheck website: Crosscheck Login.
- Go to Bug Reporting Section. Click on the bug, you want to retest.
Step 2: Fill in the Details
- Click on the Retest icon from the Action Menu or right click.
- A Retest form will appear. Choose a status (like Closed or Reproducible).
- Add the version of the website you're testing.
- Include any evidence or notes if needed.
Step 3: Save Your Changes
- Click the "Save" button to update the bug's status.
Step 4: Check Retest History
- If you want to see the bug's retest history, click on the "Retest History" tab
Frequently Asked Questions (FAQs):
What are the benefits of using the Retest feature?
The Retest feature allows for systematic verification of bug fixes, ensuring that issues are properly addressed before moving forward in the development process. It also maintains a clear history of bug retests, aiding in accountability and tracking progress.
Can I update multiple bugs' retest status at once?
Currently, the Retest feature is designed to update one bug at a time. Each bug must be individually retested and updated with the appropriate status and details.
Is there a limit to how many bugs I can retest based on my subscription plan?
Yes, the number of bugs you can retest varies based on your subscription plan. Users in the free plan can retest up to 500 bugs, while Basic and Premium plans offer higher limits of 3,000 bugs and unlimited bugs, respectively.