Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Missing attribute value for attribute path of element file #23

Closed
laki88 opened this issue Nov 15, 2017 · 7 comments · Fixed by #33
Closed

Error: Missing attribute value for attribute path of element file #23

laki88 opened this issue Nov 15, 2017 · 7 comments · Fixed by #33
Assignees

Comments

@laki88
Copy link

laki88 commented Nov 15, 2017

I got an error in message subject while running "karma start .\karma.conf.js".
When I remove sonarqubeunitreporter, I can run karma file without any error.

@tornaia tornaia self-assigned this Nov 19, 2017
@bogdanconstantinescu
Copy link

I found the issue. In file-util.js, this happens: http://bogdan.d.pr/wlCWlH
So if you have a describe ('my spec') it'll fail because it's looking for the index of 'describe('.

@JakobJingleheimer
Copy link

Also suddenly experiencing this, but I don't have any instances of describe (.

@JakobJingleheimer
Copy link

JakobJingleheimer commented Mar 5, 2018

How the hell does this cause an XML error

describe.only('', function() {
    it('', function() {

    });
});

Remove the it(), and no error. 300+ other specs are fine, and there's nothing special about this file.

@JakobJingleheimer
Copy link

Oh, my god. It breaks because of .only.

@whi-tw
Copy link
Contributor

whi-tw commented Nov 2, 2018

it seems to also break if you have describe( 'whatever rather than describe('whatever. I've fixed this in #33, though.

@Hobart2967
Copy link

reverting to version 0.0.14 solves the issue :>

@mesche
Copy link

mesche commented Aug 12, 2019

Are there any news?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants