ELI5 QA'ing and BUGs
Example of a good workflow
- TESTER: Opens up the application for testing.
- TESTER: Finds a QA error.
- TESTER: Goes to Gitlab and makes an issue to the correct repository.
- TESTER: Fills out the bug-report.md template and describes briefly what happened and gives screenshots.
- TESTER: Assign the developer if you know who is working with said case. OR notify on Discord that new issues are up.
- DEVELOPER: Sees Gitlab issue.
- DEVELOPER: Opens Gitlab issue.
- DEVELOPER: Finds a way to fix the issue.
- DEVELOPER: Comment on the issue if any actions were made to fix the issue.
- DEVELOPER: Add screenshots or proof of your fixes.
- TESTER: Sees that comments or so have appeared on the issue.
- TESTER: Check if developer actually did something.
- TESTER: Give thumbs up if problem is solved. If not..
- Repeat.
Example template
- Add bug-report.md to your repositories .gitlab/issue_templates
- https://gitlab.labranet.jamk.fi/help/user/project/description_templates
## Summary
(Summarize the bug encountered concisely)
Steps to reproduce
(How one can reproduce the issue - this is very important)
## What is the current bug behavior?
(What actually happens)
## What is the expected correct behavior?
(What you should see instead)
## Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
## Possible fixes
(If you can, link to the line of code that might be responsible for the problem)
/label ~Bug
/milestone Backlog
Filled example
Summary
History section in the main page has the team summary from 2022 in Finnish even tho its supposed to be in English
Steps to reproduce
Go to the English wimmalab.org site and scroll down. https://www.wimmalab.org/en
What is the current bug behavior?
History section in the main page has the team summary from 2022 in Finnish.
What is the expected correct behavior?
It's supposed to be in English.
Relevant logs and/or screenshots
Possible fixes
Fix the code or the JSON depending on which is causing the bug.
/label ~Bug /milestone Backlog