Test site name is "edX"; use "Open edX" in `.env.test`

Open Beginner friendly
#2,119 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
94/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, react
Domain
frontend, testing

Research direction

Start with .env.test and verify how SITE_NAME is consumed by the listed course and upgrade-bullets components. Review the page-title assertion in src/courseware/course/Course.test.jsx and the two name assertions in src/generic/upgrade-bullets/UpgradeBullets.test.jsx, then run those suites. Done means the test configuration and both assertions use Open edX, with the relevant tests passing.

Written by the indexing model from the issue text.

Description

.env.test sets SITE_NAME='edX', so every page title and site-name string the test suite renders says "edX" rather than the platform's name:

SITE_NAME='edX'

Twelve components read getConfig().SITE_NAME (the page titles in Course, LoadedTabPage and the three course-exit pages, HonorCode, SocialIcons, NewUserCourseHomeTourModal, UpgradeBullets, AccountActivationAlert). With the value changed to Open edX, all of their suites pass except two assertions that hard-code the old name:

  • src/courseware/course/Course.test.jsx: the | edX at the end of the page-title assertion in loads learning sequence.
  • src/generic/upgrade-bullets/UpgradeBullets.test.jsx line 33: /Support our.*?at edX/ and 'Support our mission at edX'.

No snapshot contains the value.

Expected. .env.test uses SITE_NAME='Open edX', and the two assertions follow. Three lines in three files.

.env.development also sets SITE_NAME='edX'; that is the fallback for a dev server without a MFE_CONFIG response, not a test fixture, and is out of scope here.

[!NOTE]
This issue was authored by Claude (Claude Code) and reviewed before posting.

Dominant language
JavaScript
Stars
71
Forks
341
Avg merge
4d 18h
Merged PRs (30d)
20

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openedx/frontend-app-learning

All issues in openedx/frontend-app-learning

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.