allure-framework / allure-framework/allure3

Implement open-test-reporting reader

Open
#182 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
401
Forks
58
Avg merge
2d 20h
Merged PRs (30d)
34

Description

See https://github.com/junit-team/junit5/issues/4113

> The Open Test Reporting format was introduced to replace the legacy XML format for test results in a way that supports all features of JUnit 5. It's designed to alleviate users from the mental load of having to translate from the logical structure of their test cases to an outdated technical format and vice versa. This task adds the missing pieces to make it truly useful and superior to the old format. This will reduce friction for our users by making it easier to understand test results and find the root cause of test failures and also make triaging bug reports easier for maintainers in the future because they will be able to request a test report which contains all relevant information.

It would be great if Allure could consume open-test-reporting report.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the linked JUnit issue 4113 and the Open Test Reporting requirements described there. Then identify the Allure entry point for consuming test reports; done means Allure can consume an Open Test Reporting report and present its relevant test-result information.

Written by the indexing model from the issue text.

Assessment

Domain
testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.