A place for like-minded quality assurance people to come together to help test Mattermost’s software
If you like breaking software, have a keen eye for UI-related bugs and want to help report your findings, here’s how you can join our testing community. You can find help and more information in the following places:
- Join our Contributors server
- Join the ~QA: Contributors channel on the Contributors server
- Forum post
- Blog post
This is where testers explore the software (can be on webapp, mobile apps, or desktop app) and give feedback on anything they think doesn’t make sense or is difficult to navigate or understand. You can download the desktop and mobile apps here.
- Exploratory testing assignments can be located here.
Pre-production features, or features already in production are tested from a feature spec.
- When feature testing assignments are available, they will be located here.
- The GitHub issue will be clearly headed “Pre-production / Production Feature testing” and will include instructions and a spreadsheet for your feedback.
We test the software on the release branch approximately 2 weeks before release (monthly on the 16th) so we can report any bugs.
- When release testing assignments are available, they will be located here.
- The GitHub issue will be clearly headed “Release testing” and will include instructions and a spreadsheet for your feedback.
| Level | Contribution | Swag |
|---|---|---|
| Level 1 - Fan | Someone who has participated in exploratory, release or feature testing and completed valid and detailed feedback | Stickers / Socks |
| Level 2 - Champion | Someone who, apart from participating in testing, also gets involved on the community server and forum (answering questions, repro'ing bug reports, etc) as well as contributing to QA documentation | QA mug |
| Level 3 - Guru | Someone who has surpassed level 2 and who we are considering as a core QA contributor (similar to how we award dev contributors with "core contributor" status) | QA t-shirt |
In addition, anyone who reports a valid bug that is not a known issue, will receive a Bug Hunter coin.