Add test to make sure we don't miss any console.logs in tests

[kokarn]

No description provided.

[jwilsson]

I'm not sure I follow, the console.logs in 0756cba were just stray ones which I forgot to remove.

Are you thinking of some sort of JSHint/JSCS check for console.logs in tests?

[kokarn]

Yeah, that should work.
As long as it stops them from showing up in the commited code where they shouldn't be :)

[CITguy]

For a project I work on, we use a script to be run on the git pre-commit hook, so that it won't allow you to commit if there are debugging statements still present in the code. The hook installs itself via an NPM postinstall. Here's a gist that might be useful: https://gist.github.com/CITguy/1138a1701b9ffbf4e091

[jwilsson]

@CITguy looks pretty nice, thanks for sharing!

I'll see if I can work something out.

[jwilsson]

We talked about using Gulp and running all our tests and linting through it, and I figured we can check for stray console.log()s there as well (that way it'll be automatically run together with npm test).

We just need to make sure it doesn't abort the tests while developing something. I'll work something out tonight.

[shellscape]

👍