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

[v.3.0.0-beta.7][allure-jest][allure-js-commons] The error text in the test step is logged with extra characters #1076

Closed
lifanov-rza opened this issue Jul 26, 2024 · 2 comments · Fixed by #1085
Assignees
Labels
theme:jest Jest related issue

Comments

@lifanov-rza
Copy link

lifanov-rza commented Jul 26, 2024

Describe the bug
The error text in the test step is logged with extra characters. I suspect that the problem is in the meta information about the text color

To Reproduce
Steps to reproduce the behavior:

  1. Create test using JEST with steps containing substeps
  2. run test with failure
  3. open allure report
�[2mexpect(�[22m�[31mreceived�[39m�[2m).�[22mtoStrictEqual�[2m(�[22m�[32mexpected�[39m�[2m) // deep equality�[22m

Expected: �[32m1�[39m
Received: �[31m2�[39m

Expected behavior
error text without meta information

Screenshots
image

@baev
Copy link
Member

baev commented Jul 26, 2024

@lifanov-rza please specify the test framework you're using.

@lifanov-rza lifanov-rza changed the title [v.3.0.0-beta.7][allure-js-commons] The error text in the test step is logged with extra characters [v.3.0.0-beta.7][allure-jest][allure-js-commons] The error text in the test step is logged with extra characters Jul 29, 2024
@lifanov-rza
Copy link
Author

@lifanov-rza please specify the test framework you're using.

done

@baev baev added the theme:jest Jest related issue label Jul 29, 2024
@baev baev closed this as completed in #1085 Aug 1, 2024
@baev baev closed this as completed in 4b5fbd8 Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme:jest Jest related issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants