Clear Title
- Good title is a must, as the moderator should be able to understand what the bug report is about from the title alone.
- Report one bug in a single report, no more, no less. If you put in too many bugs, some of them may be overlooked.
- This section should expand on the title by explaining when/where/why/how the issue occurs.
- The Expected Results section should focus on how the app behaves in normal conditions. Ex: The authorisation phase completes successfully, the user is logged into the newly created account and redirected to the home page of the app.
- The Steps to Reproduce section should focus on providing accurate and specific information so that the issue could be replicated.
- Bugs can be classified by how severe the issue is. We use 5 categories to identify the severity of the bug.
- Critical - the bugs we need to fix immediately. These are the bugs that will prevent the product from working if it were released in that state. This includes crashing, freezing for which no workaround is possible.
- High - the same examples as with critical priority bugs. However high priority bugs don't interrupt the application/ workflow or at least can be avoided with a workaround.
- Medium - the bug does not cause a failure, does not impair usability and does not interfere with the fluent work of the system and programs.
- Low - the bug is aesthetic, is an enhancement or is a result of non-conformance to a standard - typing errors/ aesthetic inconsistencies
- Usability - Suggestions, features
- With every bug report you need to say which device and operating system you used to identify the bug.
Other Notes/Error Messages
- Add here all the necessary and relevant evidence to show the problem your are describing. Evidence can be either of the following: screenshots, videos, crash or console logs (for crashes).
Comments
Post a Comment