[GSoC 2026] M 2.11 - Fix part of #24933: Acceptance tests for multi-entity translation

[Rohan-Unbeg]

Overview

1. This PR fixes part of [Feature Request]: Use new translation opportunity structure for all user-generated content in curated curriculum oppia/oppia#24933.
2. This PR does the following:
   • Adds specs/translation-submitter/feature-translation-opps-with-new-opps-model/translate-metadata-and-skill-in-target-language.spec.ts, covering the Content Type filter (its three options, and All, Lessons and Skills each filtering the list), its absence on the tabs that cannot use it, translating a lesson's title and objective including the 36 character title limit, translating a skill's description and explanation, and the resulting entries in "My Contributions".
   • Adds specs/translation-reviewer/feature-translation-opps-with-new-opps-model/review-metadata-and-skill-translations.spec.ts, covering the "Translations" action button on a review tab opportunity card, the Skills filter listing suggestions without an opportunity card to click through first, accepting and rejecting a skill translation and their toasts, opening a skill through its card from the mixed list, and reviewing a metadata translation.
   • Adds specs/logged-out-user/feature-translation-opps-with-new-opps-model/view-translated-lesson-metadata-and-concept-cards.spec.ts, covering the translated title and objective on a community library tile, the translated title in the lesson information card, the translated explanation on a concept card inside a lesson, and the fallback to English for a language with no accepted translation.
   • Adds CONTENT_TYPE_FILTER and the Content Type filter helpers selectContentTypeFilter, expectContentTypeFilterOptionsToBe, expectContentTypeFilterToBeVisible and expectSelectedContentTypeFilterToBe to utilities/user/contributor.ts, which is the shared home for dashboard helpers because the filter appears on both the "Translate Text" and "Review Translations" tabs.
   • Adds translation modal helpers to utilities/user/translation-submitter.ts for the instruction line naming the content type, the source text, the validation errors, the save button state and its label, plus skipToTranslationItemOfContentType so a test can reach a named item without depending on the order the modal serves them in.
   • Adds review helpers to utilities/user/translation-reviewer.ts for an opportunity card's action button label, the "Back to lessons" control, submitting a review and checking its short-lived toast, and the accept and reject button labels.
   • Adds expectLessonTileToShow to utilities/user/logged-out-user.ts, which checks the title and objective on a community library tile. The objective is only rendered at desktop width, so it is checked only there.
   • Registers the three suites in core/tests/ci-test-suite-configs/acceptance.json.
3. (For bug-fixing PRs only) N/A

Note on scope

This PR is stacked on PRs 2.5 (oppia#26997), 2.7 (oppia#26961) and 2.8 (oppia#27083) and must merge after all three. The milestone table lists only 2.7 and 2.8 as prerequisites, but the Content Type filter and the metadata and skill items in the translation modal come from 2.5, so the contributor flows cannot be tested without it. Those three branches are merged into this one, so the GitHub diff shows their files too. The files this PR itself adds are the ones listed above, and the incremental diff is git diff --name-only $(git rev-list --min-parents=2 --max-count=1 HEAD) HEAD.

The specs are written for Puppeteer rather than Playwright. The Playwright migration (oppia#24715) is proceeding one user journey at a time and has not reached translation-submitter or translation-reviewer, and the Playwright suite has no contributor dashboard utilities at all. Writing these in Playwright would mean building a translation submitter, a translation reviewer, the opportunity filters and the translation and review modals from scratch, duplicating work that migration will do, and splitting one feature's coverage across two frameworks. It would also leave 2.13 unable to fold the feature- folders back into the base Puppeteer specs when the feature flag is removed.

Search by translated title and tag (2.9, oppia#27111) is not covered here. It was added to the plan after the milestone table was written and is not part of 2.11's scope, and including it would add a fourth unmerged branch to the stack.

Essential Checklist

Please follow the instructions for making a code change.

• I have linked the issue that this PR fixes in the "Development" section of the sidebar.
• I have checked the "Files Changed" tab and confirmed that the changes are what I want to make.
• I have written tests for my code.
• The PR title starts with "Fix part of [Feature Request]: Use new translation opportunity structure for all user-generated content in curated curriculum oppia/oppia#24933: Acceptance tests for multi-entity translation".
• I have assigned the correct reviewers to this PR (or will leave a comment with the phrase "@{{reviewer_username}} PTAL" if I can't assign them directly).

Testing doc (for PRs with Beam jobs that modify production server data)

N/A

Proof that changes are correct

Proof of changes on desktop with slow/throttled network

This PR adds acceptance tests and changes no user-facing behaviour, so the proof is the test runs themselves.

Verification via static checks:

1. npx tsc --noEmit -p tsconfig.puppeteer-acceptance-tests.json passes with no errors in the changed files.
2. npx eslint --ext .ts passes on the three new specs and the four changed utility files.
3. npx prettier --check passes on core/tests/puppeteer-acceptance-tests/ and core/tests/ci-test-suite-configs/acceptance.json.
4. python -m scripts.check_tests_are_captured_in_ci confirms the three new suites are registered.

Verification via stress tests:

Stress tested each new suite for 50 runs across both viewports:

• translation-submitter/feature-translation-opps-with-new-opps-model/translate-metadata-and-skill-in-target-language: TODO runs passed (TODO link)
• translation-reviewer/feature-translation-opps-with-new-opps-model/review-metadata-and-skill-translations: TODO runs passed (TODO link)
• logged-out-user/feature-translation-opps-with-new-opps-model/view-translated-lesson-metadata-and-concept-cards: TODO runs passed (TODO link)

Proof of changes on mobile phone

The stress test workflow runs every suite at both desktop and mobile viewport, so the mobile results are in the runs linked above.

Proof of changes in Arabic language

view-translated-lesson-metadata-and-concept-cards.spec.ts sets the site language to Arabic to check that a concept card with no accepted Arabic translation falls back to its English explanation.

PR Pointers

• Never force push! If you do, your PR will be closed.
• To reply to reviewers, follow these instructions: https://github.com/oppia/oppia/wiki/Rules-for-making-PRs#step-5-address-review-comments-until-all-reviewers-approve
• Some e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.
• See the Code Owner's wiki page for what code owners will expect.