openedx / openedx/openedx-platform
Build out simple e2e Testing in CI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
Context
The edx-platform frontend is very complex and so not all the issues with it can be caught with the existing frontend unit tests.
Goal
To ensure that we don't break the most basic capabilities of the edx-platform, we should have a set of tests that run on a production-like runtime of edx-platform.
Acceptance Criteria
The end-to-end tests should spin up a production like run of edx-platform with assets fully built and test the following scenarios:
- User creation
- User Login
- User enrollment in a course
- User can load a problem
- User can submit a response
Some of these capabilities have moved to MFEs in which case we should use the relevant APIs but where possible we should load the page/iframe in a browser and do UI level testing.
Contributor 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.
Research direction
The issue names no files, tests, or entry points; start by reviewing the existing frontend unit-test and CI setup and how a production-like edx-platform runtime is launched. Done means CI runs browser or API-level checks covering user creation, login, enrollment, problem loading, and response submission with fully built assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, ci-cd, frontend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100