asciidisco / grunt-qunit-istanbul

Run QUnit unit tests in a headless PhantomJS instance & generate some nice code coverage metrics using Istanbul.
MIT License
33 stars 21 forks source link

Drive letters on Windows should not be case-sensitive #29

Open sgarcialaguna opened 10 years ago

sgarcialaguna commented 10 years ago

This took me a couple hours to figure out.

Wanted to include grunt-qunit-istanbul in a Jenkins project - the test ran fine, but the coverage report was empty. Running 'grunt qunit' manually worked fine. Eventually I found that Jenkins used 'd:\Jenkins\' as a workspace path and I used that path in my call to grunt. Changing it to 'D:\Jenkins\' fixed the issue.

asciidisco commented 10 years ago

Weird issue. I don't have the time to get my hands on a fix, do you mind sending in a PR?

asciidisco commented 9 years ago

@sgarcialaguna Any news on this? Have you had the time to fix the code & if so, could you provide it?

sgarcialaguna commented 9 years ago

Sorry, I had completely forgotten about this. I'll try to look into this in the next couple days / over the weekend.

I won't promise anything, though, since I don't really know anything about grunt plugins besides how to use them.

sgarcialaguna commented 9 years ago

https://github.com/sgarcialaguna/grunt-qunit-istanbul-project/blob/master/Gruntfile.js shows the problem:

        qunit: {
            all: ['tests/*.html'],
            options: {
                coverage: {
                    src: ['src/*.js'], // This works, a complete coverage report is generated
                    //src: ['SRC/*.js'], // This doesn't work, but to Windows, the paths are equivalent
                    instrumentedFiles: './temp/',
                    htmlReport: 'report/coverage',
                    coberturaReport: 'report/'
                }
            }
        },