-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
XUnit also for client side tests #40
Comments
+1 |
Yeah - plus one. I get this error: when calling via
|
This should be fixed in version You then should also set In case it doesn't work, please make sure that this and the package |
Client-side tests don't seem to report properly for me. I can see the file on CircleCI being generated, and its content appears to be ok, but circleCI complains: Would you have an idea what could be wrong with the file? EDIT: It seems that the client test report is simply reading everything off the command line and dumping it into the xml file, so if there are any other logs than test results, the xml file will be invalid. Is there a way to filter for xml lines only maybe? |
Well, the truth is, that all the test-results on the client are just written out to the console, which can be grabbed on the server-side. If you want to dig into it, this is the repository used for getting in contact with the browsers in an abstract way: https://github.com/meteortesting/meteor-browser-tests I see your problem here, but don't know how to fix it. Mainly because I can't differ between a result from a reporter and a usual |
Could we maybe clean up the xml file at the end? It's a bit hacky, but removing any "non-xml" content from the file could already be a coarse filter. I think it might be safe to say very few people would ever console.log xml-valid content. EDIT: xUnit xml seems to have a very simple syntax: https://xunit.github.io/docs/format-xml-v2 EDIT2: It looks like what you get from the console isn't even XML, it's formatted text. I'd be surprised if any xml parser can actually read it? |
Could do that ... I'd prefer a separate issue for this, since the main purpose of this ticket is solved and this (to me) is a separate ticket. If we would cut out some of the data returned by calling |
Unfortunately CLIENT_TEST_REPORTER=xunit does not work. Only server side test are exported into xunit xml file.
The text was updated successfully, but these errors were encountered: