-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
- How to get help
- Getting started with the project
- How the codebase is organized
- Making your first PR
- Debugging
- Testing
- Codebase policies and processes
- Guidelines for launching new features
- Guidelines for making an urgent fix (hotfix)
- Testing jobs and other features on production
- Guidelines for Developers with Write Access to the Oppia Repository
- Release schedule and other information
- Revert and Regression Policy
- Privacy aware programming
- Code review:
- Project organization:
- QA Testing:
- Design docs:
- Team-Specific Guides
- LaCE/CD:
- Developer Workflow:
Developer Reference
- Oppiabot
- Git cheat sheet
- Frontend
- Backend
- Backend Type Annotations
- Writing state migrations
- Calculating statistics
- Storage models
- Coding for speed in GAE
- Adding a new page
- Adding static assets
- Wipeout Implementation
- Notes on NDB Datastore transactions
- How to handle merging of change lists for exploration properties
- Instructions for editing roles or actions
- Protocol buffers
- Webpack
- Third-party libraries
- Extension frameworks
- Oppia-ml Extension
- Mobile development
- Performance testing
- Build process
- Best practices for leading Oppia teams
- Past Events