Skip to main content

Historical recorded test

SCORM Cloud (Rustici): compatibility evidence

124 of 124 flag-pack checks passed on the reference platform. This historical result covers its recorded build and test scope; each new release still needs its own regression evidence.

Test environment

Platform version
v2 test API; runtime engine version not captured
Test date
2026-07-20
Intle build
bcbde6a
Browser
Browser version not recorded in the retained summary
Editions
SCORM 2004 4th Edition and 1.2
Fixture
Baseline packages a–d and 24 flag-pack runs

Record reviewed 2026-09-30. This review date does not change the original test date or tested build.

Expected and observed results

Recorded behaviours for SCORM Cloud (Rustici)
BehaviourExpectedObserved
Baseline import and launchOpen the packaged learner viewCompliance and quiz launched in both editions; 2004 media and dual-SCO review packages launched
Timer and feedbackRetain accommodations and render feedback20/20 timer-feedback and 8/8 strict-timer checks passed
Experience and adaptive reviewRetain dismissal and route review16/16 experience and 8/8 adaptive-panel checks passed
Rich activity packsRender activity markup without page errors72/72 checks passed across 18 packages; full answer correctness was not tested
Quiz resumeRestore saved learner positionBoth editions resumed after a suspend-data persistence defect was fixed in the tested build

Evidence limits

  • Exact engine/browser versions and per-package hashes were not captured in the public summary.
  • This does not validate another LMS, current production, all generated content or learning effectiveness.
  • Optional Intle analytics collection and verified learner identity were outside this run.

Packages and your own test

Exact tested ZIPs are not available for this record. Try current sample packages; these samples do not inherit this record's result.

  1. Record your LMS/server version, browser, Intle build and ZIP hash.
  2. Import into a test course and launch using a test learner.
  3. Submit correct and incorrect responses; inspect score and completion in the LMS.
  4. Exit midway and resume the same attempt; check position and answers.
  5. Check media, keyboard use, mobile layout and your institution's network restrictions.
  6. Save screenshots and actual results; note exclusions before rollout.

An export is a frozen copy. Edit the Intle source, export again and replace the LMS upload when publishing revisions.

Hosted and LMS delivery guide · Discuss your configuration