The Dbug bot is the gear in our machine that keeps Discord Testers running!
Here are some commands that you will use on a daily basis for general bug reporting.
What does this Article Cover?
- Getting Started
- Taking the Quiz
- Adding Roles
- Commands for Checking and Adding Roles
- Bug Reporting Process
- Submitting a Bug
- Bug Submission Flags
- Editing a Bug Report
- Saving your System Information
- Submitting a Bug
- Reviewing Bugs
- Summary of all Commands
Taking the Quiz
To become a bug hunter you must pass our entry quiz. The quiz will test you on basic bug hunter knowledge that you can read here. To begin the quiz, send a direct message to Dbug bot and use the !quiz command.
Command | Command Action |
!quiz | Take the entry quiz on basic bug hunter knowledge |
Adding Roles
To begin submitting bugs, you first need to get access to the category you want to submit a bug for. These commands should be ran in the DMs of the DBug bot.
Command | Command Action |
!role list | View a list of all roles |
!role add <platform> | Add a role |
!role remove <platform> | Remove a role |
Submitting a Bug
In order to submit a bug, you'll need to use the !submit command along with flags to give more details information of the bug!
Submitting a bug consists of multiple pieces of information and these pieces of information are notes using the following flags:
!submit Flags | Flag Meaning |
-t | Title |
-r | Reproduction Steps |
~ |
Begins a new step in the reproduction steps. Note: The first step doesn't need a "~" in front of it. |
-e | Expected Result |
-a | Actual Result |
-c | Client Settings (Discord build) |
-s | System Settings (Phone: device + os version, PC: os version) |
- Here's an example of what this might look like altogether with the !submit command:
!submit -t This is the title -r Step 1 ~ Step 2 ~ Step 3 ~ Step 4 -e This is what is supposed to happen -a This is what actually happens -c Canary 64104 (11dae40) -s Windows 10 pro, 64 bit
On the other hand, finding it difficult to write it yourself or does it just take too long? Fear not - we have a tool to help you out.
Editing your Bug Report
You can edit your bug by using the !edit command, in case you need to update something or you made a mistake when writing the submit command.
Note: The flags to edit are the same as the !submit command, and you can update multiple flags at the same time!
- Editing one flag
!edit <id> -t This is the new Title
!edit <id> -r New step 1 ~ New step 2 ~ New step 3 ~ New step 4
- Editing multiple flags in one go
!edit <id> -t This is the new Title -e This is the new expected result
Saving your System Information
In order to help with the bug repro process (which we'll talk about in the section below), you can check and store your system information using the !info command!
- Checking your saved information
!info check
- Storing/updating your saved information
!info store <platformshorthand> system information
Example:!info store -a OnePlus 6 Android 1.2.3
- For storing settings, the following flags are available:
Storing Settings Flags | Flag Meanings |
-a | Android |
-i | iOS |
-w | Windows |
-l | Linux |
-m | Mac |
Reproducing Bugs
- Confirming the Ability to Reproduce a Bug
!canrepro <id> <information>
Example: !canrepro 2 samsung s20 - android 10
- Confirming the Inability to Reproduce a Bug
!cantrepro <id> cnr message
Example: !cantrepro 5 -w
You can use short hands (-a/-w/-i etc) from stored info in your message
Approval / Denials
You cannot approve your own bug
!approve <id> approval message
Denying your own bug will result in it immediately being moved to denied bugs.
!deny <id> denial message
You can use short hands in your approval / denial. In these commands the shorthands that can be used are: -a, -i, -w, -l, -m
Examples:
!approve <id> comment -w
!deny <id> -w denial message
Attachments to the Bug Report
In order to give more context to the bug, you can also add attachments to your bug report to help out with the investigation! The following attachment types are accepted:
- images: jpg, png, jpeg, heic
- gifs: gif, gifv, mp4
- video links: youtube, youtu, vimeo
NOTE: When attaching a video or screenshot make sure that there is no personal information, invites, slurs or other offensive material in it.
When adding attachments, you need to add a link and give the attachment a name. (Note: Names do not have to be one word.)
- Attaching an Attachment
!attach <id> <url> <name>
Example: !attach 1 <https://i.imgur.com/123456.png> image of mentions bug
- Detaching an Attachment
An attachment can also be removed with the !detach command.
!detach <id> <name>
Summary of All DBug Commands
DBug Commands | Command Meaning |
!quiz | Take the entry quiz on basic bug hunter knowledge |
!role list | View a list of all roles |
!role add <platform> | Add a role |
!role remove <platform> | Remove a role |
!submit | Submit a bug report |
!edit <id> | Edit a bug report |
!info check | Checking your saved information |
!info store <platform flag> <system information> | Storing/updating your system information |
!canrepro <id> <information> | Noting that you can reproduce a bug |
!cantrepro <id> <information> | Noting that you cannot reproduce a bug |
!approve <id> <approval message> | Approving a bug report |
!deny <id> <denial message> | Denying a bug report |
!attach <id> <url> <name> | Attaching an attachment to the bug report |
!detach <id> <name> | Detaching an attachment from the bug report |