fix(awesome): show the selected environment's launch interval in the report header (fixes #852) - #854
Open
d-braun wants to merge 5 commits into
Conversation
d-braun
force-pushed
the
fix-report-header-date-per-environment-(#852)
branch
from
August 21, 2026 12:40
ab78a77 to
739d3a1
Compare
epszaw
approved these changes
Aug 25, 2026
Member
|
@d-braun some tests are broken. Please fix them before we merge the PR |
|
|
d-braun
force-pushed
the
fix-report-header-date-per-environment-(#852)
branch
3 times, most recently
from
September 2, 2026 08:36
589d2db to
92465c9
Compare
…report header (allure-framework#852) The report header rendered the report-wide run summary, which spans the earliest start and the latest stop across all environments. With several environments the header therefore showed the oldest date and a duration of days, regardless of the environment picked, and it never changed on switch. Compute a run summary per environment from the existing trsByEnvId map and embed it as runSummaryByEnv in the report options, so the header can pick the interval of the selected environment. "All" keeps the report-wide summary; an environment without usable timings still falls back to createdAt.
…rmance and prevent timeout issues when running the full monorepo test suite.
d-braun
force-pushed
the
fix-report-header-date-per-environment-(#852)
branch
from
September 2, 2026 12:28
92465c9 to
c3e5e3b
Compare
Contributor
Author
|
@epszaw Tests should be fixed. :) The Allure Report Official step fails on fork PRs because pull_request runs from a fork always get a read-only GITHUB_TOKEN (the checks: write permission in the workflow can't grant it). |
…e-per-environment-(allure-framework#852) # Conflicts: # packages/plugin-awesome/src/generators.ts # packages/plugin-awesome/src/plugin.ts # packages/web-awesome/src/components/ReportHeader/index.tsx # packages/web-awesome/types.d.ts
…re-framework#852) # Conflicts: # packages/web-awesome/test/stores/treeSort.test.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Fixes #852.
In a report with several environments, the header always showed the earliest test start
across all environments, with a duration spanning the earliest start to the latest stop.
The value did not match the environment selected in the picker and never changed on switch,
because
runSummaryis computed once over all test results and read from the staticreportOptions.This computes a run summary per environment from the
trsByEnvIdmap thatAwesomePlugin#generatealready builds (same placeenvStatisticsis filled) and embeds itas
runSummaryByEnvin the report options.ReportHeaderreadscurrentEnvironmentandpicks the matching interval.
Behaviour with two environments (foo: 2026-01-15, 1 min / bar: 2026-08-05, 5 s):
January 15, 2026 at 9:00:00 AM (202d 6h)January 15, 2026 at 9:00:00 AM (202d 6h)January 15, 2026 at 9:00:00 AM (1m 0s)January 15, 2026 at 9:00:00 AM (202d 6h)August 5, 2026 at 4:00:00 PM (5s 0ms)"All" keeps the report-wide summary, and an environment without usable timings still falls
back to
createdAt. The data lives inreportOptionsrather than a separate widget file, sothe header updates immediately on environment switch without an extra fetch or loading state.
The regression came in with 683d234 (#673), which replaced the rendered
createdAtwithrunSummary.start+formatDuration(runSummary.duration).Checklist