blimmer/ember-cli-mirage-server-shutdown.md

## ember-cli-mirage-server-shutdown.md

      
    Raw
  

              ember-cli-mirage-server-shutdown.md
            
          
    What's the problem?

Mirage starts up a global server when your app initializers run. That means that each time you destroy your app, you need to call
server.shutdown(). However, if you are on Ember CLI 1.13.8 or below, you won't have a destroy-app.js helper so we can automatically
do this for you.
What can I do?

There are several things you can do to fix this. You only need to do one of the options below.
Upgrade Ember-CLI

This is the easiest way to fix this problem. Upgrade to Ember CLI 1.13.9 or higher (follow the upgrade steps with ember init) and re-run ember g ember-cli-mirage. That's it!
I wrote an ember watson formula to help convert your old acceptance tests to use this new destroyApp helper. See ember watson .
Create your own destroy-app helper


Create tests/helpers/destroy-app.js
Use the contents of the destroy-app file
Replace instances of Ember.run(this.application, 'destroy') with the new destroy-app call. You can see how it's done here

Manually shutdown after each startApp

Ensure that you manually insert a server.shutdown() after the Ember.run(this.application, 'destroy') in acceptance tests.