oppia / oppia/oppia-web-developer-docs
Create Tutorial - How to write and run acceptance tests.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 133
- PR merge metrics
- No merged PRs in 30d
Description
Skills covered
Similar issues
Existing relevant pages
https://github.com/oppia/oppia/wiki/Acceptance-Tests
Example
CUJ: As a user, exploring the "Recently Published" section
The user visits the Oppia platform and logs in.
The user navigates to the Community Library.
The user decides to explore new content and clicks on the "Recently Published" section.
The user browses through the recently published explorations but doesn't start any.
The user logs out and leaves the platform.
This journey involves a user exploring the "Recently Published" section, which is not a critical function but contributes to the user experience by providing access to the latest content. However, this may get covered in the main CUJs, but not in the same flow as mentioned above as it's more of an edge case. This journey would require tests to verify that the "Recently Published" section works correctly and that the user can successfully browse through the recently published explorations.
Notes:Talk about how we need some extra setup to make sure that there's something in the recently published section for them to click on.
Contributor guide
No contributing guide indexed for this repository
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
Read the existing Acceptance-Tests wiki page first to understand the current guidance. Use the provided “Recently Published” user journey as the tutorial example, including the extra setup needed to ensure content is available to click. Done means the tutorial explains how to write and run an acceptance test using this flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100