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

Correctly parse nested go tests #16817

Merged

Commits on Oct 17, 2017

  1. Correctly parse nested go tests

    Use a stateful parser approach to process each section of the test
    output independently. Correctly handles nested tests and nested output
    and puts any stdout/err into the SystemOut field of the generated test
    result.
    
    Note: this breaks --suite=nested, but was not able to find any users.
    smarterclayton committed Oct 17, 2017
    Configuration menu
    Copy the full SHA
    8d7e455 View commit details
    Browse the repository at this point in the history
  2. Split integration test output into two parts

    Allows junitreport to parse output correctly for nested integration
    tests.
    smarterclayton committed Oct 17, 2017
    Configuration menu
    Copy the full SHA
    5c502e3 View commit details
    Browse the repository at this point in the history