|Section Title||Primary information||Description and Notes||Suggested resources|
|Lesson Length||The expected lesson length will be approximately one hour||
Some variation possible.
Assessment Level 1
|Students||The lesson is suitable for KS3 and KS4 students||Since this is a new specification, the lesson is suitable for Year 7 to 9 students and differentiated by outcome|
|Overall Focus||The lesson will be an introduction to testing and the processes that are involved||This lesson will introduce some aspects and examples of testing to make sure students understand bug testing procedures|
|Key words||abstraction, programming language, instruction, open source, digital, file types, variable, loop,||These words need to be reinforced throughout the series of lessons|
|Assessment||test code||Evidence here will be student's own work and assessor observations|
|Key Questions||Some questions to get learners thinking about the topics||Students need to appreciate good testing makes good programs||Why do we need to test code? What are the ways to test code? Do we need to ask someone else to test it for us? Why? What is a computer bug?|
Students need to be shown the key part of testing a program they have made
|If you are using the Learning Machine learning system, students can add their comments and material to this site as evidence of their growing understanding. The site, if used consistently, will show progression via charts of activity and outcomes.|
|Teaching and Learning Elements||
In this lesson we need to give students the tools and knowledge to begin testing their program. They also need to be shown this in terms of an overall project, so they can document the process.
Use some of the student's own work and share with the group and discuss the quality of the tests designed and used.
Question students about how and why they did what they did. Check for understanding.
You may need to give the students some examples of testing procedures and examples of possible bugs.
|Lesson Structure||Possible structure||
Give some worked examples of code in the real world and show how bugs might exist. The simplest and most obvious one is a typo, but it could be wrong numbers, wrong words, out of place sequences etc. Show them the results of bugs if possible.
For example numbers output might be out of sequence or not in the right order, which would show a bug in the program.
The bugs show here are quite hard to spot, which shows how hard it is. The popular operating system Debian Linux has approximately 78,000,000 lines of code to check for bugs. Windows 7 has about 40,000,000, Mac OSX has 85,000,000. Some useful code stats.
|Homework||Get students to document part of their project code to show the syntax they are using or write definitions for their documentation on their portfolio||Students can vary their homework depending on their level of understanding||Get students to document their experience on their portfolio system for assessment|