ember-cli-mirage | An Ember Addon to easily add Mirage JS to your Ember app | Addon library

Ola @Divakar, thanks for your question! And Welcome to Ember

Looking at your question it seems like it could be related to an issue that we had recently in ember-data where the generators were broken. I think they were fixed in ember-data@3.11.1 but from your package.json it would seem that you have ember-data@3.11.0

If you want to update ember-data and see if the issue is still there you can run the following:

Mirage factory are meant to generate testing data:

Factories are classes that help you organize your data-creation logic, making it easier to define different server states during development or within tests.

The factory is only run once by server.create('foo') or server.createList('foo', 10) to create initial data for the records. This helps you to avoid code duplication in tests and scenarios. But it's not a model representing that record.

Actually Mirage does not support something like computed properties out of the box. But you could achieve it by customizing the serializer used. Overriding the serialize method should do the trick:

Ember CLI Mirage intercepts all ajax (XMLHttpRequest) and fetch requests by default. You have to whitelist the requests that should be passed through by using server.passthrough() method. (this is server instance in mirage/config.js.) You could use relative and absolute URLs with server.passthrough as well as with all route handlers. So server.passthrough('https://(my auth0 domain).auth0.com/userinfo') should fix your issue.

You're logging response which is actually the return value of store.findAll, rather than the HTTP response from Mirage.

store.findAll wraps up the HTTP request/response logic, and actually responds with an instance of an Ember Data model, or an array of models. In your case since you called findAll, the response is an array of Ember Data models.

If you want to see the details of Mirage's response, check your console for something like Mirage: 200 OK for GET /accounts. You should be able to expand that to see the details of the request and response that Mirage handled.

As @jelhan points to in the comment above, the issue here is missing test environment settings within the environment.js configuration.

To fix the UnrecognizedURLError, adding ENV.locationType = 'none' satisfies the requirements of testem.

I also replaced the other environment variables found in the linked block.

My test environment configuration now looks like this:

Let's try to focus a single relationship, since there's a lot going on in the question you've posted. We'll look at second-resource.

It looks like Mirage is sending back second_resource_ids under the attributes key of the first_resource primary data in the JSON:API payload. That tells me Mirage thinks second_resource_ids is an attribute of first_resource, when in fact it's a relationship.

Assuming your Models & Relationships are setup correctly, you need to tweak the way you're creating data in Mirage.

If you take a look at the Associations section of the Defining Routes guide, you'll see this message:

Mirage's database uses camelCase for all model attributes, including foreign keys (e.g. authorId in the example above)

Right now, you're doing this:

Do you need to override it for all serializers or just one?

If all, you could so something like this on the application serializer:

• ember-cli is having another dependency called ember-cli-mirage which is dependant on faker.
• On previous machine, check what versions are there for node, npm, ember-cli, bower and phantomjs-prebuilt.

• Either you can use same versions. Or try clearing cache and updating only npm using:

I think the problem you are facing is due to the fact that your mirage data isn't formatted as-per JSON-API specifications.

mirage/config.js =>