Testing is one of the most important — and most poorly executed — stages of the IB Design Technology IA. Many students believe testing is simply showing that their product works. In reality, IB testing is about gathering evidence, exposing weaknesses, and driving improvement.
If testing only proves success, it is usually too weak to score highly.
What Testing Means in IB Design Technology
Testing in IB Design Technology is the process of:
- Measuring performance against design requirements
- Collecting user feedback
- Identifying strengths and limitations
- Generating evidence for iteration and evaluation
Testing is not a formality. It is the bridge between design and evaluation.
The Biggest Testing Mistake Students Make
The most common mistake is testing after everything is finished, simply to confirm success.
Weak testing looks like:
- “The user tested the product and said it worked well.”
- One photo with minimal explanation
- No link to design requirements
This provides almost no usable evidence and limits evaluation marks.
Start Testing Earlier Than You Think
Strong projects test before the final product is complete.
Early testing allows you to:
- Identify problems while changes are still easy
- Justify iteration
- Show learning and improvement
Testing early versions, components, or mock-ups is often more valuable than testing a polished final product once.
