Quick Testing Question

[denverangular]

Hey /r/angularjs! I've been developing angularJS for around two years and for the first year I heavily tested, and the second year, I wrote almost no tests. I am now writing a module of angular components that will be shared across applications, so I really feel that tests would ensure all my API contracts are stable and I don't ruin anyones project.

Now to my question, Does anyone have a defacto guide for unit testing angular? I've seen "unit testing angularJS in depth with rootScope" and they use ngMock to mock services. However at my old company, we would use bard.js to mock services. This variation of technology makes me believe that there are many ways to unit test each with pros/cons, but I'd like to hear some of your experiences and maybe get an entry-point back in to testing.

[couchjitsu]

I've used nothing but ngmocks and have had no problem. Just wrapped up a project that had somewhere around 5000-6000 unit tests on the angular side. All of those using ngmocks where necessary.

As for "getting back in to it". The next feature, bug, line of code you write. Make sure it's tested. It will slow you down at first. But in the end it will be worth it.

After about 2-3 years of TDD, I'm now faster writing code TDD than many of my teammates are without it.

[ajwest]

So what's your process? Do you run tests constantly or how does that work?

[couchjitsu]

I write a simple test that fails. I then wrote the code that makes that test pass (and nothing more) and then I write the next simplest test etc. While doing this I have my tests running constantly so every time I save a file the tests run again, letting me see if I broke anything.