san650 / ember-cli-page-object / 1228

98%

Pull #385

travis-ci

Fix compatibility exports

When using `require()`, we're not guaranteed that the module we're `requiring` is resolved yet, so it could just be an empty object with no exports. This has actually happened to a user, although it's tightly tied to their module dependency graph, and I haven't been able to easily repro it, nor do I think writing a unit test for it is feasible :( But the fix is to "lazy call" the `@ember/test-helpers` methods so we can be assured that they are resolved by the time we call them, even if they aren't when we export our compatibility functions.

256 of 267 branches covered (95.88%)

Branch coverage included in aggregate %.

18 of 18 new or added lines in 1 file covered. (100.0%)

840 of 843 relevant lines covered (99.64%)

471.43 hits per line