karma-bro + angular about karma-browserify HOT 3 CLOSED

Just declare your shims in your package. Browserify will only bundle it if you actually require it. You'll also need the depends option:

"browserify": {
  "transform": [
    "browserify-shim"
  ]
},
"browser": {
  "angular": "./bower_components/angular/angular.js",
  "angular-mocks": "./bower_components/angular-mocks/angular-mocks.js"
},
"browserify-shim": {
  "angular": {
    "exports": "angular"
  },
  "angular-mocks": {
    "depends": "angular"
  }
}

For what it's worth though, I've moved entirely to the global config for several reasons. The main one is that I write a lot of reusable angular modules with CommonJS and then use them in Angular projects. If you use the path-based shim config, you have to rely on browserify to dedupe your modules and all modules that depend on Angular must use an identical version. Also you need to have bower installed globally and run bower i as an install script for your reusable modules. It ends up being horribly unmaintainable and buggy.

As of #1 you can just stick angular and angular-mocks in the file array before your test glob and your bundle will be added after angular-mocks.

from karma-browserify.

Hi, thks for your answer.
I ended up leaving the all configuration for browserify in the package.config file.
Then in karma my files section looks like this

...
files: [
    './scripts/**/*.js'
],
...

I like to have my tests files along with the source code instead of a separate tests folder.

Finally my test start like this:

require('angular-mocks');
require('./app');
describe('myService', function () {
    var service = null;

    beforeEach(angular.mock.module('myApp'));

    beforeEach(inject(function ($injector) {
        service = $injector.get('myApp.myService');

    }));

    it('should exist', function () {
        expect(service).toBeDefined();
    });

    it('add should succeed', function () {
        expect(service.add(1, 3)).toBe(4);
    });

    it('sub should succeed', function () {
        expect(service.sub(1, 3)).toBe(-2);
    })
});

because angular-mocks has a dependency on it will also load angular.
This works like a charm.

The only thing (but it's not really an issue) is that i have to do angular.mock.module(...) to load the module in the beforeEach instead of classical module(...)

from karma-browserify.

That's a limitation born from the fact that Angular choose to export multiple things from angular-mocks. That concept isn't compatible with CommonJS where there's only one module.exports. Browserify could do something clever and attach the exports to a base object but that's not really its place.

from karma-browserify.