Testing Guidelines
First of all: thank you for testing! Your feedback is invaluable for improving the editor.
How to report an issue
Please file issues in the GitHub issue tracker.
When filing an issue, include as much information as possible:
- What you did — step-by-step instructions to reproduce the problem
- What you expected — what should have happened
- What actually happened — what went wrong, including any error messages
- Your setup — operating system, editor version, and whether you were connected to a G2 device
- A patch file — if the issue is related to a specific patch, attach the
.pch2 file
The more detail you provide, the better. If I cannot replicate the issue, I cannot investigate or fix it.
Tips for good bug reports
- Try to find the minimal steps to reproduce — the simpler, the better
- Check if the issue is already reported before filing a new one
- One issue per report — don’t combine multiple problems in one ticket
Viewing the console log
The editor logs USB traffic, connection status, and commands to the DevTools console. Including this output in a bug report is very helpful.
To open the console:
- From the menu: View → Toggle DevTools (or press
Cmd+Shift+I on Mac, Ctrl+Shift+I on Windows/Linux)
- Click the Console tab in the panel that opens
To save the log:
- Right-click anywhere inside the console panel
- Choose Save as… and save the file
- Attach the saved file to your issue report