Skip to content
Alder

How to test a SCORM package without an LMS

Updated 16 October 2026

Quick answer

Run the course in a test player that plays the part of an LMS, so you can see the calls it makes and what would be recorded. SCORM Cloud is the usual reference; free in-browser players such as Nate Stoker's SCORM Viewer show the raw calls; Alder runs the zip in your browser, explains each call in plain English and predicts what an LMS would record. Then try one test learner in your real LMS. How to test in Alder.

Why opening the course on your computer isn't a test

A SCORM course reports to the LMS through a connection the LMS provides (the SCORM API). Open its launch file from your computer and there is nothing to connect to: the slides play, but nothing is recorded, and many courses show a message such as “Unable to acquire LMS API”. Some things only work in an LMS anyway: Articulate notes that Storyline's exit trigger never works when the course runs from a local disk. To test tracking, you need something that answers the course's calls the way an LMS would.

Test your course in Alder (free)

  1. Drop the published zip

    Open Alder and drop the zip your authoring tool made. It is opened in your browser tab; nothing is uploaded.

    Alder's drop zone: Drop your published .zip here. SCORM, xAPI or cmi5. Opened in this tab only. Nothing is uploaded. A Choose a .zip file button and a Try a sample course link.
    No zip handy? The sample course shows every step.

  2. Read what Alder found

    The answer at the top says whether the zip is ready to upload. Each problem card says what happens to learners, why, and how to fix it in your authoring tool.

  3. Launch it and click through as a learner

    Click “Launch the course”. While you click, “What has happened so far” sums up the course's calls, and “Download log for your LMS admin” saves every one.

    What has happened so far, seen by Alder in this test: the course connected to the LMS, saved the learner's progress twice and reported incomplete at 0:00. Buttons: Download log for your LMS admin, Copy summary for email.

  4. Press “I’m done” and read the record

    “What an LMS would record” shows the result. Choose your LMS under “Uploading to” to see whether it would record the same.

    What an LMS would record after the sample quiz is passed: Finished yes (completed), Passed, Score 80, next time Review mode. Worth checking: Moodle would record it differently.
    The prediction after a test run of Alder's sample course.

  5. Test as a returning learner

    “Test as a returning learner” reopens the course with what it saved, to check that it picks up where you left off.

Where Alder fits

Alder does the checking and the playing in one place, in your browser, and then explains. All of this is free:

  • Every check on the zip and the manifest, each with what to change.
  • A test player where Alder plays the LMS, with a call log that says what each call means (“The course told the LMS the learner passed”) next to the raw call.
  • “What an LMS would record”: finished, passed, score and what happens next time. We tested this on SCORM Cloud in September 2026: after the fixes those runs led to, Alder's prediction matches what SCORM Cloud, with its default settings, recorded for every test scenario we ran there and for the five real courses we compared.
  • Whether seven LMSs would record the same result (one dot each), and the notes for SAP SuccessFactors, Moodle and Workday once you choose one under “Uploading to”. Any LMS problem marked “Must fix” is shown free too. The “Why?” behind each dot, and the other notes for Cornerstone, Canvas, Docebo and TalentLMS, are part of Pro.
  • The saved-progress (suspend_data) meter, a returning-learner test and a report.

What Alder can't do: it runs in your one browser, so it can't reproduce Safari or iPad problems, your LMS's own pop-up windows or your network. It plays one SCO (one tracked part) at a time and doesn't run SCORM 2004 sequencing between them. And its LMS results are predictions, not your LMS.

What each kind of tool shows

A hosted test LMS: SCORM Cloud. Rustici's SCORM Cloud is the reference most forum advice points to. You upload the zip, launch it, and read what it recorded and its debug log (see how to read it). It needs an account and an upload of your course, and the free trial has limits on courses, registrations and storage. It is also one LMS with its own defaults: it saves data on a timer rather than waiting for the course to save (Rustici), and by default it keeps a SCORM 1.2 course's own “passed” even when the score is below the manifest's mastery score, which Moodle, by default, does not. So passing there is a good sign, not a guarantee.

Cybercussion's SCOBot Platform (once SCOBot Playground) is another hosted option: you sign in, play a package, and get a report on problems such as oversized saved progress.

Free in-browser players with an API log. Tools such as SCORM Lab and Nate Stoker's SCORM Viewer play a package and list every call (SCORM Lab asks for an email code before it plays your own package). They show exactly what the course sent. Reading it is mostly up to you, so they suit people who already know the SCORM data model.

Validators that check the zip without playing it. Checkers such as Sodium Learn's SCORM validator look at the zip's structure and its manifest without playing the course. That catches upload errors quickly, but not what happens once a learner starts. See free SCORM validators compared.

A free LMS. Moodle, or TalentLMS's free plan, gives you a real LMS result. It takes setting up, it doesn't explain what went wrong, and it only tells you about that one LMS.

A testing order that works

  1. Check and play the zip in Alder before you upload it, and fix what it finds.
  2. If you want the reference record, or your client asks for it, run it in SCORM Cloud.
  3. Before rollout, try one test learner in your real LMS.