Use web notifications for betterifying your TDD

[bcardarella]

If your browser supports web notifications a new Notifications
checkbox will appear in the toolbar menu. When checked a Fail
notification will show when any tests have failed and a Pass
notification will show when all tests are green. Tomsters added for
scale.

[bcardarella]

I wasn't quite sure how to test web notifications. And I didn't know of a better place to put that code. Feedback welcome and I'll adjust as necessary.

[bcardarella]

This is of course best used when you are in your code and saving, the test suite auto-reruns and you won't have to switch back to the browser to see the result.

[rwjblue]

Very cool. I like.

[stefanpenner]

very cool.

Is it possible to extract as much as possible to a bower project. This will make upgrading easier

[lukemelia]

Nice!

On Friday, May 23, 2014, Stefan Penner notifications@github.com wrote:

very cool.

Is it possible to extract as much as possible to a bower project. This
will make upgrading easier

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/804#issuecomment-44076094
.

[twokul]

iLike

[twokul]

maybe?

!!QUnit.urlParams.notification

[bcardarella]

ping @stefanpenner, everything has been extracted into two libraries:

• https://github.com/dockyard/qunit-notifications provides all of the web notification support and can be used with any qunit test suite. Adds configuration options for customizing the notification messages
• https://github.com/dockyard/ember-qunit-notifications provides the tomster images and has qunit-notifications as a dependency

I tried to move everything out of tests/test-loader.js but could not see another place to put the notification initializer. I'm open to suggestions.

[davidjrice]

This is cool! however it causes the this error running ember serve if you have an app generated prior to ember-cli version 0.0.29 and don't have qunit-notifications added to your app's bower.json.

Affects ember-cli version 0.0.29 to 0.0.33.

version: 0.0.29
Livereload server on port 35729
Serving on http://0.0.0.0:4200
ENOENT, no such file or directory 'vendor/qunit-notifications/index.js'

I know we're pre-release so just adding this here in case the note is useful to someone upgrading. However, I wonder if there is a way to safely do the import?

[abuiles]

@davidjrice did you run ember init?

[stefanpenner]

they seem to be in the new blueprint: https://github.com/stefanpenner/ember-cli/blob/master/blueprints/app/files/bower.json#L16

[davidjrice]

@abuiles yep, but on a version < 0.0.29. @stefanpenner yes they're in the blueprint okay.

[mfeckie]

@bcardarella Is there any config that allows us to turn this on by default when starting ember test --server ?

[bcardarella]

@mfeckie doesn't that run testem? I actually have not tried to use the notifications with testem. I suppose there could be an option added to opt-in to them in your .ember-cli file

[bcardarella]

That's assuming they even work with with testem

[mfeckie]

@bcardarella, yeah, testem fires up chrome and phantomjs. It's no big deal to click to turn on notifications. Just curious. Thanks for your answer