# 新バージョンリリース時のQAチェックリストはありますか？

**URL:** <https://meta.discourse.org/t/qa-checklist-for-when-new-versions-are-released/81678>\
**Category:** Product Support\
**Created:** [2018 年 2 月 27 日午後 4:31 UTC](https://meta.discourse.org/t/qa-checklist-for-when-new-versions-are-released/81678 "2018-02-27T16:31:24Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![dnsmichi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dnsmichi/32/379505_2.png) [@dnsmichi](https://meta.discourse.org/u/dnsmichi)\
**Post date:** [2018 年 3 月 1 日午後 7:10 UTC](https://meta.discourse.org/t/qa-checklist-for-when-new-versions-are-released/81678/9 "2018-03-01T19:10:06Z")

</div>

You could add more monitoring checks, than e.g. checking if the site is up and its content serves a specific string (I do that with Icinga on [monitoring-portal.org](http://monitoring-portal.org)).

If you for example enable the REST API, there’s many things you can test/check. Even insights into the applications currently running. Since Discourse runs in Docker, there’s a variety of APIs and checks around to go further with Redis, PostgreSQL, Nginx, Ruby-on-Rails, and so on.

You may also go the route with full application and UX monitoring with end2end tests. There’s certain frameworks around like casperJS, not sure though if that works with Discourse. Probably better to have such things automated via API.

But still, you could go the route to trigger events and expect something in return on the current site.

I don’t do that yet, but it is on my list to increase monitoring and always know if the site is fully operational, or if I have hit a bug or a regression.

---

_[View the full topic](https://meta.discourse.org/t/qa-checklist-for-when-new-versions-are-released/81678)._