Create folders recursively for custom output{Dir|File} about karma-junit-reporter

[killercentury]

Found the same issue

[lukasz-karolewski]

+1
same here

[dignifiedquire]

@kether667 can you confirm that #49 fixes the issue?

[lukasz-karolewski]

just tested, i confirm that #49 fixes #48

[dignifiedquire]

Should be fixed in 0.3.3

[merlosy]

Hi all,

It seems I still have the issue:

PhantomJS 1.9.8 (Linux 0.0.0): Executed 21 of 23 (skipped 2) SUCCESS (0.047 secs / 0.099 secs)
�[33m25 08 2015 11:33:46.243:WARN [reporter.junit]: �[39mCannot write JUnit xml
    ENOENT, open '/test/results/PhantomJS_1.9.8_(Linux_0.0.0)/test-results-jenkins.xml'

I'm using:

• node v0.12.7
• grunt-cli v0.1.13
• grunt v0.4.5
• bower v1.4.1
• karma-junit-reporter v0.3.3

Regarding my karma definition:

junitReporter: {
      outputDir: '/test/results/',
      outputFile: 'test-results-jenkins.xml'
},

I'm trying to build it with Jenkins.. If I have a look in my jenkins workspace, the 'result' folder is not created. Do I have to sudo the build process?

Any other ideas?

[watchwithmike]

Similar to @merlosy I'm still seeing this problem in 0.3.6

PhantomJS 1.9.8 (Mac OS X 0.0.0): Executed 250 of 250 SUCCESS (7.251 secs / 0.693 secs)
30 09 2015 21:01:52.134:WARN [reporter.junit]: Cannot write JUnit xml
    ENOENT, open '/Users/mike/git/project-name/build/test/PhantomJS_1.9.8_(Mac_OS_X_0.0.0)/test-results.xml'

When I role back to 0.2.2 and just use the outputFile parameter I get the expected results.

[adriaanthomas]

The ENOENT error looks like #67. The problem is that the browser-specific directory was not created.

[watchwithmike]

@adriaanthomas Thank you, I agree that looks like the same problem. I'll await the next release.

[dignifiedquire]

Release was cut this morning