Write Better Ember Tests

Jon Pitcherella
Jul 27, 2016 · 4 min read
Image for post
Image for post

If you’re not testing your code, well, you’ve got some nerve. For the rest of us rational people, let’s look at some basic tips for writing better Ember tests.

What Makes a Good Test

1. Easy to Reason

2. Specificity

3. Speed

Be Verbose

Have a meaningful test name:

Even though an assertion message is optional, it provides a good overview of what you’re testing:

Page Object

In this trivial example, the first test demonstrates a problem where as you start to add more tests, you will end up writing the same selectors multiple times. In the second test, it should be clear that the page variable could be refactored and re-used across tests. Now all of your tests reference page.$button; One change to the page object now updates all of your tests using it.

An even better approach would be to leverage the ember-cli-page-object addon:

In this example, we setup a page object which has all the parts of the page we care about, similar to the examples prior. With ember-cli-page-object, tests become much easier to reason because our assertions become almost human readable: page.button.isVisible could be understood by non-developers. ember-cli-page-object also makes writing tests faster for developers. Tests can be quickly read and understood without having to recall which jQuery selector to use to find your element.

Pro Tip: I have found id and class selectors volatile over time. I have found using a data-test attribute to be much more stable. For example:

<p class=”strong” data-test=”description”>Something</p>

In this piece of HTML, we have a <p> tag that has two attributes, class and data-test. class may change over time as styles change, or naming convention changes. data-test is more of a universal selector for this element that denotes what the element is and signals to the developer that it’s used by tests and should be changed with hesitation.

Mock Server Requests

  • No backend dependency to run your app tests
  • Data and state are ephemeral
  • It’s faster to mock various server scenarios

There are a few ways to achieve this, but my personal favorite is ember-cli-mirage. TL;DR:

  • Your application is going to make web requests, for example: GET /api/things
  • You’re going to use Mirage to intercept web requests.
  • You’re going to send a “mock” response so your tests can run without actually hitting a backend.

Pro Tip: ember-cli-mirage does not currently support the idea of scenarios. For example, I want GET /api/things to return a specific response most of the time, but in some different case, I want it to return something else.

Here’s what I have found to be a good solution:

  • Define your Routes as if they were the “happy path” — the data that is returned most of the time.
  • In the test that expects something different, specifically override that route, for example:

This is recommended by Mirage and can be found in their documentation here.

Final Thoughts

Make no mistake, tests can be challenging. They often involve the same amount, or more code than your application. No matter how easy it is to write tests, they still take time, which could be time spent writing more features or fixing bugs. The real key to writing good tests is understanding their worth. Your time is the most valuable asset you have. Don’t waste it by debugging things a simple test would have caught.

Have some tips of your own? I’d love to hear them.

Web Development, Ember, JavaScript, Testing


Originally published at jonpitcherella.com on July 27, 2016.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store