allure-framework / allure-framework/allure2
Reporting and trends by release and environment
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
We need to trace each test suite cycle execution with the test environment (development, qa, ...) and the release of the product.
Currently, if I am not wrong, you can only have one environment properties file/configuration for all tests executions, and the historical trends is based on the date of execution.
We would like to add reporting capabilities:
- Test cycles. We can define a test cycle execution (with configuration like environment, release that we're testing, ...)
- Test status. We can see the execution by test cycle, and trend is based on the test cycle or with comparison with other test cycles.
Best regards.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the current environment configuration and the code that builds historical trends, then determine how test cycles would associate environment and release metadata. Done means reports can group executions by cycle and compare trends across cycles.
Written by the indexing model from the issue text.
Assessment
- Domain
- analytics, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100