Skip to content

Parameterized test final aggregated status after separate result uploads #495

@LeadShadow

Description

@LeadShadow

Hi!

I have a question regarding parameterized test result uploads and aggregation.

Example scenario:
I have a parameterized test with 3 iterations.

First iteration passes → result is uploaded successfully.
Second iteration fails → through API I mark it as broken (for example via tag/status).
Third iteration passes → currently I can add a condition to inherit/check the broken status.

At the end, I would like the whole parameterized test to be shown as failed/broken overall, even though results are uploaded separately for each parameterization.

So the main question is:
is there already any existing functionality/recommended approach for sending some kind of final aggregated result after all parameterized runs are completed, so the parent test case gets the correct final status?

Right now results are uploaded independently per parameterized execution, and I’m trying to understand the best way to represent the final combined state of the whole test.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions