Introduction

The Army DL Product Acceptance Criteria specifies the process for testing and certification of Army SCORM conformant courseware to be deployed on the Army’s learning management system ATIS Learning. The process can be summed up in three simple steps: SCORM conformance testing, RCC testing, and ATIS Learning CTE testing. The entire process is for producing evidence that your courseware meets the requirements of Army DL Business Rules and Best Practices (BRBP) and Acceptance Criteria. IMI courseware must be certified by VPDE before deployment on ATIS Learning for group trials and functional testing.


Figure 1. SCORM courseware testing process


Note that in order to run tests on Army learning platforms, you need to gain access to Rustici Content Controller (RCC) and ATIS Learning Content Test Environment (CTE). Refer to Acceptance Criteria Appendix L for the detailed steps to acquire the permission.

Access ATIS Learning CTE and Rustici Content Controller (RCC)
On ATIS Learning PROD, complete four (4) role based training courses Attempt to access both ATIS Learning CTE and RCC Email usarmy.jble.usaac.list.dls-alms-customer-service-center@army.mil with your role and organization to request access After successful login, email usarmy.jble.usaac.list.dls-alms-customer-service-center@army.mil to confirm access

Table 1: Steps to access ATIS Learning CTE and RCC

Three (3) Important Tests

You must conduct the following tests for your courseware before each group trial and function testing.

SCORM Conformance Testing: upload and test your courseware package using the Army SCORM 2004 3rd Edition Conformance Test Suite (ACTS) at https://acts.dldart.org. ACTS will verify the courseware package meets the requirements laid out in the Army Business Rules and Best Practices for Distributed Learning Development Guide (BRBP). If your courseware fails the ACTS test, the package must be fixed and re-tested.

Rustici Content Controller (RCC) Testing: upload the courseware to RCC and test the package using its Test feature (AC Appendix F). For non-assessment packages, both incomplete and complete pathways must be captured. For assessment packages, fail and passed pathways must be captured. Save the debug logs and upload them to the RCC Debug Log Analyzer (RCC-DLA) at https://tools.dldart.org/rcc-debug-log/. The debug log analysis report will display whether all the required SCORM API calls have been made in the tests.

ATIS Learning CTE Testing: Make sure you have taken the ATIS Learning Role Based Training on ATIS Learning Production and consult the training materials and Quick Reference Guide as you create and test the course on ATIS Learning. The table below outlines the steps to configure and test your courseware on the ATIS Learning CTE.

ATIS Learning CTE Configuration & Testing

Create a topic Create a new topic and a new learning assignment under the topic Add your courseware’s proxy package as a SCORM package activity under the learning assignment you created Configure the Completion Conditions and Restrict Access settings of the SCORM package activity. Create and publish a single topic course for your courseware testing Create a new course and a template. Create a new course iteration. Publish the course iteration and the course . Enroll yourself and other testers in the published course. Test the course with the student role. Find the published course from Your Courses. Enter the course and then enter the topic. Switch your user role to Student. Test the courseware and take screenshots required in accordance with Acceptance Criteria Section 2.7.

During the CTE testing, ensure your package rolls up properly and displays the correct completion status (incomplete/complete, failed/passed). Take screenshots for all completion statuses.

Submission for Certification

After completing ATIS Learning CTE testing and ensuring your courseware functions as intended, fill out the appropriate developer checklist (AC Appendix A or B) and submit the courseware for certification in support of group trials. Group trials ensure the courseware has all requested features and content and functions as the proponent desires. If the courseware does not pass group trials, it must be modified and the process must be restarted.

After the group trial and upon completion of required revisions, you will submit your updated courseware and supporting documentations for certification in support of ATIS Learning functional testing. Functional testing ensures the courseware has all necessary functionality and will not cause errors on ATIS Learning production (PROD). Functional testing may find Criticality Level 1, 2, and 3 errors. More information on these errors can be found in the AC Appendix J. Criticality Level 3 errors are not required to be fixed for final submission, but the proponent may request these to be corrected. In the case of critical errors requiring package modification, the AC process must be restarted.

Once the courseware has successfully passed functional testing, it can be submitted for final delivery. For contracted developers, information on Final Gold Delivery of courseware can be found in AC Section 3.3 “Final Courseware Delivery for Contractors ONLY.”

Help

If you need assistance with any part of this process, the DART Team can help. Submit a request for assistance at https://cars.dldart.org.

References

1. Army Business Rules and Best Practices for Distributed Learning Courseware Development Version 4.0
2. Army Acceptance Criteria for Distributed Learning Products
3. Rustici Content Controller User Guide
4. ATIS Learning Quick Reference Guides
5. Moodle Documentation
6. Criticality Levels