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.

Sign up for GitHub

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

Jump to bottom

fix(cli): correctly handle special characters in JUnit failure details #2028

Merged
merged 5 commits into from Jan 20, 2022
Merged

fix(cli): correctly handle special characters in JUnit failure details #2028

merged 5 commits into from Jan 20, 2022

Commits on Jan 19, 2022

  1. fix(cli): correctly handle special characters in JUnit failure details 

    Those details are contained in XML CDATA section and should therefore not be XML-escaped.
    @fgreinacher
    fgreinacher committed Jan 19, 2022
    Copy the full SHA
    ffc1c1e View commit details
    Browse the repository at this point in the history

  2. Merge branch 'develop' into fix/cdata-escape

    @fgreinacher
    fgreinacher committed Jan 19, 2022
    Copy the full SHA
    945e481 View commit details
    Browse the repository at this point in the history

Commits on Jan 20, 2022

  1. Merge branch 'develop' into fix/cdata-escape

    @fgreinacher
    fgreinacher committed Jan 20, 2022
    Copy the full SHA
    6f960d6 View commit details
    Browse the repository at this point in the history

  2. chore(repo): empty commit to trigger CI

    @P0lip
    P0lip committed Jan 20, 2022
    Copy the full SHA
    320d24d View commit details
    Browse the repository at this point in the history

  3. test(cli): update expected output

    @P0lip
    P0lip committed Jan 20, 2022
    Copy the full SHA
    0039aea View commit details
    Browse the repository at this point in the history