# Suggestions for better plugin maintenance

**URL:** https://meta.discourse.org/t/suggestions-for-better-plugin-maintenance/52337
**Category:** Development
**Created:** [31 Octubre, 2016 16:41 UTC](https://meta.discourse.org/t/suggestions-for-better-plugin-maintenance/52337 "2016-10-31T16:41:51Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [4 Noviembre, 2016 23:23 UTC](https://meta.discourse.org/t/suggestions-for-better-plugin-maintenance/52337/10 "2016-11-04T23:23:54Z")

</div>

It doesn’t look to be a “hot” topic for [@plugin\_authors](https://meta.discourse.org/groups/plugin_authors) .

> [@Developing Discourse Plugins - Part 6 - Add acceptance tests](https://meta.discourse.org/t/beginner-s-guide-to-creating-discourse-plugins-part-6-acceptance-tests/32619):
>
> Previous tutorial: [Developing Discourse Plugins - Part 5 - Add an admin interface](https://meta.discourse.org/t/developing-discourse-plugins-part-5-add-an-admin-interface/31761) Did you know that Discourse has two large test suites for its code base? On the server side, our Ruby code has a test suite that uses [rspec](https://rspec.info/). For the browser application, we have a [qunit](https://qunitjs.com/) suite that has [ember-testing](https://guides.emberjs.com/release/testing/testing-application/) included. Assuming you have a development environment set up, if you visit the http://localhost:3000/tests URL you will start running the JavaScript test suite in your browser. One fun aspect is that …

But I’m wondering if plugins had some type of “if tests fail - exit and continue” thing in place it would help to at least keep any problems contained to the problem plugin(s)

---

_[View the full topic](https://meta.discourse.org/t/suggestions-for-better-plugin-maintenance/52337)._