Year 9 Digital TechnologiesUnits 1 and 2
ASSESSMENT LESSON 7

Required Testing Begins 🧪

Today you begin the formal test records for your rover. Testing is where your design starts producing evidence.

Start with movement tests, then begin object interaction. Record what actually happens, even if the result is messy.

Today’s goal

Start formal testing for straight-line movement, turning and object interaction.

Before you leave

Complete Engineering Entry 7 and record at least one formal test result in your Starter Pack.

1. Minimum Starter Pack pages to complete today

Today’s folder evidence should show that formal testing has started. Use real test results, not guesses.

Starter Pack page Minimum work for today
Engineering entry tracker Add Entry 7 when it is completed and signed off.
Required testing overview Check that you understand all six required tests. Add general testing notes if needed.
Straight-line movement test Record what you tested, how you tested it, expected result, actual result, problem found, improvement made and evidence recorded.
Turning test Record how you tested turning and whether the rover turned accurately enough for the task.
Object interaction test Start the object interaction test. Record results for any actions tested today: collect, push, lift, carry or transport.
Initial/final design notes If testing causes a design change, add a note or sketch showing what changed.

2. Object interaction reminder

The final object interaction test must cover all five actions. Today, begin the test and record honest results.

Collect
Get control of the object.
Push
Move the object by pushing it.
Lift
Raise the object from the surface.
Carry
Hold or support the object while moving.
Transport
Move the object to another location.

3. Testing routine

  1. Choose one test to run.
  2. Write what you expect to happen.
  3. Run the test carefully.
  4. Record the actual result.
  5. Write one problem, improvement or next step.
  6. Add evidence: sketch, result, measurement, observation or photo reference.
Testing tips
  • Change one thing at a time so you know what caused the result.
  • Repeat a test if the first result seems strange.
  • Write down failures. Failed tests are useful evidence.
  • Make your test clear enough that someone else could understand what you did.
Extension ideas if your group is ahead

Choose an extension that suits your own design. Do not copy another group’s solution. Record what you tried, why you tried it, and what happened.

  • Repeat a movement test three times and compare the results instead of relying on one attempt.
  • Create a simple scoring scale for object interaction, such as 0 = failed, 1 = partly worked, 2 = worked reliably.
  • Record a before/after result if you improve the rover during testing.
  • Add a labelled test setup sketch so another group could understand how you tested your rover.

Engineering Entry 7: what a detailed entry needs

Use the entry sheet properly. Your entry should tell the story of what happened this lesson, not just list tasks.

Entry section What to include today
What I/we did today Write which formal test or tests you started, how you tested the rover, and what happened.
Problem, test or checkpoint Choose one formal test result as your checkpoint. This could be straight-line movement, turning or one object interaction action.
What I noticed and thought Explain what you observed and what you think caused the result, problem or behaviour.
What changed or was fixed Describe the change you made, or explain what needs to change next if it is not fixed yet.
Result and next step Record what happened after the change or check, then write the next sensible action.
Evidence space Add a labelled sketch, labelled diagram, measurement, test result, code note, observation or photo reference.
Helpful sentence starter: “Today we formally tested... The result was... This shows that our rover... The next improvement should be...”

Before you leave: ask for teacher feedback/sign-off, then put the entry sheet in your clear plastic folder.

Authenticity reminder

Do not invent test data. Your test records must show what the rover actually did today, even if the result was not what you hoped for.

Year 9 Digital Technologies • Assessment Lesson 7 • VEX IQ Gen 2 Rover