Better assertion message when ember asserts.

[kiwiupover]

The object that the error is thrown on is returned as [object Object].

Assertion Failed: You modified image1xFile twice on [object Object] in a single render.

I believe ember overwrites the toString for ember created objects like components to return the name of the object but the ember-quint is not overwriting the toString method for objects it creates.

@rwjblue maybe you can give more context here.

[rwjblue]

👍 discovered this while pairing with @kiwiupover

@trentmwillis - I'd love your thoughts here...

[rwjblue]

I am happy to add a toString to the context when it is set in ember-qunit and/or ember-test-helpers, but it seems like it may be a generally useful thing upstream in QUnit?

[trentmwillis]

I think I'm missing something, it sounds like the suggestion is to add toString to the test environment, which seems odd to me, as you shouldn't be passing the test environment into your application code.

[kiwiupover]

In an integration test where a component is instantiated the test is the outside context. Ember when makes an assertion at that point the test is the object that ember is using in the assertion object hench test.toString() returns [object Object] not a helpful error.

[trentmwillis]

Okay, thanks that makes more sense. I think this is something that should be handled in ember-test-helpers, as it seems like it could also apply to ember-mocha and, as it stands, it seems primarily related to an Ember-specific debuggability issue. Though if there are other common use cases, feel free to open an issue upstream with QUnit.

[rwjblue]

👍 - Sounds good, I'll work up a PR for ember-test-helpers and we can discuss in more detail there...

[kiwiupover]

@rwjblue would you mind if I write the PR.

[Turbo87]

seems like this was resolved by emberjs/ember-test-helpers#181