# Check plugin or theme validity

**URL:** <https://meta.discourse.org/t/check-plugin-or-theme-validity/137111>\
**Category:** Support\
**Created:** [December 26, 2019, 5:07pm UTC](https://meta.discourse.org/t/check-plugin-or-theme-validity/137111 "2019-12-26T17:07:47Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [December 30, 2019, 11:15am UTC](https://meta.discourse.org/t/check-plugin-or-theme-validity/137111/14 "2019-12-30T11:15:41Z")

</div>

The development install #howto topics describe how to run tests and I believe that those tests will run against all installed plugins. Many plugins have no tests or might be written such that they would cause tests to fail if it’s designed to change how discourse works.

Also, there is [(Superseded) Set up plugin continuous integration tests on Travis CI](https://meta.discourse.org/t/setting-up-plugin-continuous-integration-tests-on-travis-ci/59612) which will allow you to run tests for a given plugin at every commit.

I would be interested to know how to have Travis run a full test against a particular set of plugins to confirm that there are no conflicts. One day I’ll get around to creating a topic about that.

It is certain that tests of all of the plugins mentioned above will fail and knowing that it fails won’t be of any use to anyone.

---

_[View the full topic](https://meta.discourse.org/t/check-plugin-or-theme-validity/137111)._
