search

DarkShield / daDashboard

Dashboard Frontend
0 stars 0 forks source link

Bring in code coverage tool & get to 100% #62

Open mattjay opened 10 years ago

mattjay commented 10 years ago

Need the grunt code coverage tool we use on the proxy in here and to see where we are at.

ProZachJ commented 10 years ago

The Karma side appears to already be using the coverage tool. Just need to configure jasmine-node.

mattjay commented 10 years ago

Nice. Just thought of it because I wrote a new route and checked out our router tests. Seriously lacking coverage there. I guess I was lazy in the past.

ProZachJ commented 10 years ago

actually when I did grunt test:coverage I got a blank report

so needs some work

mattjay commented 10 years ago

tests were broken due to something up with package.json. try my new branch block_API

ProZachJ commented 10 years ago

I'm on it

ProZachJ commented 9 years ago

@mattjay In the last PR I added some grunt configurations.

The best way to use them is to ctrl + click on Gruntfile.js in Webstorm and select "Open Grunt Console". There you can see all the test options. Grunt now automatically sets the proper environment variable based on the test you select. So no more export NODE_ENV

ProZachJ commented 9 years ago

Everytime I sit down to do this I get the urge to do something "more productive" we need to just have a hack day together and get this stuff knocked out.

mattjay commented 9 years ago

grumble grumble Angular tests.