# Why are integration specs written in QUnit?

**URL:** <https://meta.discourse.org/t/why-are-integration-specs-written-in-qunit/45638>\
**Category:** Development\
**Created:** [14 Junio, 2016 06:56 UTC](https://meta.discourse.org/t/why-are-integration-specs-written-in-qunit/45638 "2016-06-14T06:56:21Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [15 Junio, 2016 05:52 UTC](https://meta.discourse.org/t/why-are-integration-specs-written-in-qunit/45638/10 "2016-06-15T05:52:43Z")

</div>

I usually use the term “smoke test” for those.

[discourse/spec/phantom\_js/smoke\_test.js at b3965eb06994fbe11b5a945efc99b136714b3fe3 · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/b3965eb06994fbe11b5a945efc99b136714b3fe3/spec/phantom_js/smoke_test.js) has got to pass for a build to be stamped with test passed.

We have “integration” tests on the server that look at end-to-end server behavior. And “integration” tests in qunit for end-to-end client behavior.

But the “smoke test” is the only test we have the glues everything together and tests a real production instance.

---

_[View the full topic](https://meta.discourse.org/t/why-are-integration-specs-written-in-qunit/45638)._