By the time a project reaches the final stage of our eXACT methodology, it is tempting to think the hard work is done. The storyboard has been approved, the course has been built, and it looks ready to go. This is exactly the point at which Test, the fourth stage of our methodology, becomes so important.
Testing can be the stage that gets squeezed when a project runs behind schedule. In our experience, it is also the stage most likely to be underestimated at the planning stage in the first place. That is a mistake, because the issues that surface during proper testing are often the ones learners notice first.
What we actually check
Testing a course properly is not clicking through it once to make sure nothing is obviously broken. It means checking that content is accurate, that every interaction behaves as intended, and that the course works consistently across the devices and browsers learners will actually use.
It also means checking that the course does what the learning outcomes from the eXplore stage set out to achieve. A course can be technically flawless and still miss the mark if it does not actually support the behaviour change or knowledge transfer it was designed for.
Testing for accessibility
Accessibility testing deserves its own mention, because it is easy to assume that building with accessibility in mind during the Create stage is enough on its own. It is not. Screen reader testing forms a core part of how we test every course, since it is the only reliable way to confirm that the structure, labelling and navigation actually work the way they are supposed to for someone using assistive technology.
This kind of testing can surface issues that are invisible if you are only looking at a screen. A button that makes visual sense might be announced unhelpfully by a screen reader. A sequence that looks logical on screen might jump around unpredictably when navigated by keyboard alone.
What good testing covers
A thorough test phase tends to include the following.
- Functional testing of every interaction, link and navigation element
- Screen reader testing to confirm accessibility in practice
- Checking the course across the devices and browsers it will actually be used on
- Reviewing content against the original learning outcomes
- A final proofread for accuracy, spelling and consistency
- LMS testing to ensure SCORM reporting
Skipping or rushing any of these checks tends to store up problems for after launch, which is a far more difficult and costly time to fix them.
Test is not a formality tacked onto the end of a project. It is the stage that confirms everything else has actually worked. The Test stage deserves the same care and attention as the stages that came before it.
