Computing Progress logo
Community Supported
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

Lesson Links: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39

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?
Learning Objectives
  • To understand and appreciate the testing procedures
  • To describe and explain, with examples the key tests required
  • To understand how computer programs are tested

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
  • Class led examples of tests
  • Students can break into groups and work on their own programs using and documenting the tests they are applying
  • Class discussion and evaluation of the tests
  • Summarize the key points and reinforce the importance of testing

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.

As previously.

You may need to give the students some examples of testing procedures and examples of possible bugs.


Lesson Structure Possible structure
  1. introduce a range of visual programs and discuss their features
  2. show students some more detailed examples of visual programs, emphasising the structure
  3. group work to work on some of their own ideas
  4. discuss what they have learned and what they can apply
  5. volunteers to share their work and explain how they came to their opinions
  6. highlight next week's focus and issue homework

Use various visual programs to show students how they work and what they do.  The programs chosen will depend on your experience with them and level of comfort.  The idea is for students to choose one for themselves and develop or modify a program and document the process.  You can use Scratch, Logo, Python etc.

You can also investigate using CODE Logo which has other examples of programs which you could use for modifying if students don't want to make their own.

Scratch logo has lots of sample programs to download and modify.

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


Print Friendly, PDF & Email