Change Details

## Summary The #confirmedit extension has QUnit tests for hCaptcha specific code that are not run in CI because the hCaptcha sub-extension is not loaded. We should either load the sub-extension or move the tests out of the sub-extension ## Background - The #confirmedit extension has sub-extensions for each type of captcha that can be used -- This is largely no longer necessary as discussed in {T398193}, but there are some remaining issues that makes it difficult to remove the sub-extensions (such as not wanting unnecessary i18n and ResourceLoader modules to be registered when not using that captcha) -- However, the sub-extension approach means that hCaptcha QUnit test modules are not loaded in CI, as only the overall #confirmedit extension is loaded - We should make the QUnit tests run in CI so that we can ensure our changes to front-end JS code for the #hcaptcha-editing-trial do not cause regressions and any breakages block merges. To do this we can either: -- Make it so that all the ConfirmEdit sub-extensions are loaded in CI, so that any tests that are run can be run with all extensions loaded to avoid skipping any tests that should be run -- Remove the sub-extensions from #confirmedit as described in {T398193} ## Acceptance criteria - [ ] The hCaptcha QUnit tests run in CI through any acceptable approach to get there

## Summary The #confirmedit extension has QUnit tests for hCaptcha specific code that are not run in CI because the hCaptcha sub-extension is not loaded. We should either load the sub-extension or move the tests out of the sub-extension ## Background - The #confirmedit extension has sub-extensions for each type of captcha that can be used -- This is largely no longer necessary as discussed in {T398193}, but there are some remaining issues that makes it difficult to remove the sub-extensions (such as not wanting unnecessary i18n and ResourceLoader modules to be registered when not using that captcha) -- However, the sub-extension approach means that hCaptcha QUnit test modules are not loaded in CI, as only the overall #confirmedit extension is loaded - We should make the QUnit tests run in CI so that we can ensure our changes to front-end JS code for the #hcaptcha-editing-trial do not cause regressions and any breakages block merges. To do this we can either: -- Make it so that all the ConfirmEdit sub-extensions are loaded in CI, so that any tests that are run can be run with all extensions loaded to avoid skipping any tests that should be run -- Remove the sub-extensions from #confirmedit as described in {T398193} ## Acceptance criteria - [x] The hCaptcha QUnit tests run in CI through any acceptable approach to get there

## Summary The #confirmedit extension has QUnit tests for hCaptcha specific code that are not run in CI because the hCaptcha sub-extension is not loaded. We should either load the sub-extension or move the tests out of the sub-extension ## Background - The #confirmedit extension has sub-extensions for each type of captcha that can be used -- This is largely no longer necessary as discussed in {T398193}, but there are some remaining issues that makes it difficult to remove the sub-extensions (such as not wanting unnecessary i18n and ResourceLoader modules to be registered when not using that captcha) -- However, the sub-extension approach means that hCaptcha QUnit test modules are not loaded in CI, as only the overall #confirmedit extension is loaded - We should make the QUnit tests run in CI so that we can ensure our changes to front-end JS code for the #hcaptcha-editing-trial do not cause regressions and any breakages block merges. To do this we can either: -- Make it so that all the ConfirmEdit sub-extensions are loaded in CI, so that any tests that are run can be run with all extensions loaded to avoid skipping any tests that should be run -- Remove the sub-extensions from #confirmedit as described in {T398193} ## Acceptance criteria - [ - [x] The hCaptcha QUnit tests run in CI through any acceptable approach to get there