Ember JS | Qunit - Phantom JS Set called on already destroyed object

Asked Aug 06 '15 at 20:21

Active Aug 07 '15 at 22:40

Viewed 66 times

I am running into this weird problem, where Ember Qunit Tests pass successfully when I run a single module. But they fail when I run all modules test cases.

The failure error looks like this

set called on already destroyed object.

Can someone point me in the correct direction to get this fixed please?

edited Aug 07 '15 at 22:40

rahul bose

asked Aug 06 '15 at 20:21

Aditya Kappagantula

1

Could you share more info (how many tests are in the total suite, what does the average teardown look like, what the test in question looks like) – Toran Billups Aug 07 '15 at 02:45
1

can you please explain more? Maybe a sample of how the tests look like? – Dhiraj Aug 07 '15 at 21:12
The problem drills down to the fact that Ember.service is not calling its Will Destroy method for some weird reason! – Aditya Kappagantula Aug 08 '15 at 00:17

Ember JS | Qunit - Phantom JS Set called on already destroyed object

0 Answers0