Unit 4 - 7.5%

Task 7: Programming Practical Test

Practical programming test with algorithms and trace tables.

Open Resource Pack

Assessment Details

Type
Practical
Timing
Week 9
Weighting
7.5%
Topics
Control structuresTrace tablesTest dataDebugging

Task Overview

Task 7: Practical Test (Programming)

Outline Reference

  • Assessment type: Practical test
  • Task weighting: 7.5% (sample outline)
  • Timing: Term 3, Week 9
  • Dates (2026): Monday 14 September to Friday 18 September

Purpose

Assess programming skills: code development, debugging, and use of control structures.

Task Overview (Draft)

A timed practical test requiring students to:

  • Develop or modify a simple programming solution.
  • Use variables, data types, and control structures.
  • Identify or correct programming errors.

Evidence and Submission

  • Source code file and test evidence.
  • Completed output or screenshots if required.

Conditions

  • Conducted under supervised, time-limited conditions.
  • Language/environment specified by school.

School Policy (Assessment and Reporting)

  • Missed assessments: absent without a valid reason may incur a penalty decided by the HOLA; unavoidable absence is completed on return.
  • Absences: parent notification required; sickness/misadventure form for formal assessments; medical certificate may be required.
  • Extensions: request to the HOLA before the due date; acceptable reasons include illness/injury/personal circumstances; adjusted date is generally within two days of return.
  • Late submissions: late without acceptable reason receives a percentage penalty set by the teacher in consultation with the HOLA.
  • Academic integrity: no cheating, collusion, plagiarism, or AI-generated work; correct acknowledgment required.
  • Authentication: drafts/checkpoints may be required; in-class validation may be used.

Glossary Verbs (Use Consistently)

  • Construct: make or build.
  • Debug: identify and correct errors.
  • Demonstrate: show by example.