[X] I have tested the issue with the latest version of the product
Issue Description
Expectation
Provide the testName and a field like foundBy (but named more appropriately) in the top level data of the JSON export of the extension.
Actual
In the JSON export of the extension testName and foundBy is included in the JSON for each issue. However, in the happy situation where there are no issues the name of the test run as well as the mailadres of the tester is nowhere available in the export.
How to Reproduce
Run the test on a page where 0 issues will be found. Export the test to JSON.
Additional context
I'm trying to build a dashboard for all the tests. The test name is a perfect candidate for a readable name for the URL. And noting who ran the test, also when 0 issues were found, would also be very valuable as a way to contact the person who decided to mark something as an issue or not.
The information is clearly available, but it seems to me that not including it in the top section of data (with the "url", "extensionVersion", "axeVersion", etc.) was an oversight.
@joppekroon Thank you for raising this issue. I've created a ticket for it in our product backlog (axe Extension). We will prioritize and resolve it in one of our upcoming releases.
Product
axe Extension
Product Version
v4.81.4
Latest Version
Issue Description
Expectation
Provide the
testName
and a field likefoundBy
(but named more appropriately) in the top level data of the JSON export of the extension.Actual
In the JSON export of the extension
testName
andfoundBy
is included in the JSON for each issue. However, in the happy situation where there are no issues the name of the test run as well as the mailadres of the tester is nowhere available in the export.How to Reproduce
Run the test on a page where 0 issues will be found. Export the test to JSON.
Additional context
I'm trying to build a dashboard for all the tests. The test name is a perfect candidate for a readable name for the URL. And noting who ran the test, also when 0 issues were found, would also be very valuable as a way to contact the person who decided to mark something as an issue or not.
The information is clearly available, but it seems to me that not including it in the top section of data (with the "url", "extensionVersion", "axeVersion", etc.) was an oversight.