The goal counter that counted double
A student builds a goal counter for the made-up Eastfield School football team. A click should add one goal. On match day, the first goal makes the screen say 2.
The student tested it, but only by looking at the first screen. Testing is not looking. It is asking the app questions on purpose and checking the answers.
By the end of this lesson
Note
I can describe the stages and kinds of testing and use a simple tool to find a fault.
Key words
| Word | What it means |
|---|---|
| Testing | checking an app on purpose to find faults |
| Bug | a fault that makes an app do the wrong thing |
| Debug | to find and fix a bug |
| Functional testing | checking that each feature does its job |
| Non-functional testing | checking how well it works, such as speed and ease of use |
| Breakpoint | a chosen line where the code stops so you can look |
The cells students fill in are left blank in this preview.
Starter: what you already know
Have a go
Starter: what you already know
4 questionsYour answers are marked here and are not kept. A college account keeps every student’s marks.
Testing finds faults before users do
The purpose of testing is to find faults, called bugs, and to check the app does what the client asked. Finding a bug in testing is good news. Finding it after launch is expensive and upsets users.
Testing happens in stages. Each stage has different testers.
Three stages of testing
| Stage | Who tests | Aim |
|---|---|---|
| Alpha | The team and people inside the organisation | Find the big faults early |
| Beta | A small group of real users outside the team | See how real people use it |
| User acceptance | The client | Agree it does what was asked, before it is accepted |
The cells students fill in are left blank in this preview.
Check
Have a go
Check
3 questionsYour answers are marked here and are not kept. A college account keeps every student’s marks.