Way to specify external javascript libraries for tests?

[DragonAxe]

For example, I have some JavaScript libraries such as jquery-3.4.1.min.js and google-protobuf.js that need to be available when running J2CL tests in ChromeDriver. How can tell J2clMaven about these files while running unit tests?

I've tried placing them in src/main/resources/public/ where they get copied to the test output directory, but the test's html, js, and bundle files don't reference them.

Thanks in advance!

[niloc132]

Putting something in */public/ or META-INF/resources/ will only ensure that it is copied to your output (prod or test), but not that it is loaded automatically. For example, images, css files, data files wouldn't be somehow loaded into the application, but would be available for your application to load.

For example, you can load your JS files then with something like gwt-core's ScriptInjector, with the added step of looking up the base directory (where both your compiled and copied .js files live). Effectively, this is just creating a new script tag with the specified src path, and giving you a callback for when it loads. You can then delay the rest of your test until that load is finished.

Assuming your .js file is loaded as a script in a browser (rather than a module in a browser, or something in node.js/etc), you could use document.currentScript and look at the src attribute, remove the file name to see the parent path, etc. That would need to be loaded when the script runs, so part of a class's .native.js. For module imports you could examine import.meta. If you want to do the check while the test runs (again in a browser environment) you could loop through document.getElementsByTagName('script') and check their src attributes, etc.