Skip to content

6. Testing, Debugging and Maintainability

This section focuses on improving software quality once programs have been written.

Combines

  • naming conventions
  • internal documentation
  • construction of relevant test data
  • test tables with expected and actual output
  • breakpoints
  • debugging output statements

Why these belong together

These techniques all help students refine and explain their code. They are especially important in a folio because students need to show evidence of process, not just final answers.

Good folio-style tasks

  • repair a faulty program using breakpoints or debugging output
  • create a testing table before running a solution
  • improve poorly named code and justify the changes
  • add useful internal documentation to explain logic and data handling

Key skills supported

  • document the functioning of a software solution through internal documentation
  • design and apply suitable debugging and testing techniques