SCORM Test Track
Course Data

The Course Data section of the SCORM Test Track homepage shows some of the aggregate information that would be likely to show up in any LMS.
Test Track

WELCOME!

While this page is still here, Test Track has moved. It’s joined the SCORM Cloud neighborhood as one of the features of that awesome product. Same ability to test content, just a new location. Get an account today or log in and get started. Your old Test Track login should work just fine.


Front and Center

Front and center on the SCORM Test Track homepage you’ll find the course status. As a user of a course or an author, the data found here is fundamentally important. As you click through your course, you want to be sure it’s getting these things right.

tt-anatomy

  • Completion Status: Has the user completed the course? This requires that you, as a tester, know what the content expects of you.
  • Success Status: Success differs from completion in that it’s looking for a passing score or a similar concept of mastery. This is an area of confusion for content authors as well. Some will use completion alone, or success alone. This is also confusing because SCORM 1.2 and SCORM 2004 handle these concepts very differently.
  • Total Time: As stated, the total time spent amongst all of the sub elements of the course.
  • Score: If available, the score is an aggregate of the SCO’s scores. In 1.2, the combination of the scores in controlled by the rudimentary rollup package properties. In SCORM 2004, it’s controlled by the rollup rules found in the manifest.

tt-coursestatus

These items are so important because they translate… learners understand them, managers understand them. If a piece of SCORM content fails to communicate the basic data points accurately, then it will likely fail in other ways as well. They serve as a great bellwether.

For further detail, click on “View Detailed Report” in SCORM Test Track. This report will provide a comprehensive view into the current state all of the available SCORM tracking data.

Next -> Debug Logs