-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Playtesting explorations
Thank you for helping us playtest lessons on Oppia! Your feedback is vital for helping exploration authors understand where students get stuck, so that the lessons can be improved over time for other students. This page explains best practices for playtesting, as well as the sort of feedback we are looking for.
We'd be interested in your feedback on a couple of things in particular:
- Did you enjoy playing the lessons?
- Did you complete the lessons? If not, why?
- As a result of playing the lesson, did you gain proficiency in the subject being taught?
When you’re playing a lesson, please note the following:
- things you particularly like
- wrong answers or misconceptions that you think we should address
- things that you get frustrated/stuck by
- any suggestions you have.
Let us know if particular pieces of feedback that Oppia gives are helpful or not. If you could suggest better feedback, that would be awesome, too.
If you find, at any point, that you don’t want to continue further, that’s totally OK. Just let us know why you stopped, and what you’d change about the lesson so that other students would have a better experience.
Please fill in this post-survey. Also, if you have any questions, let us know, and we’d be happy to try and answer them. Thanks again for your help!
Have an idea for how to improve the wiki? Please help make our documentation better by following our instructions for contributing to the wiki.
Core documentation
Developing Oppia
- FAQs
- Installing Oppia
- Getting started with the codebase
- Making your first PR
- Learning resources for developers
- Codebase Overview
- Coding Guidelines
- Coding style guide
- Guidelines for creating new files
- How to add a new page
- How to write frontend type definitions
- How to write design docs
- Revert and Regression Policy
- Server errors and solutions
-
Debugging
- If your presubmit checks fail
- If CI checks fail on your PR
- Finding the commit that introduced a bug
- Interpreting GitHub Actions Results
- Debugging Docs
- Debugging datastore locally
- Debugging end-to-end tests
- Debugging backend tests
- Debugging frontend tests
- Debug frontend code
- Debugging custom ESLint check tests
- Debugging custom Pylint check tests
- Debugging Stories
- Guidelines for launching new features
- Guidelines for making an urgent fix (hotfix)
- Lint Checks
- Oppia's code owners and checks to be carried out by developers
- Privacy aware programming
- Backend Type Annotations
- Bytes and string handling in Python 3
- Guidelines for Developers with Write Access to oppia/oppia
- Testing
- Release Process
Developer Reference
- Oppiabot
- Frontend
- Backend
- Translations
- Webpack
- Third-party libraries
- Extension frameworks
- Oppia-ml Extension
- Mobile development
- Mobile device testing
- Performance testing
- Build process
- Team structure
- Triaging Process
- Playbooks
- Wiki
- Past Events