learningequality / learningequality/studio
Determine testing strategy for publishing channels and ricecooker workflow
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Summary
Context: An error catchall in exercise publishing caused publish operations to complete even though exercise generation was failing.
As part of the overall Vue refactor QA effort, we should ensure we have test cases to ensure proper behavior for publishing of nodes of all major content types, and tests that involve ricecooker workflows, to ensure these have not been broken by the Vue migration.
Some ideas:
- Force-publish the Studio QA channel and review the resulting channel to ensure publishing happened successfully.
- Maybe have the ricecooker equivalent "a little bit of everything" channel uploaded to Studio.
- Perhaps we could use something like Selenium IDE to have an automated script to check through the resulting Kolibri channel, so that we can run this regularly?
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 by reviewing the Studio QA channel publishing flow, the ricecooker workflow, and the existing Vue migration QA coverage. Define the supported content types and publishing outcomes to verify, then decide whether the resulting checks should be manual or automated before identifying the appropriate test entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- content, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100