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.

Sign up for GitHub

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

Jump to bottom

utilities Results / AxeResults QOL update to include runOnly object after deserialisation #290

Open
Zidious opened this issue Dec 20, 2022 · 0 comments
Open

utilities Results / AxeResults QOL update to include runOnly object after deserialisation #290

Zidious opened this issue Dec 20, 2022 · 0 comments
Labels
playwright playwright integration selenium Selenium integration tech debt web-apis

Comments

@Zidious
Copy link
Contributor

Zidious commented Dec 20, 2022 •
edited
Loading

To better match axe-core's end results we should add (as a QOL feature) when a user does the following:

AxeBuilder axeBuilder = new AxeBuilder(); 
axeBuilder.withRules("label"); 
// ...

In the end results object does not tell the user within toolOptions if runOnly was set and with what rules (example above).

We should map runOnly within toolOptions , within ToolOptions.java class

Mapping should be similar:
image
@Zidious Zidious added tech debt playwright playwright integration selenium Selenium integration labels Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
playwright playwright integration selenium Selenium integration tech debt web-apis
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Zidious @dequejenn