Fix #383. Refactored test suite to use bower_components so we catch thes...

[ssafejava]

...e errors by staying on top of dep updates. Added a test in views.js to catch this particular error explicitly.

QUnit update now throws errors upon improper use of asyncTest/start/stop, so I fixed those errors as well.

Removed test/vendor and test/qunit directory as they are no longer needed.

Added test/spec directory.

[SBoudrias]

BTW global files ignore can/should be added to your own global .gitignore. That helps only keeping project related ignores in the local .gitignore.

[ssafejava]

Good point, will remove & update.

[tbranyen]

Looks like bower needs to be added to devDependencies.

[SBoudrias]

devDependencies or peerDependencies? I wonder as it'll probably won't run if not installed globally.

[tbranyen]

Its only for our needs, devDependencies should work fine. Travis puts everything in your PATH anyways.

[ssafejava]

Yeah, that seems right, bower & grunt both won't run at all even if installed in node_modules, so they should be peerDependencies.

For example, yeoman's package.json

[tbranyen]

What was the reason for moving tests into test/specs?

[ssafejava]

I thought it was clearer. It isn't immediately obvious that setup.js and configure.js are actually test suites, and I think that putting them in the spec folder makes that simpler to understand. Both structures are common in projects I've worked with; if it's a big deal, I can revert.

[tbranyen]

Not a big deal, just calling it out because it's not relevant to the fix in issue 383. I'd like @jugglinmike to comment on this before merging.

[jugglinmike]

I agree that it's better to have the tests themselves in a dedicated directory. It would be nice to see the resolution of #383 in an independent commit, although it sounds like I'm alone on that.

[tbranyen]

Okay cool, merging.

[tbranyen]

Thanks @ssafejava!