Testing and QA

Have you guys seen our .jshintrc? I thought there was a note about jshint in our coding style but seems not. Note that modules (amd or yui) built with grunt will be linted with jshint (though unfortunately the one which YUI uses is slightly older).

I have not looked at the javascript coding style checker but if it provides useful value over jshint - I think its possible we could incorporate that into our js build process (assuming there would be possible ways to silence the checker when there really isn't a solution to a particular style check).

Edit: Doh, just seen Damyons response.

Hi David,

I didn't realise there was an open bug in the tracker about this topic.

I will look at your snippet in depth throughout this week, but at first sight I see some rules I didn't realise that were configurable (especially the jsDoc documentation part).

Best regards,

Julen

Hi Damyon,

I discovered this tool reading JSHint documentation, which suggests to use JSCS "if you would like to enforce rules relating to code style" (e.g. to enforce camelcase notation)

Best regards,

Julen

jscs is more about where spaces and brackets go and enforcing formatting.

jshint is more a static analysis tools that might reveal when you're doing something you shouldn't in your code (using the wrong kind of comparison).

There is a little bit of overlap, but there's functionality in jshint that overlapped that they removed and explicitly point you towards jscs in their documentation.

edit: heh, should really read the whole thread before I reply, just repeating what's already been said.