Test the behaviour, not just the ZIP
A SCORM package can upload successfully and still behave incorrectly. A useful test checks the whole learner journey: launch, navigation, completion, score, exit, resume and the record shown in the LMS.
Use a staging LMS or a standards-focused test environment where possible. Keep production learners away from unverified packages.
1. Check the package structure
- Confirm the file is a valid ZIP.
- Open it and make sure
imsmanifest.xmlis at the ZIP root, not inside an extra folder. - Check that files referenced by the manifest actually exist and that filename case matches.
- Re-export rather than hand-editing a package unless you understand the consequences.
A missing or misplaced manifest is a common reason an LMS cannot recognise a SCORM package.
2. Test launch and every important path
Launch as a learner, not only as an administrator. Test menus, media, interactions, links and branching routes. If the course has optional and required paths, test both.
Browser developer tools can reveal missing files, blocked requests and JavaScript errors when a course launches blank or breaks midway.
3. Test completion, success and score separately
Run at least three attempts: a successful completion, an unsuccessful assessment attempt and an early exit. Confirm the LMS shows exactly what your design intends.
Do not assume “completed”, “passed” and “score recorded” are the same event. SCORM versions and LMSs can represent these states differently. See completion vs passed/failed.
4. Test exit and resume
Leave partway through, close the player, relaunch and verify that the learner returns to the intended place with relevant progress preserved. Repeat after a long interaction or assessment because resume data can fail only after the course has accumulated more state.
5. Use a small test matrix
| Test | Expected result |
|---|---|
| First launch | Course opens without errors |
| Exit midway | Attempt remains resumable |
| Relaunch | Progress/location restored |
| Pass | Correct completion, success and score |
| Fail | Correct unsuccessful state without false completion |
| Retake | New attempt behaves as LMS policy intends |
6. Record the tested configuration
Keep the source version, export standard, mastery score, completion rule, test LMS and test date with the release. If a future update behaves differently, this gives you a known-good baseline.
If something fails, work systematically rather than republishing at random. Start with our SCORM completion troubleshooting guide.
Put the guidance into practice
Build a real course in Lumeo, preview it in the browser, and export it to SCORM, standalone HTML or PDF. The free plan does not require a payment card.