# Smoke-testing plugins during upgrade process

**URL:** <https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118>\
**Category:** Feature\
**Created:** [October 1, 2017, 8:18am UTC](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118 "2017-10-01T08:18:48Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [October 2, 2017, 7:29am UTC](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118/11 "2017-10-02T07:29:06Z")

</div>

> [@ChrisBeach](#):
>
> Automated tests are not “mythical” or hard. Most plugins already have them. They’re just not currently being run when a Discourse instance is upgraded.

For the record we always smoke test every official plugin (and run the tests the plugin provides) during our CI process which happens before meta is deployed on every commit.

I don’t see it as the job of the installer to be running the tests is a continuous integration server that should be doing this for everyone. But I am not sure how much extra work I want to take on for the ecosystem right now. Long term I am fine to have a digital ocean instance that is constantly testing plugins against latests commits.

---

_[View the full topic](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118)._