Setup npm pretest

[duggiefresh]

No description provided.

[ryanflorence]

This assumes consumers are using bower, which is maybe true often but not always. What's the reasoning?

Sent from my iPhone

On Jul 15, 2014, at 12:57 PM, Doug Yun [email protected] wrote:

You can merge this Pull Request by running

git pull https://github.com/duggiefresh/ember-qunit adds-bower-install
Or view, comment on, or merge it at:

#75

Commit Summary

Adds "bower install" to npm's postinstall
File Changes

M README.md (1)
M package.json (3)
Patch Links:

https://github.com/rjackson/ember-qunit/pull/75.patch
https://github.com/rjackson/ember-qunit/pull/75.diff
—
Reply to this email directly or view it on GitHub.

[rwjblue]

I think we might just want to move the bower install, directory clearing, and building into pretest. So test is just the actual testing. npm test will automatically run a pretest script before running the tests so we'll still just be able to npm test the same.

[duggiefresh]

Sweet. Good call on npm pretest.

[rwjblue]

Can you split this up between test and pretest?

"pretest": "bower install && rm -rf dist && broccoli build dist",
"test": "karma start --browsers Firefox --single-run"

[rwjblue]

Closing in favor of #100.