Skip to content
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.

Allure report failing due to invalid XML character #155

Open
jtaylordigital opened this issue Apr 2, 2019 · 0 comments
Open

Allure report failing due to invalid XML character #155

jtaylordigital opened this issue Apr 2, 2019 · 0 comments

Comments

@jtaylordigital
Copy link

Hi. I'm trying to implement the Allure reporter into our project, but I'm encountering an issue where the reporter errors out and stops running tests when an assertion in a test fails validation. If the assertions pass, the allure report files are generated as expected.
When an assertion fails validation, the following error is generated and the test run stops:
Error: charData should not contain characters not allowed in XML

We're using jest-matchers as our assertion library, and the assertion that generates this error is in this format:
expect(sometext).toBe(sometext);

If I run the test with just the spec reporter, the assertion returns a validation message that looks like this:

Expected value to be (using ===):
  "sometext"
Received:
  "notsometext"

Is there a way to resolve this error so that Allure will properly generate the report files even when these assertions fail?

We're using:
"wdio-allure-reporter": "0.8.3"
"jest-matchers": "20.0.3"
"webdriverio": "4.12.0"

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

No branches or pull requests

1 participant