The first person to test many SCORM courses is the LMS administrator, and they are rarely delighted about it. They upload the package, launch it, watch a status fail to update, and send it back. A day later the cycle repeats. Most of those round trips are avoidable, because most reporting, resume and launch problems can be found on your own machine first. How do you test a SCORM package before uploading it to the LMS, and what exactly should you check?
Test a SCORM package in three passes: inspect the manifest and zip structure, run the course in a tool that logs every SCORM API call, and then repeat a short set of score, status and resume scenarios in an LMS sandbox. The manifest pass catches packages the LMS will reject outright. The API log catches courses that launch but report wrongly or not at all. The scenario pass, with an ordinary learner account, catches problems that only appear inside a real LMS. Together they take an hour or two for a typical course, far less than a week of re-uploads.
Why Test Before the LMS Sees the Package?
Because the LMS is the most expensive place to discover a problem. Every failed upload costs an administrator's time, and every test launch in production can leave stray learner records behind. Some LMS platforms also keep each uploaded version, so a careless afternoon can leave four near-identical copies of a course in the catalogue.

The LMS is also the hardest place to see what went wrong. Most platforms show the result, such as "incomplete", without showing the calls that produced it. A local test environment shows the calls. That visibility turns guesswork into a short list of specific faults.
One terminology note. SCORM, the Sharable Content Object Reference Model, does not test anything by itself. It is a set of rules. Testing means checking that your package follows them and that the LMS interprets your course's data the way you expect.
What Should You Check in the Manifest?
The manifest, imsmanifest.xml, is the file the LMS reads first, so start there. The SCORM content packaging guide is the reference for what the LMS expects. Two rules matter most for testing: if the manifest is not at the top level of the zip, the upload fails, and if a file the course calls is missing from the package, a screen breaks after launch.
Work through this SCORM testing checklist for the package itself:
- Unzip the package. The manifest should appear at the top level, not inside a subfolder.
- Open the manifest in a browser or XML editor. If it does not parse as XML, the LMS will reject it.
- Check the schema version in the metadata. It should match the SCORM version you meant to publish.
- Find the launch file in the resource entry and confirm it exists at that exact path, with the same capitalization. Many web servers treat Index.html and index.html as different files.
- Look for file names with spaces, accented letters or unusual symbols, which some servers handle poorly.
- Check for absolute paths or links that point outside the package.
- If the manifest defines a mastery score or passing score, confirm it matches the pass mark in the course.
- Note the zip size. A very large package may hit an upload limit, so ask the LMS admin what theirs is.
Which SCORM API Calls Should You Watch?
All of them, but a few deserve close attention. A SCORM course talks to the LMS through a small JavaScript API: it initializes, reads values, writes values, commits and terminates. A test tool that logs those SCORM API calls shows the whole conversation. The SCORM run-time reference lists every data model element and its allowed values, which is the yardstick for the log.
A healthy session follows a predictable shape:
Initialize("") -> true
GetValue("cmi.entry") -> ab_initio
GetValue("cmi.suspend_data") -> ""
SetValue("cmi.location", "slide-07") -> true
SetValue("cmi.suspend_data", "...") -> true
SetValue("cmi.score.scaled", "0.85") -> true
SetValue("cmi.completion_status", "completed") -> true
SetValue("cmi.success_status", "passed") -> true
SetValue("cmi.exit", "normal") -> true
Commit("") -> true
Terminate("") -> true
That example uses SCORM 2004 names; a SCORM 1.2 course uses LMSInitialize, LMSSetValue and fields such as cmi.core.lesson_status instead. In either version, look for these warning signs:
- Any call that returns "false", or a non-zero error code from GetLastError.
- Values outside the allowed vocabulary, such as "complete" instead of "completed".
- Initialize called twice, or calls made after Terminate.
- No Commit before the session ends.
- Suspend data that grows close to its limit as the course goes on.
How Do You Test a SCORM Package for Scores, Status and Resume?
Run a fixed set of scenarios and compare the log with the result you expect. Writing the expected results down first keeps the test honest. Here is a starting matrix for a quiz course with an 80% pass mark, using SCORM 2004 terms:
| Scenario | What you do | Expected result |
|---|---|---|
| Pass | Finish and score 90% | Completed, passed, scaled score 0.9 |
| Fail | Finish and score 60% | Completed, failed, scaled score 0.6 |
| Partial | Stop halfway, close the browser | Incomplete, exit suspend, location saved |
| Resume | Relaunch after the partial run | Entry resume, returns to the saved slide |
| Retry | Fail, then retake and pass | Final status passed, per your retry rules |
For a SCORM 1.2 course, replace the status column with the single value your publish settings should produce, such as "passed" or "failed" in cmi.core.lesson_status.
A tool that shows these calls without an upload makes the matrix quick to run. AuthorLearn Studio includes a built-in LMS test harness that shows every SCORM API call without uploading anything, and its preview debug panel shows LMS calls alongside variables and trigger events. You still confirm the results in your own LMS. The 30-day free trial is on the download page, though the trial cannot publish, save or export.
What Changes When You Test Inside the Real LMS?
The environment changes, and the environment causes its own failures. Once the local tests pass, upload to an LMS sandbox or test area and repeat the pass, fail and resume scenarios. Pay attention to:
- Launch behaviour. The LMS may open the course in a frame or a new window, and pop-up blockers can stop it.
- Attempt settings. Some LMS settings start a new attempt on every launch, which breaks resume regardless of the course.
- Completion rules. The LMS may require both completed and passed before marking the enrolment done.
- Reports. Check that the report columns show what the course sent.
- Browsers and devices. Test at least two browsers and, if learners use them, a tablet or phone.
- The account. Use an ordinary learner account, never an admin account, which may bypass restrictions.
When something differs from your local result, the API log from the local run tells you whether the fault is in the course or in the LMS configuration. That evidence makes the conversation with the LMS administrator much shorter.
For SCORM troubleshooting, a simple record helps more than memory. Keep a short log for each test run with the date, the package version, the browser, the scenario and the result, and attach the API log when something fails. When an issue reappears months later, as issues tend to, that record shows whether it is a regression in the course or a change in the LMS.
Functional testing is only half of a release check. The other half is making sure every learner can use the course, and that pass gets its own walkthrough in accessibility checks before you publish.
A Tested Package Saves an Awkward Call From the LMS Admin
To test a SCORM package properly, check the manifest and zip structure, read the API log for a full session, run a short matrix of pass, fail, partial, resume and retry scenarios, and then repeat the key scenarios in an LMS sandbox with a learner account.
None of these steps is difficult. Together they catch most of the problems that would otherwise surface as a puzzled support ticket. Keep the matrix and the expected results with the course files, and run them again each time you republish. After three clean releases in a row, the LMS administrator will probably stop opening your packages with a sigh.
