Skip to content

Aggregate e2e test results into a single JUnit report #2578

@timflannagan

Description

@timflannagan

Feature Request

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Example: "I have an issue when (...)"

This is a follow-up for the e2e parallelization work that was done through #2520.

Describe the solution you'd like
A clear and concise description of what you want to happen. Add any considered drawbacks.

Now that the overall e2e suite is split across four, parallel instances, the result of running those individual test jobs results in four JUnit reports (on top of any cluster debugging information) being produced, vs. a single JUnit report like the previous behavior. Combining them into a single report will with future work around building CI metrics to help identify flakes, regressions, etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions