Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with ember-cli-blanket + ember-cli-mirage #75

Open
jagthedrummer opened this issue Jul 23, 2015 · 6 comments
Open

Problems with ember-cli-blanket + ember-cli-mirage #75

jagthedrummer opened this issue Jul 23, 2015 · 6 comments

Comments

@jagthedrummer
Copy link

I've followed the instructions in the README about setting up the passthrough for mirage in the config file. When I do that my tests all run fine, but then the very last one fails with this error:

not ok 28 PhantomJS 2.0 - JSHint - unit/torii-providers: global failure
    ---
        actual: >
            null
        message: >
            InvalidStateError: DOM Exception 11: An attempt was made to use an object that is not, or is no longer, usable.
        Log: >
            [object Object]
            [object Object]
            [object Object]
    ...

The failure only happens in the command line runner. In the browser everything works as expected, so I don't have a way to inspect those objects to see what is being logged.

This is in the test suite for an ember-cli add-on and it happens with both the json and lcov reporters.

@jschilli
Copy link
Collaborator

if you turn off the coverage flag for the CLI runner does the error occur?

On Jul 23, 2015, at 12:22 PM, Jeremy Green [email protected] wrote:

I've followed the instructions in the README about setting up the passthrough for mirage in the config file. When I do that my tests all run fine, but then the very last one fails with this error:

not ok 28 PhantomJS 2.0 - JSHint - unit/torii-providers: global failure
---
actual: >
null
message: >
InvalidStateError: DOM Exception 11: An attempt was made to use an object that is not, or is no longer, usable.
Log: >
[object Object]
[object Object]
[object Object]
...
The failure only happens in the command line runner. In the browser everything works as expected, so I don't have a way to inspect those objects to see what is being logged.

This is in the test suite for an ember-cli add-on and it happens with both the json and lcov reporters.


Reply to this email directly or view it on GitHub #75.

@jagthedrummer
Copy link
Author

When I turn off the coverage flag the error does not occur, and the test runner reports only 27 tests. So it seems weird that it's failing out on a 28th test with the coverage flag enabled.

@sglanzer-deprecated
Copy link
Owner

@jagthedrummer I know this is an older issue, but are you still experiencing this and if so, would you be able to provide steps to reproduce on a new addon project?

@duksis
Copy link

duksis commented Feb 8, 2016

having the same issue when following the readme
when using the new passthrough option for mirage tests are passing, but no coverage generated :)

@andrewmtoy
Copy link

I'm seeing the same issue. I think this issue and issue 142 are related.

@andrewmtoy
Copy link

andrewmtoy commented May 27, 2016

I fixed this issue by upgrading pretender to 1.1.
You will also need jquery version >= 2.x.

miragejs/ember-cli-mirage#404

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants