-
Notifications
You must be signed in to change notification settings - Fork 22
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
is there a way to create aggregated report ? #20
Comments
Hi @mahesh-nihr, I was waiting for specific need to gather requirements for this feature and contribution from the user to come up with joined requirements. In my team we had need to aggregate results but we wanted to deduplicate raw axe violation and use deduplicated violations (not other parts) to create one html file. Currently, I approach this flow in following way (testCafe example):
I assumed that this flow may not work for everyone and complicated, so I haven't published axe violation deduplication lib. I would really appreciate your input on possible implementations of your request.
Option 2: create new function(same name, e.g createAggregatedHtmlReport) that will read individual html files from specific directory, read all options from them. Function call can look like this:
Option 3: publish in npm my violations deduplication library that accepts array of violations from different runs and create one array where violations are joined by violation id. My personal preference is Option 2 because you can run it without relying on raw results to be available during it's run time. |
Hi @lpelypenko - i am also working on an aggregate report. what i have done is as follows :
I would like to know if your library for deduplication is available publicly. P.s - really amazing work on this reporter. it is really wonderful that an extensive, readable report is generated. |
Hi thanks for awesome package. I am able to create reports for individual pages but just wondering is there a way to create aggregated report for results from multiple pages ?
Thanks
The text was updated successfully, but these errors were encountered: