Skip to content
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.

script errors mess up the output of the xml reporter #265

Closed
cromega opened this issue Aug 16, 2012 · 4 comments
Closed

script errors mess up the output of the xml reporter #265

cromega opened this issue Aug 16, 2012 · 4 comments
Assignees
Labels
Milestone

Comments

@cromega
Copy link

cromega commented Aug 16, 2012

when something causes a yellow error, it ends up in wrong parts of the ouput. its true for the dots reporter as well, the yellow lines should be written somewhere after the failing test name, not among the dots.
but its especially critical with the xml reporter where those lines break the xml structure:

...
</testsuite>
�[1m�[33mUncaught exception: Unable to get property 'name' of undefined or null reference�[0m
�[1m�[33mUncaught exception: ./stuff.js:168 Uncaught TypeError: Cannot read property 'name' of undefined�[0m
<testsuite errors="0" tests="20" time="0.003" failures="0" name="Firefox 13.0.1, Windows 7">
...

also, the error lines shouldn't be truncated

@cjohansen
Copy link
Member

The errors should show up as error elements. Will figure out why that's not the case.

@ghost ghost assigned cjohansen Aug 16, 2012
@cromega
Copy link
Author

cromega commented Sep 14, 2012

ignore errors in the reporters that bubble up out of scope

@ghost ghost assigned dkl-ppi Jan 18, 2014
@GCheung55
Copy link
Contributor

May be dupe of #439.

@dkl-ppi
Copy link
Member

dkl-ppi commented Jul 14, 2015

This issue is now handled in #439.

@dkl-ppi dkl-ppi closed this as completed Jul 14, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants