Set the base path for this plugin to calculate routes to helpers in the .grunt/ folder? about grunt-contrib-jasmine HOT 12 CLOSED

I haven't actually used live-reload. Does it serve with the live-reload folder as its root? The Specrunner should be able to be put anywhere as long as it has access to .grunt in the root.

I could make the tmpdir configurable if necessary.

from grunt-contrib-jasmine.

Yeoman sets live-reload to serve out of .tmp by default. We changed it to .devServer. It won't work served out of root I think--too many source files at play.

It's important to have specrunner in a specific location.

Having the spec runner as a sibling of the index.html allows the requirejs path configuration to stay the same. Ideally, require config is the same between dev, test, and dist--this way there's limited chance of introducing bugs as a result of differences, and there's less config to maintain.

A configuration that allows specRunner to live in any location (with working paths) would be ideal.

from grunt-contrib-jasmine.

This would be nice to have.

from grunt-contrib-jasmine.

This has actually been fixed in new version ;)

from grunt-contrib-jasmine.

@inossidabile, I'm having a similar issue. Which version allows the SpecRunner to sit in any location? Does that mean it also allows the temp (.grunt) folder to sit elsewhere, such as the server's static folder?

from grunt-contrib-jasmine.

@geekytime I don't use it anymore. But I'm quite sure the latest one should work. Try master as well.

from grunt-contrib-jasmine.

The url problems can run pretty deep for someone trying to use an existing server configuration. In our case, our server expects static content to be served from /static/, butgrunt-contrib-jasmineandgrunt-template-jasmine-requirejs` both do a lot of path-correction relative to the project root, or relative to the outfile in terms of it's position relative to the project root.

I can use whatever path-corrections I want for the files by implementing my own template, but I'd still need a way to tell it how to load my _SpecRunner.html from a path that isn't relative to the project root at browser-time.

from grunt-contrib-jasmine.

@geekytime I don't use it anymore.

Do you mind if I ask what you are using? 😁

from grunt-contrib-jasmine.

@geekytime I made a step away to more generic solutions like Karma. To be explicit I use testem and corresponding Grunt plugin

from grunt-contrib-jasmine.

+1

from grunt-contrib-jasmine.

@geekytime it doesn't look like .grunt gets put in the same place as the generated _SpecRunner.html.

from grunt-contrib-jasmine.

This issue seems quite similar to #170, in which I asked if it might be possible to choose where to put the contents of the current .grunt/ directory (I've got the SpecRunner in test/, which is hosted via GitHub Pages, and it'd be great -- much neater -- to be able to put Jasmine's code in test/ as well).

from grunt-contrib-jasmine.