Use an IDE to write and test programs
Connect code editing, run-time testing, translation and diagnostics to the integrated development environment.
This sequence follows Cambridge IGCSE Computer Science 0478, 2026–2028 syllabus Version 6. It covers subject content sections 4.1–4.2 only. The separately published 2029–2031 syllabus is not mapped here. Practice is original, self-checked and does not award an official Cambridge grade. Full timed papers and human subject-teacher review remain outstanding.
Before you begin
- No programming language is required. Be comfortable with place value and multiplication; each lesson introduces the computer-science notation it uses.
Work on paper. Try each question before revealing help, and explain why your method works.
Quick readiness check
What is an IDE?
What you will learn
- Explain the role of an IDE
- Identify common IDE functions
- Match a development need to an IDE feature
An IDE combines tools for development
An integrated development environment (IDE) brings programming tools together. It can include a code editor, a run-time environment, translators and error diagnostics.
Apply and check the rule
Common features include auto-completion, auto-correction and prettyprint (automatic formatting). Together these help a programmer write, run, inspect and improve code; they do not prove that the program is correct for every input.
Pause and explain
Which IDE feature formats code consistently?
Worked example
A programmer mistypes a variable name and wants the IDE to flag the problem. Which feature helps?
Show the worked solution
- The program is checked during translation or execution.
- Error diagnostics identify a problem and may point to its location.
- The programmer can correct the source and test again.
Answer Error diagnostics help identify the problem; the programmer must still fix and retest the code.
Try a topic test
Choose Easy, Normal or Difficult. Save your answers and open worked review after finishing.
Test this topic →From guided practice to a new situation
Write your answer and reasoning first. Use a hint only if you are stuck. The model solution is for self-checking; your written work is not automatically marked.
Match each feature to its role: code editor, run-time environment, error diagnostics.
Give me a hint
Separate writing, execution and feedback.
Compare my reasoning
- Code editor: create and change source code.
- Run-time environment: execute the program.
- Error diagnostics: report detected problems.
Editor writes code; run-time environment executes it; diagnostics report errors.
Look for these in your work
- Editing role
- Execution role
- Diagnostic role
A learner wants consistent indentation and automatic suggestions for a function name. Name the IDE feature for each.
Give me a hint
One feature formats, the other suggests code.
Compare my reasoning
- Prettyprint formats source consistently.
- Auto-completion suggests or completes the function name.
Prettyprint; auto-completion.
Look for these in your work
- Formatting feature
- Suggestion feature
A program passes IDE syntax diagnostics but calculates the wrong result for some inputs. Explain why the IDE did not prove the program correct.
Give me a hint
A diagnostic feature catches only errors it can detect.
Compare my reasoning
- The IDE can identify syntax or other detectable problems.
- The algorithm may still contain a logic error.
- The programmer needs tests with representative inputs and expected results.
Passing diagnostics does not prove the algorithm is correct. Test behaviour against expected results, especially boundary and unusual inputs.
Look for these in your work
- Diagnostic limit
- Logic error
- Test requirement
Common mistakes
- Calling auto-completion a translator
- Assuming prettyprint changes the algorithm's logic
What can you explain now?
What does auto-completion help with?
Compare with the explanation
Suggesting or completing code while it is written
It speeds up code entry but does not guarantee that the suggested code is correct.
After trying it yourself, choose your next review. This is your self-assessment.
Your review choice appears on Today. Sign in to sync it across devices.
Make it stick
Name four common IDE features from the syllabus.
If you needed the solution, close it and solve the problem again from a blank page. A correct answer is stronger when you can explain the reason for each step.