# How are you testing your Ember app?

**URL:** <https://discuss.emberjs.com/t/how-are-you-testing-your-ember-app/6257>\
**Category:** Testing\
**Created:** [September 12, 2014, 8:45pm UTC](https://discuss.emberjs.com/t/how-are-you-testing-your-ember-app/6257 "2014-09-12T20:45:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielavila](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/danielavila/32/12474_2.png) [@danielavila](https://discuss.emberjs.com/u/danielavila)\
**Post date:** [September 12, 2014, 8:45pm UTC](https://discuss.emberjs.com/t/how-are-you-testing-your-ember-app/6257/1 "2014-09-12T20:45:38Z")

</div>

My team is searching for a solution on how we can test our Ember application. We are curious on how the Ember community is testing theirs. So I decided to post this, and hope to hear some good ideas from you guys. Thanks for the replies in advance!

What are you using for unit testing?

Are you using qunit and running tests in the browers? Are you using testem, karma, etc?

---

<div class="post-metadata">

**Author:** ![stravid](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/stravid/32/10138_2.png) [@stravid](https://discuss.emberjs.com/u/stravid)\
**Post date:** [September 13, 2014, 9:22am UTC](https://discuss.emberjs.com/t/how-are-you-testing-your-ember-app/6257/2 "2014-09-13T09:22:28Z")

</div>

We are exclusively developing with Ember CLI so our QUnit test suite can be run in the browser or command line. If you haven’t looked at Ember CLI yet take a peek, you will be positively surprised!

---

<div class="post-metadata">

**Author:** ![mixonic](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/mixonic/32/14829_2.png) [@mixonic](https://discuss.emberjs.com/u/mixonic)\
**Post date:** [September 13, 2014, 5:28pm UTC](https://discuss.emberjs.com/t/how-are-you-testing-your-ember-app/6257/3 "2014-09-13T17:28:47Z")

</div>

There is a rather extensive [Testing Guide](http://emberjs.com/guides/testing/) on the Ember.js website. Lots of ideas there.

Most Ember projects use Ember’s testing mode, [QUnit](http://qunitjs.com/), [ember-qunit](https://github.com/rwjblue/ember-qunit) for nice setup helpers, and [Pretender](https://github.com/trek/pretender) or something similar for HTTP mocking. These are provided out of the box with [ember-cli](http://www.ember-cli.com/), though I have seen many projects use them without ember-cli.

ember-cli implements livereload, so simple CI is as easy as leaving a browser window open with the tests. It also comes with a phantomJS runner out of the box for use on CircleCI, Travis, or another hosted CI solution. Testem is sometimes used, but I don’t usually touch it.

You _could_ test an Ember app with Mocha or any arbitrary runner, but QUnit (for better or worse) is the most documented path.