openedx / openedx/frontend-app-authoring
General QA sweep for frontend-app-authoring
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 218
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 20
Description
Background
Since being converted to react, we are encountering a variety of miscellaneous bugs in Studio.
AC
- Run every Studio frontend test in the release testings spreadsheet
- Test any remaining Studio features. Write down what you test.
- Be sure to test all advanced Problem types and Advanced components.
- Be sure to test Studio's extensions points using some 3rd-party plugins. At a minimum, test:
- Per your judgement, add additional test cases to the release testing spreadsheet.
- Catalog and triage bugs you encounter.
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
Start in the frontend-app-authoring repository by locating the Studio frontend tests and the release testing spreadsheet. Run every listed test, exercise advanced Problem types, Advanced components, and the named third-party plugins, recording coverage and cataloging any bugs found. Done means the requested coverage is documented and discovered bugs are triaged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100