Skip to content

Commit

Permalink
Updating assertion language
Browse files Browse the repository at this point in the history
I don't see a reason to bend over backwards to support the exact same
assertion language for this (deprecated) feature. This new message is
sufficiently clear.
  • Loading branch information
ef4 committed Apr 12, 2015
1 parent e01d5df commit a770db3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions packages/ember-routing-htmlbars/tests/helpers/outlet_test.js
Original file line number Diff line number Diff line change
Expand Up @@ -109,12 +109,12 @@ QUnit.skip("outlet should assert view is specified as a string", function() {

});

QUnit.skip("outlet should assert view path is successfully resolved", function() {
QUnit.test("outlet should assert view path is successfully resolved", function() {
top.setOutletState(withTemplate("<h1>HI</h1>{{outlet view='someViewNameHere'}}"));

expectAssertion(function () {
runAppend(top);
}, "The view name you supplied 'someViewNameHere' did not resolve to a view.");
}, /someViewNameHere must be a subclass or an instance of Ember.View/);

});

Expand Down

1 comment on commit a770db3

@mmun
Copy link
Member

@mmun mmun commented on a770db3 Apr 13, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Please sign in to comment.