Editing the QUnit tests

QUnit tests are not set in stone.

You may find certain tests failing that are otherwise working locally.

Whats the difference?

SCOBot includes a light-weight local mimic of the API_1484_11 for SCORM 2004. This comes pre-baked with some default settings. Your imsmanifest.xml may include 'minNormalizedMeasure' or 'completionThreshold' values which equate to 'cmi.scaled_passing_score' and 'cmi.completion_threshold'. More direct, this means the content may be packaged with a different completion or scaled score needed to be completed and passed. Therefore the tests can fail because completion is reporting 'completed', when the Unit test was looking for 'incomplete'. Launch data could not be present. Or it is, and its just different than whats being tested.

These are meant to be edited

Fine tune your own tests. You may only be setting score and success/completion status. No need to test interactions and objectives then. Feel free to even write your own Unit tests that follow your scoring and progress protocols.

Cosmetic Fails vs Actual issues

Could be as simple as timezone/offset issues testing date formats. Could even be the time it takes a really old browser to translate a ISO8601 Duration back into a date object, and its milliseconds off. These aren't show stoppers, but its meant to highlight differences.