Task 7 – Testing and Debugging—Martin Levins


A rubric for this unit should address the achievement standards, and the ones that I think are most apposite are:

  1. Plan and manage digital projects using an iterative approach.

    1. here, iterative is the key point
  2. Test and predict results and implement digital solutions.

    1. here, predict then test is the key point
  3. Evaluate information systems and their solutions in terms of risk, sustainability and potential for innovation and enterprise.
    1. an opportunity for peer evaluation here, but I think I would put that as a separate assessment, based on their experience of the first 2

I think I would first lead a conversation about Quality Assurance, based on past experience of the students, who, by now, should have experienced issues relating to inadequate documentation and planning! I’d refer to products such as the 737 Max attitude sensor debacle; admittedly a technical article but with a readability of 9 years of schooling, so should be OK at this level.

I’d steer the conversation to unpacking the achievement standards and turning this to student-speak, then ask “what does above, at or below standard look like?” to build the rubric with the students.

Iteration could be assessed by looking at the development of the code, showing the development and testing process, perhaps by introducing Git as a version control service. This is fairly advanced though, so maybe just saving the code at different stages of development would suffice.

The test case stubs in the code could remain in the code, but simply commented out thus:

#  testing

We could then enable testing by a search and replace:

find “#  testing: ”
replace “#  testing\r” [\r represents carriage return]

After test

find “#  testing\r”
replace “#  testing: “

Prediction and testing could be related to the checklist that pilots use before flight as a way of minimising risk.

So, in short, I’d get the students to build the rubric

.

 

+ There are no comments

Add yours

Leave a Reply