Alternatives to testing your SCORM Packages
When developing eLearning modules, there is a final component that I usually test before handing the files to the client (of course, it depends on the requirements) and it’s the capability of the module to report completion, score and bookmarking to the LMS.
It is not the most complicated nor the easiest task to complete, but you’ll need to keep a few things in mind to have a smooth experience:
Have an LMS available
Have a SCORM Cloud account
Have a SCORM Testing tool
Ideally, you should have an LMS available that is very similar (or the same) to the LMS where the eLearning module is going to be deployed. Of course this is something that is not always possible (almost never) since not all the clients have a sandbox available (it is important to test in a sandbox environment as to not affect the files on the production site), but you can always use your own LMS, either on a sever or in your local machine. This will, at least, give you the idea if the module is working as a SCORM package and if it reports to the LMS.
Another option is to use SCORM Cloud. From a performance point of view, this should always be your go to, since this website (provided the developers of the SCORM standards) will always show the most accurate performance of the eLearning module in a LMS environment. You can create an account on the SCORM Cloud website, but with a free account, you have a file size limit of 100 MB at any time in your realm.
Finally, another option is to use a testing tool, such as RELOAD SCORM Player. This is not considered an LMS, but the advantage that this tool gives you is that you can see exactly what data is being reported back to the LMS, including bookmarking data and, very important, is that it runs locally without having to install a local server. The only disadvantage I have found so far, is that it only runs SCORM 1.2 eLearning modules.
