Test site name is "edX"; use "Open edX" in `.env.test`
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
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| edXat the end of the page-title assertion inloads learning sequence.src/generic/upgrade-bullets/UpgradeBullets.test.jsxline 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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openedx/frontend-app-learning
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
openedx/frontend-app-learning#2265 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openedx/frontend-app-learning#2250 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
openedx/frontend-app-learning#2147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openedx/frontend-app-learning#2059 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
openedx/frontend-app-learning#2051 ·
Maintainers usually reply within 1 day
All issues in openedx/frontend-app-learning
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
check:passed logos:edit
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
db-d1-sqlite: upsert is aliased to updateOne, so payload.kv.set never inserts new keysPossibly taken @pcbeingused333 claimed this today. OpenBug db: d1-sqlite Payload OSS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#19766 ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inverse-inc/packetfence#9707 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
githubnext/gh-aw-workshop#5896 ·
Maintainers usually reply within 1 day