debug in browser using testacular (now karma)

angularjs karma-runner
Lucas picture Lucas · Apr 9, 2013 · Viewed 29.7k times · Source

I am trying to figure out the best way to debug my unit tests when I break them. Typically in previous test environments I could just run the tests in the browser and breakpoint the test, or the code and see why my test was failing. I can't seem to figure out how to do that with testacular. Is there an easy way to debug unit tests?

Answer

Tomas Romero picture Tomas Romero · May 24, 2013

  1. In karma.conf.js:

    browsers = ['Chrome'];

  2. In your failing spec:

    it('spec', function() {
    debugger; // This is like setting a breakpoint
    // ...
});
  3. Run Karma.
  4. Go to the newly opened Chrome Browser, open the console and refresh the page.

Now in Chrome's Developer Tools source tab you should see the execution stopped at the debugger.

Related questions

Angular 1.6.0: "Possibly unhandled rejection" error

We have a pattern for resolving promises in our Angular app that has served us well up until Angular 1.6.0: resource.get().$promise .then(function (response) { // do something with the response }, function (error) { // pass the error the the error service return …

Read More
Mocking AngularJS module dependencies in Jasmine unit tests

I'm attempting to unit test controller code inside a module that takes other modules as dependencies, but haven't been able to figure out how to mock them properly. I'm using the Jasmine Framework and running my tests with Karma (Testacular). …

Read More
Testing service in Angular returns module is not defined

I am trying to run the default service unit test in my project (Taken from the Angular Seed project on GitHub), but I keep getting the error "module is not defined". I have read that it could be something to …

Read More