Support unit and integration tests out of the box.

[blimmer]

This commit maintains the previous behavior where the initializer appends the destination element to the DOM, but allows for falling back to the #ember-testing div in the testing environment.

This resolves #78 and resolves #125

[blimmer]

Thanks!

[lukemelia]

Released as 0.9.0 🎉

[aandis]

After upgrading to 0.9.0, the modal doesn't render at all in my integration test. Falling back to 0.8.8 with suggested workaround

[aandis]

Hm. I was able to reproduce the issue on 0.8.8 if I change the id from fancy-div to ember-testing.

[blimmer]

The change in 0.9.0 is to attach modals to the ember testing div that's created by default when you're running tests. It's hard to say what's going on exactly without some sample code. Here are a few ideas, nonetheless:

• check to see if there are multiple elements in the DOM with the target element id. it might be that there are two divs with the same ID and ember-modal-dialog is not sure how to attach it?
• try overriding the destinationElementId in your app under app/services/modal-dialog.js similar to what's done in this PR and hard-code it to a unique element in your testing DOM

if those things don't help, could you please provide some sample code to further diagnose?