feat(empty-table-header): new rule to flag empty table headers

[jlin95]

<< Describe the changes >>
New rule created for #2604

For initial review only!

Closes issue:

[straker]

Thanks for putting this together. It's a great start and just needs a few things.

[straker]

Thanks for the updates. Just a few more changes.

[jlin95]

Out of curiosity, have been getting
while trying to run the axe.js build locally.

I didn't make any changes to the Gruntfile/etc, just synced my fork with the develop branch...

[straker]

Out of curiosity, have been getting
while trying to run the axe.js build locally.

I didn't make any changes to the Gruntfile/etc, just synced my fork with the develop branch...

The develop script just constantly watches for changes to axe files and rebuilds the app or runs the tests. Looks like it's working but are you seeing something different?

[jlin95]

Out of curiosity, have been getting
while trying to run the axe.js build locally.
I didn't make any changes to the Gruntfile/etc, just synced my fork with the develop branch...

The develop script just constantly watches for changes to axe files and rebuilds the app or runs the tests. Looks like it's working but are you seeing something different?

Yep, basically previously I would navigate to localhost:9876/test/integrations and run all the tests at one shot from the browser, but now it seems that each rule/etc will execute the tests individually instead of all at one shot, please correct me if I understood it wrongly!

[straker]

Oh yes, I believe that was before we switched to karma for our testing framework. Develop now just watches and re-runs the specific test file associated with the script. To run the full tests you do npm test or there is an entire script setup to run individual directory tests (e.g. npm run test:unit:core to run core tests).

Resolved

[WilcoFiers]

Looks good. Thank you for the contribution!

[WilcoFiers]

Reviewed for security.