'spec/fixtures' is hardcoded about karma-fixture HOT 3 CLOSED

👍

Ugly work around is to set the base property on fixture:

  beforeEach(function() {
    fixture.base = 'test/fixtures';
    var fixtures = fixture.load('test-fixture.json');
...

Gross but it should work until this gets properly resolved.

from karma-fixture.

@kobrigo @mklaber Unfortunately i cannot find any programmatic way to pass config options to the plugin inside the context iframe.

The only way i can think of is a permutation of @mklaber's way.
You add the one of the following to a setup file that is included and always executed before your specs:

window.fixture = new Fixture('your_path_to_your_fixtures')
// or 
window.fixture.base = 'your_path_to_your_fixtures'

Let me know if you have any other suggestions.

from karma-fixture.

I published 0.2.3, where i created a .setBase() method that can be executed once in a top level before().

One other option is to create a spec setup file, and load it before your specs, similarly to the require.js config file. Inside that file you could run fixture.setBase(my/fixtures/base).

I also implemented loading fixtures by passing their full filenames, including their base path, thus overriding the fixture.base value.

I could not find a way to pass configuration from the karma.conf.js file inside the context.html runtime, other that writing a preprocessor plugin, and rewriting the html2js plugin for this purpose seems like overkill. If you find/know any other way please let me know.

from karma-fixture.