To test SCORM package files before delivery, run three checks in order: validate the zip structure, play the course in a neutral player such as SCORM Cloud, then play it in an LMS that resembles your client’s. Each check catches a different kind of failure.
Providers get blamed for tracking problems they never saw, because the course fails only inside the client’s LMS. This guide gives you a test script, an eight-point matrix and a one-page test record.
Disclosure: SimpliAuthor is a SimpliTrain product, made by the same company that publishes this site. The steps below are vendor-neutral and work for a package from any authoring tool.
Key takeaways
- Validate the package, test it in a neutral player, then test it in the client’s LMS or one like it.
- Run three attempts: failing, passing and interrupted midway. One happy-path run hides score and resume bugs.
- Read the debug log, not just the learner screen.
- No test proves identical behavior in every LMS, so send the client a record of what you tested and what you did not.
Why should you test a SCORM package before the client’s LMS sees it?
Testing a SCORM package before delivery separates package defects from LMS configuration problems while fixes are still cheap and private. Without a record, a failed completion looks like your error, even when the client’s LMS reads the course’s data differently.
LMSs do not read tracking data identically. According to Articulate Support, SCORM 1.2 reports one status value, so each LMS judges what it means, and the same course can show different statuses in different LMSs.
How do you test SCORM package files before they reach a client?
Test SCORM package files in three stages: structure validation, a run in a neutral player that exposes the debug log, and a run in the client’s LMS or a close match. Run them in that order, because each stage removes one suspect.
Sources disagree on whether the second stage is enough. Rustici Software, which makes SCORM Cloud, says content failing there will probably fail in your LMS too. That holds one way only: passing in SCORM Cloud is necessary evidence, not proof.
- Stage 1, validate the package: check the zip structure and manifest.
- Stage 2, neutral player: run the three-attempt script in SCORM Cloud and read the debug log.
- Stage 3, client-like LMS: repeat the passing and interrupted attempts in the client’s staging site, or a similarly configured LMS.
After stage three, fill in the test record and send it with the package.
How do you validate a SCORM package before launching it?
Validating a SCORM package means checking that the zip is built correctly before any learner data is involved. The manifest file, imsmanifest.xml, must sit at the root of the zip, every file it references must be present, and the SCORM version must be one the client’s LMS accepts.
LearnUpon’s support documentation (updated March 2026) lists a missing manifest, a manifest nested in a subfolder, an unsupported SCORM version and special characters in filenames as common upload failures. Run this pre-flight list on every build:
- Manifest location: zip the contents of the folder, not the folder itself, then unzip and confirm imsmanifest.xml is at the top level.
- Filenames: use plain letters and numbers, since LearnUpon reports special characters can break uploads.
- SCORM version: match the client’s stated version, using our SCORM 1.2 vs SCORM 2004 guide to choose.
How do you test SCORM package behavior in SCORM Cloud?
SCORM Cloud is a free-to-start hosted player from Rustici Software that imports your zip, launches it and records what the course reports. Upload the package, finish it in different ways and check the results and debug log for each attempt.
As of October 2026, Rustici’s pricing page (last modified June 16, 2026) lists a free trial with 3 courses, 5 GB of storage and 10 active resettable registrations, with no time limit. A Tester plan costs $40 per month and keeps the 10 resettable registrations. Rustici’s user guide recommends the Sandbox for repeated launches, because it avoids registration limits.
What is the three-attempt test script?
The three-attempt script covers the pass path, the fail path and an interrupted session. Run all three on every package.
- Attempt A, fail path: finish the course but answer the quiz wrongly. Expect a failed or incomplete result.
- Attempt B, pass path: reset the registration, complete every required element and pass. Expect completed or passed, plus a score if there is a quiz.
- Attempt C, interrupted session: leave halfway with the exit button, relaunch and confirm you return to the same spot. Repeat by closing the tab.
What should the debug log show?
The debug log should show a complete conversation between the course and the player: initialize, set status, set score if there is a quiz, commit and terminate. A missing call is a common root of a lost completion.
Rustici’s troubleshooting article by Joe Donnelly (June 2021) lays out the SCORM 1.2 sequence. A course must call LMSInitialize and LMSFinish, set cmi.core.lesson_status, set cmi.core.score.raw when there is a quiz, and call LMSCommit to persist data. A score is not required, but your client’s LMS may require one.
Pro tip: Keep A Known-Good Control Package. Download a complete example from the SCORM.com Golf Examples, choosing one the page does not mark as non-functional, and upload it to the client’s LMS next to your course. If the control also fails to track there, that points to the LMS configuration, and you have evidence that has nothing to do with your authoring.
What should an eight-point SCORM test matrix check?
An eight-point SCORM test matrix checks structure, launch, completion, score and pass mark, resume, exit behavior, browsers and retakes. Each row states how to run the check, what a pass looks like and what a failure usually means in practice.
| Test | How to run it | Pass looks like | A failure usually means |
|---|---|---|---|
| 1. Structure | Import the zip into SCORM Cloud, then the client LMS | Imports with no manifest or parser error | Manifest not at zip root, missing files or unsupported version |
| 2. Launch | Launch from the course page and an assignment | First screen renders, no API error | Blocked pop-up, wrong launch path or old content blocked by the browser |
| 3. Completion | Attempt B: finish every required element | Log shows a completed or passed status set | No status set, or completion rule differs from the LMS setting |
| 4. Score and pass mark | Attempts A and B with known quiz answers | Score matches your answers; fail and pass results differ | No score set, or pass mark differs from the LMS mastery score |
| 5. Resume | Attempt C: exit midway, relaunch | Returns to the same place with answers kept | suspend_data too large for the SCORM version, or data not committed |
| 6. Exit behavior | Exit with the button, then with a closed tab | Same data saved either way | Course relies on an exit call the learner may skip |
| 7. Browsers | Repeat Attempt B in each learner browser | Same result in each | Browser blocking content or cookies |
| 8. Retake | Relaunch after completion, then after a reset | LMS follows the client’s retake rules | LMS attempt setting, not the package |
On row 5, the SCORM.com run-time reference lists a suspend_data maximum of 4096 characters in SCORM 1.2 and 64000 in SCORM 2004 3rd and 4th Editions, and Articulate Support lists 4000 for the 2nd Edition. If a long course loses its bookmark only in SCORM 1.2, suspect that limit first.
Why does a SCORM package pass in SCORM Cloud but fail in the client’s LMS?
A SCORM package that passes in SCORM Cloud but fails in a client’s LMS usually has an LMS-side cause: a stricter data requirement, a setting such as mastery score, a version quirk or a browser policy. Compare the debug log to the LMS’s own log before changing the package.
Check these causes in order:
- Missing data the LMS requires: the log shows no score or no commit.
- Different status interpretation: common with SCORM 1.2. Try SCORM 2004 if the client supports it.
- Suspend data over the limit: resume fails only on long courses.
- Tab or session handling: LearnUpon notes that scores can be missing when a learner closes the tab instead of using the exit button.
- Client configuration: mastery score, attempt limits or completion criteria set in the LMS.
Nimble’s help center states the ownership rule: if a package fails in your LMS but works in SCORM Cloud, contact the LMS provider. Our SCORM compatibility across LMS platforms guide explains the platform differences. After any late fix, repeat all three attempts. If the fix means editing a compiled package without source files, see how to edit a SCORM file without the source files.
Which free tools can test SCORM package files, and what are their limits?
Free tools that test SCORM package files fall into three groups: a hosted player with logs such as SCORM Cloud, a browser viewer that previews playback, and a debugger that runs inside an LMS. None of them replaces a run in the client’s own environment.
| Tool type | Example | What it shows | Limit to know |
|---|---|---|---|
| Hosted player with logs | SCORM Cloud trial | Results and debug log per registration | 3 courses, 5 GB, 10 resettable registrations (Rustici pricing page, June 2026) |
| Browser viewer | educate-me.co free SCORM viewer | Plays SCORM 1.2 and 2004 zips | Its page says tracking happens in an LMS player, so it previews only |
| In-LMS debugger | SCOverseer bookmarklet | SCORM calls inside an LMS | Needs the course already in an LMS (per LMS Chef) |
Pro tip: Check Where Client Files Go. Client courses are often under NDA. The free viewer we reviewed asks for an email and a role and does not state how long it keeps uploads. Read privacy terms before uploading confidential content.
What should you send the client with the package?
Send the client a one-page SCORM test record with each package you deliver. It lists the environments you tested, the result of each matrix row and any known limits, so the client can confirm tracking quickly and your work is documented.
Copy this template for each delivery and replace the bracketed items:
SCORM TEST RECORD Course and version: [name] Date: [date] Tester: [name] SCORM version: [1.2 / 2004 3rd / 2004 4th] Environments: SCORM Cloud [date]; client-like LMS [name or "not tested"]; browsers [list] Results (pass / fail / not tested): 1 [ ] 2 [ ] 3 [ ] 4 [ ] 5 [ ] 6 [ ] 7 [ ] 8 [ ] Attempt A, fail path: [status, score] Attempt B, pass path: [status, score] Attempt C, interrupted: [resumed at correct place: yes / no] Not tested: [for example, mobile app] Client to confirm: mastery score [value]; completion criteria [value]
What should you do next?
Run the three-attempt script on your next SCORM package delivery, before it ships to the client. Save the SCORM Cloud debug log, fill in the test record and ask the client’s administrator for a staging slot so the third stage is possible.
If your packages start as PDFs, slides, Word files or recordings, the free SimpliAuthor SCORM converter outputs SCORM 1.2 or 2004, according to its product page. That page does not describe completion or score tracking, so run the same matrix on its output. Our PDF to SCORM converter guide covers those conversions.
If you need an LMS to test in or deliver from, SimpliTrain comes from the same company as SimpliAuthor. You can request a SimpliTrain demo and ask how it reports SCORM completion and scores. For later revisions, use our checklist for updating old SCORM courses.
Frequently asked questions
How do I test a SCORM package for free?
Upload the zip to a SCORM Cloud trial account, launch it from the Sandbox and check the results and debug log. As of October 2026, Rustici’s pricing page lists 3 courses, 5 GB and 10 resettable registrations for the free trial, with no time limit. Then repeat the key attempts in the client’s LMS.
Is SCORM Cloud enough to prove a package works in my client’s LMS?
No. A pass in SCORM Cloud is strong evidence the package is sound, but each LMS applies its own settings and interpretations. Rustici says content failing in SCORM Cloud will probably fail in your LMS too. The reverse does not hold, so also run the course in the client’s environment.
Why does my SCORM package work in SCORM Cloud but not in the LMS?
The cause is usually on the LMS side: a required score the course never sets, a mastery score mismatch, a different reading of SCORM 1.2 status or a suspend_data limit. Compare the SCORM Cloud debug log with the LMS log. Nimble’s help center advises contacting the LMS provider in this case.
What is the SCORM suspend_data limit and why does it break resume?
Suspend data stores a learner’s place between sessions. According to the SCORM.com run-time reference, the limit is 4096 characters in SCORM 1.2 and 64000 in SCORM 2004 3rd and 4th Editions. A long SCORM 1.2 course can exceed 4096, and resume then fails. Republishing as SCORM 2004 3rd or 4th Edition is the usual fix.
Is there an official SCORM compliance test?
Yes, ADL publishes SCORM conformance test suites, but ADL’s SCORM page says the tests run on an honor system with no ADL involvement, and that certification is no longer offered. Conformance logs do not prove a course tracks correctly in a particular LMS.



