Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asses whether saving allure-history as a means for build historical data is useful #9756

Open
dianabarsan opened this issue Jan 24, 2025 · 0 comments
Labels
Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice

Comments

@dianabarsan
Copy link
Member

Describe the issue
We download and store allure history with every e2e test. The reports are available on https://docs.communityhealthtoolkit.org/build-history/

Describe the improvement you'd like
As far as I can tell, the reports don't actually show history, they show the latest run. And even if a test has failed recently, but not in the last suite, it will come up as having 100% success rate.

An example:
This failure: https://github.com/medic/cht-core/actions/runs/12483808060/job/34840612337
Appears in the the trend:

Image

But is reported as 100% success:

Image

This is confusing and unhelpful.

Describe alternatives you've considered
Options:

  1. Figure out if there is a way to access historical builds in allure.
  2. Persist build history in a different way that is accessible.
@dianabarsan dianabarsan added Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice
Projects
None yet
Development

No branches or pull requests

1 participant