fix(reporter): log a more descriptive test URL in the reporter

[timmywil]

• Also update all submodules for tests

[timmywil]

The moduleId replacement and reportId are the things left out of the descriptive URL.

Example for jQuery when running the basic module:

http://localhost:53730/test/?module=basic

[mgol]

Code changes look good, thanks!

I am not able to test it that easily; I'd have to commit a script that swaps jtr for a version from this PR, push to my fork to a branch, change GA settings to have it run on this branch and then look at GA, since this output only appears on BrowserStack runs. I'll skip that, I assume you tested it somehow.

[timmywil]

The tests for this repo already do what you're describing. Have a look at the test run for jQuery Migrate in this repo's GA. The "Tests finished" log is the same regardless of success or failure, and the same reporter is used whether running via BrowserStack or when using Selenium. However, the tests in this repo don't isolate modules. I've already tried this, but for posterity, you can simulate exactly what jQuery core does (via the jtr-isolate.yml config used in the browserstack.yml GH workflow) with the --run option:

git submodule update --init
cd test/jquery
npm install
npm run test:unit -- --run module=basic

Which results in

[mgol]

OK, cool! That's enough for me, merge away. 🙂