Lesson 4: Testing and Sharing
15-20 minutes
What You Will Learn
In this lesson, you will:
- Test your project to see if it does what you planned
- Have someone else try your project and watch what happens
- Learn how to give and receive kind feedback
- Make improvements based on what you learn
- Celebrate your finished project!
Step 1: Test It Yourself
Before you show your project to anyone else, test it yourself. Go through your project like you have never seen it before. Pretend you are a brand-new user!
Your Testing Checklist
Go through this list and check each thing:
- Click the green flag. Does the project start the way you planned?
- Does the first thing happen correctly?
- Try clicking on sprites. Do they do what they should?
- Does the project go in the right order, from beginning to end?
- Do the sounds play at the right time?
- Does the project have an ending? Does it feel finished?
- Try clicking the green flag again. Does it start over correctly?
- Is there anything confusing? Would someone know what to do?
If you find something that does not work right, go back to Scratch and fix it. This is not a problem -- this is exactly how real creators work! They call this process iteration, which means making something better by trying, testing, and improving.
Step 2: Have Someone Else Try It
This is one of the most important steps! When you build something, you know how it works because you made it. But other people do not know what you know. Having someone else try your project helps you see it through fresh eyes.
How to Run a User Test
Ask a family member or friend to try your project. Here are the rules:
- Do not explain anything first. Just say "Try my project!" and let them figure it out.
- Watch quietly. Do not tell them what to click or what to do. Just watch.
- Notice what happens. Do they get confused at any point? Do they click on something you did not expect? Do they smile or laugh?
- Ask them afterwards: "What did you think? Was anything confusing? What was your favorite part?"
What to Watch For
When someone else tries your project, pay attention to these things:
- Did they know how to start? (If not, you might need to add instructions.)
- Did they try to click on something that does not do anything? (Maybe that should do something!)
- Did they seem bored at any point? (Maybe that part needs to be shorter or more interesting.)
- Did they enjoy it? (That means you did a great job!)
Step 3: Giving and Receiving Kind Feedback
Feedback means telling someone what you think about their work. Good feedback is kind and helpful. It tells someone what they did well AND gives ideas for making it even better.
Examples of Kind Feedback
Not helpful: "It is boring."
Kind and helpful: "I liked the beginning! Maybe you could add a sound when the character talks to make it even more exciting."
Not helpful: "It does not work."
Kind and helpful: "When I clicked on the cat, nothing happened. I think it might need a 'when this sprite clicked' block."
Not helpful: "Mine would be better."
Kind and helpful: "This is really cool! The joke at the end made me laugh. What if the character did a dance too?"
The Feedback Sandwich
A good way to give feedback is to make a "sandwich":
- Top bread: Say something you liked. ("I loved the space background!")
- Filling: Share an idea for improvement. ("Maybe the alien could talk slower so I can read it.")
- Bottom bread: End with encouragement. ("This is really fun -- great job building this!")
When you get feedback, remember: the person is trying to help you make your project even better. It is not about what is wrong -- it is about how to make it even more awesome.
Step 4: Make Improvements
Now that you have tested your project and gotten feedback, you might want to make some changes. Here are some common improvements:
- Add instructions. At the beginning, have a sprite say something like "Click on me to start!" so people know what to do.
- Fix timing. If text disappears too fast, make the "say" blocks last longer. If things feel slow, make them shorter.
- Add sounds. A little music or sound effects can make your project much more fun.
- Add a clear ending. Have a sprite say "The End!" or "Thanks for playing!" so people know it is finished.
- Keep it simple. Sometimes the best improvement is removing something that is confusing, not adding more stuff.
You do not have to make every change that someone suggests. It is YOUR project. Pick the improvements that you think will make it the most fun.
Step 5: Celebrate!
You Did It!
You just did something amazing. You came up with an idea, made a plan, built it in Scratch, tested it, got feedback, and made it better. That is exactly what real creators do!
It does not matter if your project is small or simple. What matters is that you thought it through and finished it. That takes creativity, patience, and real problem-solving skills.
You should be very proud of yourself!
Ways to Celebrate
- Show your project to other family members or friends
- If you have a Scratch account, share your project online so other kids can see it
- Take a screenshot of your project and put it on the fridge (yes, really!)
- Talk about what you learned while building it
- Think about what you might want to build next
Key Takeaways
- Test your project by going through it like a brand-new user
- Have someone else try it without explaining anything -- watch what they do
- Kind feedback tells someone what they did well AND gives ideas for improvement
- Iteration means making something better by trying, testing, and improving
- You do not have to make every suggested change -- it is your project!
- Celebrate what you made! Finishing a project is a real achievement
What is Next?
Practice Activities
Try some extra challenges to sharpen your project-building skills.
Practice ActivitiesModule Quiz
Test what you learned about design thinking, planning, building, and testing.
Take the QuizModule 8
Ready for the final module? Explore logic puzzles, strategy games, and celebrate everything you have learned!
Go to Module 8