CI should be changed to run the tests, not only to ensure that this is fixed but to not regress again.

For follow ups better use a different branch name, vue3 is misleading.

CI issue is different; this PR resolves the issue that was stopping the execution of tests locally (atleast)

So you cant run the test locally?
what error messages do you get?
I can run them, although the Firefox one always fails for me.

I am using npm run test to invoke ava and it is giving following error to me

This PR fixes it; afterwards the output is something like this:

Can you try ./gradlew check zapRunTests

Yeah its working fine. Isn't it utilizing Java tests? Why can't we run ava directly?

This PR fixes it; afterwards the output is something like this:

That error shows utils is not defined so the fix is not complete.

The fix is just for the import statement; not for the whole unit tests file.

Second, I can see the gradle job is running java tests, and not ava ones. Should I focus on Java unit tests or on JS ones?

For me the java tests are the most important, but the js ones would be good to fix too..

This PR fixes it; afterwards the output is something like this:

That error shows utils is not defined so the fix is not complete.

It is complete now

Task :npmLintAllHud FAILED - should be an easy one to fix 😁

Is it possible to execute only the failing unit test and not zapRunTests each time?

Before d7019fb module was throwing error in browser resulting in failed initialization of HUD.

Now, if you run npm run test it shows two failed tests which means our unit tests (JS ones) are executing perfectly. Also HUD is loading perfectly fine in browser (tested on both Chrome & Firefox)

UPDATE
The failing unit tests have also been fixed:

Checkmarx One – Scan Summary & Details – cf2bb209-bacd-4fcf-9239-d9c1c8ab4c38

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	CVE-2023-28154	Npm-webpack-5.72.0	Vulnerable Package
	CVE-2024-53990	Maven-org.asynchttpclient:async-http-client-2.12.3	Vulnerable Package
	CVE-2021-33813	Maven-org.jdom:jdom-1.1.3	Vulnerable Package
	CVE-2022-25858	Npm-terser-5.12.1	Vulnerable Package
	CVE-2022-38900	Npm-decode-uri-component-0.2.0	Vulnerable Package
	CVE-2023-2976	Maven-com.google.guava:guava-31.1-jre	Vulnerable Package
	CVE-2023-45133	Npm-@babel/traverse-7.12.12	Vulnerable Package
	CVE-2023-46234	Npm-browserify-sign-4.2.1	Vulnerable Package
	CVE-2024-47554	Maven-commons-io:commons-io-2.13.0	Vulnerable Package
	CVE-2023-44270	Npm-postcss-8.4.29	Vulnerable Package
	CVE-2024-29025	Maven-io.netty:netty-codec-http-4.1.92.Final	Vulnerable Package
	CVE-2024-55565	Npm-nanoid-3.3.6	Vulnerable Package
	CVE-2020-8908	Maven-com.google.guava:guava-31.1-jre	Vulnerable Package

Fixed Issues

Severity	Issue	Source File / Package
	Cx89601373-08db	Npm-debug-2.6.9
	CVE-2022-24823	Maven-io.netty:netty-common-4.1.73.Final
	CVE-2022-41915	Maven-io.netty:netty-codec-4.1.73.Final

The PR is ready for review; the building failing doesn't make sense to me as ZAP HUD is working fine locally.