QA Guidance

1. All Content Viewers

What to test: Every content type renderer (HTML5, H5P, BloomPUB, video, audio, PDF, ePub, Perseus, slideshow, QTI)

What to look for: JavaScript errors, broken interactions, content failing to load, performance differences

Why: Webpack bundling changes re-enabled Terser mangling and changed how core-js polyfills are loaded in the sandbox. These affect all compiled JavaScript.

• 6a4c0c4621 - Webpack bundle size optimizations (mangling re-enabled)
• de9ac92470 - Fix core-js duplication in viewer bundles
• 54eb476011 - H5P JavaScript library update

2. Application Startup & Navigation

What to test: Initial page load, navigation menu population

What to look for: Delayed or missing navigation items, flash of untranslated content, race conditions on slow connections

Why: i18n setup is now async with lazy-loaded locale data. Navigation component registration is deferred until i18n completes. This changes the timing of when the app becomes fully interactive.

• 2eb1fbab96 - Lazy load all intl and vue-intl locale files, defer nav component registration

3. Internationalization Across the App

What to test: Non-English languages, RTL languages, language switching

What to look for: Missing translations, layout breaks in RTL, errors when switching languages

Why: The entire i18n initialization flow was refactored from synchronous to asynchronous. Any code that assumed translations were immediately available could break.

• 2eb1fbab96 - Lazy load all intl and vue-intl locale files

4. Channel Import

What to test: Import channels from various sources

What to look for: Import failures, missing metadata post-import

Why: Channel import now includes modality annotation step. The annotation uses options__contains JSON string matching.

• 3458d8fcf2 - Annotate modality field on upgrade and channel import flows