Validator¶

Tools → RevGaming → RevLearning → Validator.

An editor window for checking a package and a live session before you hand either to a customer. LmsValidatorWindow is the whole folder.

What it is for¶

The failures this catches are the ones that only appear on a real LMS: an API that was never found, a write the LMS refused, a suspend payload over the limit, a status that did not land where you expected. In the Editor everything succeeds, because the stub accepts everything — which is what makes the stub useful for building a course and useless for validating one.

Run it inside a WebGL build hosted on the LMS and it reports what the LMS actually said.

The static half runs in CI¶

The window is the interactive half. The offline half is Tests~/tools/validate-package.py, which checks a generated zip's structure and manifest, and it runs on every push against packages built by ScormBuildSmokeTests — so a packaging regression fails a pull request rather than an upload.

Tests~/CONFORMANCE.md has the live checklist this window was built to work through, the results from the SCORM Cloud run against this release, and the steps that run did not cover.

A note on what it found¶

The validation panel shipped for a while able to record only a correct answer. That made one of the audit's own findings — about incorrect-answer vocabulary — impossible to confirm by any live run, which is the kind of gap a validator is supposed to close rather than create. Worth knowing if you are extending it: a validator that cannot produce the failure case cannot validate the failure case.