# Does Mattermost have testing except public automated ones? i.e. How to persuade my manager Mattermost is bug-free?

**URL:** <https://forum.mattermost.com/t/does-mattermost-have-testing-except-public-automated-ones-i-e-how-to-persuade-my-manager-mattermost-is-bug-free/11629>\
**Category:** Troubleshooting\
**Created:** [May 7, 2021, 5:58am UTC](https://forum.mattermost.com/t/does-mattermost-have-testing-except-public-automated-ones-i-e-how-to-persuade-my-manager-mattermost-is-bug-free/11629 "2021-05-07T05:58:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fzyzcjy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/fzyzcjy/32/4786_2.png) [@fzyzcjy](https://forum.mattermost.com/u/fzyzcjy)\
**Post date:** [May 7, 2021, 5:58am UTC](https://forum.mattermost.com/t/does-mattermost-have-testing-except-public-automated-ones-i-e-how-to-persuade-my-manager-mattermost-is-bug-free/11629/1 "2021-05-07T05:58:43Z")

</div>

Hi, I want to persuade my manager into using Mattermost. However, he asked: How does Mattermost ensure its code quality? How does it ensure bug-free?

I do have checked the open source code and see some tests inside the repository. So I wonder whether that is the whole story, or whether Mattermost have some hidden tests that is not visible in GitHub? Or mattermost has some manual tests (e.g. a tester works everyday to test the product)?

How should I answer my manager?

---

<div class="post-metadata">

**Author:** ![jasonblais](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/jasonblais/32/720_2.png) [@jasonblais](https://forum.mattermost.com/u/jasonblais)\
**Post date:** [May 11, 2021, 10:36pm UTC](https://forum.mattermost.com/t/does-mattermost-have-testing-except-public-automated-ones-i-e-how-to-persuade-my-manager-mattermost-is-bug-free/11629/2 "2021-05-11T22:36:56Z")

</div>

Hi @fzyzcjy excellent question!

Here is an outline our release process along with key testing phases of each of our releases in this blog: [How our remote team ships Mattermost like clockwork](https://mattermost.com/blog/how-our-remote-team-ships-like-clockwork/)

The release process includes a mix of automated and manual testing carried out each month to ensure a high quality, stable release.

We are also working on a full QA test automation of the core features of the platform, including an end-to-end testing hackathon currently on-going with our community: [E2E Test Automation Hackathon (May 3 - 31)](https://forum.mattermost.com/t/e2e-test-automation-hackathon-may-3-31/11616)

Finally, we also support an [Extended Support Release (ESR)](https://docs.mattermost.com/administration/extended-support-release.html), which is intended for organizations who value stability over having the newest features and improvements, or who have a long internal testing and certification process to undergo when upgrading.

Hopefully this is helpful! If you have any further questions, I’d be happy to help clarify!

Jason