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

Issues getId return null value for gradle project #34

Open
ankur1233 opened this issue Jun 9, 2024 · 3 comments
Open

Issues getId return null value for gradle project #34

ankur1233 opened this issue Jun 9, 2024 · 3 comments

Comments

@ankur1233
Copy link

ankur1233 commented Jun 9, 2024

I have setup gradle project and getting Issues.getId() same project run with maven setup it work fine

invoke "io.github.sridharbandi.modal.axe.Issues.getId()" because "issues" is null
java.lang.NullPointerException: Cannot invoke "io.github.sridharbandi.modal.axe.Issues.getId()" because "issues" is null
at io.github.sridharbandi.IRunner.lambda$generateHtmlReport$0(IRunner.java:25)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
at io.github.sridharbandi.IRunner.generateHtmlReport(IRunner.java:24)
at io.github.sridharbandi.AxeRunner.generateHtmlReport(AxeRunner.java:53)

@sridharbandi
Copy link
Owner

@ankur1233 Can I know the website you are using, I will check it from my side.

@ankur1233
Copy link
Author

yah sure it's : https://www.hilti.fr/

@anonymous73612
Copy link

anonymous73612 commented Aug 1, 2024

Hello @sridharbandi, we are getting this error ava.io.FileNotFoundException: ./target/java-a11y/axe/json/f9a05f92-9a3a-4486-a7b5-60ed4db7918d.json (No such file or directory) and that's the reason we are getting null pointer on Issues.getId().

But the interesting part is that the json file is correctly generated at this path testauto/target/java-a11y/axe/json/0c4844d2-e5fb-4be7-9fdf-a196f005547c.json but throws an error while reading the json

I see that the json is generated after the test is completed inside the target folder and while it tries to find the json during the test execution it fails as there is no json, could you please check this issue on priority as it's impacting our testing?
Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants