Server Development
Posts: 236
Joined: Fri Apr 10, 2015 3:08 pm
Sun Dec 30, 2018 9:32 am
Bug reports guideline (updated)
Nothing speeds up the fixes creation as good as a properly composed bug report ^_^
That's just a little tip on how to compose one.
Normally, that should include the following:
- Brief description
- Expected behavior
- How it actually works
- Steps to reproduce it
- (if possible) Some visual attachments, be it a screenshots and/or gif/video recording.
Attachments are not required, but having a snapshots of a game when some weird stuff happens might help a lot in issue pinpointing process - it's pretty normal that some bugs might be hard to reproduce, thus inflating the work time just because a dev tries to get that to work as reported.
That's pretty much it. If you have any suggestions/objections/propositions - feel free to reply!
Cheers!
That's just a little tip on how to compose one.
Normally, that should include the following:
- Brief description
- Expected behavior
- How it actually works
- Steps to reproduce it
- (if possible) Some visual attachments, be it a screenshots and/or gif/video recording.
Attachments are not required, but having a snapshots of a game when some weird stuff happens might help a lot in issue pinpointing process - it's pretty normal that some bugs might be hard to reproduce, thus inflating the work time just because a dev tries to get that to work as reported.
That's pretty much it. If you have any suggestions/objections/propositions - feel free to reply!
Cheers!