1. Decrease time to ship a bug fix release
2. Raise the quality of the software by reducing number of manual tests
Our end-to-end (E2E) tests, written in JavaScript using the Cypress framework, help us cut down manual tests, and are an integral part of the product development process.
Event Details
1. Event runs from May 3rd to May 31st, 2021. Any submitted PRs must be merged by June 11th 4:00 PM PST to qualify. Those closed by maintainers as incomplete, invalid or spam are not counted.
2. Five merged pull requests wins you a swag bag
3. Top-3 contributors win a special award.
4. First-time contributors receive a custom-printed Mattermost Mug! https://forum.mattermost.org/t/limited-edition-mattermost-mu...
How to Join
1. Join our Test Automation Hackfest channel in Mattermost: https://community.mattermost.com/core/channels/e2e-test-auto...
2. Review test cases ready for automation: https://docs.google.com/spreadsheets/d/1auZlKnfWPtAXhl0dJYyN...)
3. Find a test case you’re interested in and either post in the Test Automation Hackfest channel, or comment in the spreadsheet.
4. Create a pull request to add a Cypress test automation using this guide: https://developers.mattermost.com/contribute/webapp/end-to-e...
Resources
* Announcement blog post: https://mattermost.com/blog/mattermost-e2e-cypress-test-auto...
* Automated UI testing with Cypress: https://mattermost.com/blog/automated-ui-testing-with-cypres...
* E2E Testing in Mattermost documentation: https://developers.mattermost.com/contribute/webapp/end-to-e...
* Spreadsheet of test cases to automate: https://docs.google.com/spreadsheets/d/1auZlKnfWPtAXhl0dJYyN...
One of our paying customers uses Mattermost so we've started the process of peeking at their API to see what we're up against. Since we've already got Discord/Slack it probably won't be super tough. That being said, there were plenty of gotchas added Discord after we already had slack since their API was different enough to be a bit annoying at times.
Look at email addresses: platforms like Gmail and Yahoo will delete your account for inactivity with adequate advance warning, but they will not release your email address for someone else to claim in the future (on the other hand, paid platforms like Fastmail and Posteo will allow your deleted addresses on their domains to be grabbed by anyone).
With GitLab’s policy of renaming inactive accounts without any warning or notice, any links that someone has shared could later point to a different person. A “404 Not Found” error or an “email address does not exist” error is far better, IMO, than redirecting someone to a totally different person.
If an inactive username is to be released back for use by someone else, there should be a significant duration from the time the username is disabled to the time when it’s available for someone else.
It's to prevent name-squatting, GitHub has a similar policy: https://docs.github.com/en/github/site-policy/github-usernam...
What if I'm hospitalized or away on an extended trip? You just going to let someone else take my account username?
No thanks.
[1] https://about.gitlab.com/support/#dormant-namespace-requests
[2] https://docs.github.com/en/github/site-policy/github-usernam...