Report bugs
How you report a bug while testing depends on where it is. If the bug is in the task you are testing, mark that test case Fail and describe the bug. Don't create a new issue. If the bug is outside the task's scope, create a new issue labeled type: bug in one of the ways below.
Report on the Bandum web app
- Open the task page in the Bandum web app and scroll to the Report a bug section.
- Click Report an out-of-scope bug. If the Connect box appears, paste your GitHub or GitLab token first. See Get started for BAs, POs, and PMs.
- Enter a Title (required). Optionally enter Steps to reproduce, Expected, Actual, Severity, and Related TC.
- Submit. The page shows an Open issue link to the issue it created.
Bandum creates a new issue labeled type: bug. If someone already reported the bug, Bandum adds a comment to the existing issue instead of creating a duplicate.
Report from the command line
ph bandum bug "Cart page is blank when quantity is 0" \
--from GH-12 --tc TC-3 --severity medium \
--steps "Open /cart, set quantity to 0" \
--expected "Shows that the minimum quantity is 1" \
--actual "Blank page, console reports an error"| Flag | Meaning |
|---|---|
--from GH-n, --tc TC-x | The task and test case where you found the bug |
--severity high|medium|low | Severity, written as a severity: ... label. The old values cao, trung-binh, and thap still work and map to high, medium, and low |
--evidence <file> | Attach a screenshot or a small log. You can use it more than once |
--body-file f.md | Use a prewritten body |
--queue | Save to the local queue only and send later |
The command masks secrets before it sends and prevents duplicate reports. If you lose your connection, it saves the bug in .bandum/bugs/. Use ph bandum bug list to see the queue and ph bandum bug push to send it.
You can also skip Bandum and create the issue directly on your project's GitHub or GitLab. Add the type: bug label, and add severity: high, severity: medium, or severity: low if you know the severity.
Keep sensitive data out of issues
Don't paste passwords, tokens, or real customer data into the description, screenshots, or logs. Phillip masks common kinds of secrets, but it can't mask business data.