# Plugin QUnit tests are not running as part of rake qunit:test

**URL:** <https://meta.discourse.org/t/plugin-qunit-tests-are-not-running-as-part-of-rake-qunit-test/59577>\
**Category:** Development\
**Created:** [3월 20, 2017, 8:29오후 UTC](https://meta.discourse.org/t/plugin-qunit-tests-are-not-running-as-part-of-rake-qunit-test/59577 "2017-03-20T20:29:06Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [7월 17, 2017, 6:24오후 UTC](https://meta.discourse.org/t/plugin-qunit-tests-are-not-running-as-part-of-rake-qunit-test/59577/7 "2017-07-17T18:24:30Z")

</div>

> [@david](#):
>
> Maybe that’s something that could be used internally to make sure core plugins get tested properly? Or alternatively the LOAD\_PLUGINS variable could be set in the Dockerfile?

@sam (I think discourse\_test is your creation?), what do you think about loading plugins for the tests-passed pipeline?

The [plugin qunit tests](https://travis-ci.org/discourse/discourse/jobs/254507190) are now all fixed, but today [many core plugin rspec tests](https://travis-ci.org/discourse/discourse/jobs/254507188#L7282) were broken by the removal of the old markdown engine, yet the commit still ended up in tests-passed. (fails are in `poll`, `discourse-details` and `discourse-narrative-bot`).

---

_[View the full topic](https://meta.discourse.org/t/plugin-qunit-tests-are-not-running-as-part-of-rake-qunit-test/59577)._