1. A common Content Aggregation Model which includes Content Packaging.
2. A common specification for a Run-Time Environment (RTE) that facilitates interoperable communication between Learning Management Systems (LMS) and course content components.
3. A common representation of content aggregation, sharable content object (SCO), asset, and package meta-data that can be utilized to promote discoverability and reuse.
   
   

1. LMS Run-Time Environment Conformance Test.
2. Sharable Content Object (SCO) Run-Time Environment Conformance Test.
3. Meta-Data Conformance Test
.
4. Content Package Conformance Test.
   
   

• Launch known conformant Sharable Content Objects (SCOs)
  
  
• Support the Application Program Interface (API) functions defined in the SCORM
  • LMSInitialize("")
  • LMSFinish("")
  • LMSCommit("")
  • LMSGetValue("datamodel.group.element")
  • LMSSetValue("datamodel.group.element","value")
  • LMSGetLastError()
  • LMSGetErrorString()
  • LMSGetDiagnostic()
    
    
• Determine if all mandatory data model elements are implemented correctly by the LMS
  
  
• Determine which optional data model elements are supported by the LMS and implemented correctly.

• Can be launched by a known conformant LMS
  
  
• Supports the Application Program Interface (API) functions defined in the SCORM
  
  Required
  • LMSInitialize("")
    
    
  • LMSFinish("")
    
    
  Optional
  • LMSCommit("")
  • LMSGetValue("datamodel.group.element")
  • LMSSetValue("datamodel.group.element","value")
  • LMSGetLastError()
  • LMSGetErrorString()
  • LMSGetDiagnostics()
    
    

• Required
  • Is a well-formed XML document;
  • Validates against the IMS Meta-data Version 1.2.1 Schema;
  • Implements all mandatory elements correctly;
    
    
• Optional
  • Uses optional elements correctly.
  • Uses extensions.
    
    

• Correct use of repeating elements (i.e. multiplicity).
  • A WARNING will be logged for any element exceeding the smallest permitted maximum number of supported instances.
  • An ERROR will be logged for any mandatory element that is not used.
  • An ERROR will be logged for any element exceeding one (1) instance for those with a multiplicity of "0 or 1" or "1 and only 1" (Note: This causes XML validation errors).
    
    
• Correct use of "langstring" and "datetime" elements
  • An ERROR will be logged for any element that does not bind all data within a "langstring", where explicitly defined (Note: This causes XML validation errors)
  • An ERROR will be logged for any element that contains multiple "langstring" elements that do not contain different xml:lang attribute values.
  • A WARNING will be logged for any "datetime" element that does not adhere to the "International Standard Date Notation (yyyy-mm-dd)" or the "International Standard Notation for the Time of Day (hh:mm:ss)" (See below for details)
    
    
• Adherence to "restricted vocabularies"
  • An ERROR will be logged for any element that is not part of the restricted vocabulary list
    
    
• Adherence to "best practice vocabularies"
  • A WARNING will be logged for any best practice vocabulary element that does not contain 'LOMv1.0' as the source of the VocabularyType.
  • A ERROR will be logged for any best practice vocabulary element that specifies 'LOMv1.0' as the source of the VocabularyType but does not contain a valid best practice vocabulary token as a value of the VocabularyType.
    
    
• Adherence to the smallest permitted maximum number of characters
  • An WARNING will be logged for any element that exceeds the smallest permitted maximum number of characters allowed
    
    
• Element 4.2 "size" must be given in a numeric format (i.e. bytes)
  • An ERROR will be logged for element 4.2 "size" if it is not represented in a numeric (integer) format (Note: This causes XML validation errors).
    
    

• Correct use of "vcard" elements
• Correct use of Universal Resource Locator (URL) or Universal Resource Identifier (URI)
• Adherence to ISO 639/3166 standard for describing elements 1.4, 3.5, 5.11 - "language"
• Adherence to the current MIME types available
  
  

• A WARNING will be logged for all "datetime" elements that do not use the following formats:
  • "International Standard Date notation" (yyyy-mm-dd)
  • "International Standard for the Time of Day" (hh:mm:ss)

• Contains an imsmanifest XML document at the root of the content package that:
  • Is well-formed;
  • Validates against the ADL Content Packaging Version 1.2 Schema;
  • Implements all mandatory elements correctly;
  • Uses optional elements correctly;
  • Optionally uses extensions.
    
    
• Contains all supporting schema definition files at the root of the package.
  
  
• Contains conformant Asset, SCO, Content Aggregation, and Package Meta-data as determined by the Meta-data Conformance Test.
  
  
• Contains conformant SCOs as determined by the SCO RTE Test.
  
  

• Correct use of repeating elements (i.e. multiplicity).
  • An ERROR will be logged for any mandatory element that is not used.
  • An ERROR will be logged for any element exceeding one (1) instance for those with a multiplicity of "0 or 1" or "1 and only 1" (Note: This causes XML validation errors).
    
    
• Adherence to "restricted vocabularies"
  • An ERROR will be logged for any element who's value is not part of the restricted vocabulary list.
    
    
• Adherence to the smallest permitted maximum number of characters
  • An WARNING will be logged for any element that exceeds the smallest permitted maximum number of characters allowed.
    
    
• Correct use of Timespan data types
  • A ERROR will be logged for any element with a Timespan data type that does not adhere to the format (hhhh:mm:ss.ss) as specified in the SCORM Content Packaging Information Model and XML Binding.
    
    
• Correct use of ID data types
  • A ERROR will be logged for any element with an ID data type that is not unique within the manifest.
    
    
• Correct use of IDRef data types
  • A ERROR will be logged for any element with an IDRef data type that does not reference a defined ID.
    
    
• Correct use of location/href
  • A ERROR will be logged for any element with an href attribute or location that does not reference an existing File or URL.
    
    

Constraints

Prerequisites

Installation

1. Please remove all ADL schemas (schemas that are not extensions to the SCORM) from your desktop.
2. Double-click on the downloaded self-extracting executable file to begin the installation process
3. Click the "Next" button to continue from the "Welcome" page.
4. Read the "License Agreement" and
   • Click the "I accept the terms in the license agreement" radio button to agree and continue with the install
   • Click the "I do not accept the terms in the license agreement" radio button if you do not agree with the terms of the license and wish to exit the install
   Then click the "Next" button.
5. If a previous version of this software is installed, the setup will spawn the Uninstall routine to uninstall any previous version. This routine will walk through the steps to uninstall.
   Note: Having this version and a previous version installed simultaneously may cause unpredictable results.
6. The recommended root installation directory is "C:\ADL".  You may choose another root installation directory, but the Test Suite install will always append the "\TestSuite1_2_7" sub-directory to the specified root installation directory.  The remainder of this readme document assumes that the Test Suite will be installed to "C:\ADL\TestSuite1_2_7".  If you override the default to use a different root installation directory, please take that into consideration when reading the remainder of this readme.  Verify or change the installation directory, then click the "Next" button
7. If you would not like to view a copy of this readme document, Click on the "Show the readme file" checkbox to un-check
8. Click on the "Finish" button to complete the installation.
   
   

• A link to www.adlnet.org
• A shortcut to this readme document
• A shortcut to the Test Suite
  
  

Un-Installation

• The Windows Control Panel "Add/Remove Programs" feature can be used.
  1. Choose Start/Control Panel
  2. Choose Add/Remove Programs
  3. Highlight the ADL SCORM® Version 1.2 Conformance Test Suite Version 1.2.7 (Self Test)
  4. Choose "Remove"
  
  
• If the Test Suite is already installed, running the install again will uninstall the software. This method will not re-install the Test Suite. You will need to run the self-extracting executable after un-installing to accomplish a re-installation.

• Step 1 - Import ADL SCORM Test Course I
  
  The Test Content Package located at:
  C:\ADL\TestSuite1_2_7\TestSuite\LMSRTE\Courses\LMSTestCourse01.zip
  should be imported into the Test Subject LMS.
  
  Understanding the hierarchy and order of the SCOs as described in the provided <organization> of the Manifest found in the Content Package is critical for correctly configuring the test course within the test subject LMS.  The Manifest (imsmanifest.xml) document can be viewed using an XML editor or a general-purpose text editor, such as Windows Notepad.
  
  The contents of this course are located in this zip file at Lesson01\Resources and includes the following:
  
  
  • sco01.htm  (Sharable Content Object 01)
  • sco 02.htm  (Sharable Content Object 02)
  • sco03.htm  (Sharable Content Object 03)
  • sco04.htm  (Sharable Content Object 04)
  • sco05.htm  (Sharable Content Object 05)
  • sco06.htm  (Sharable Content Object 06)
  • sco07.htm  (Sharable Content Object 07)
  • sco08.htm  (Sharable Content Object 08)
  • sco09.htm  (Sharable Content Object 09)
  • lmsrtefunctions.js  (A file containing several javascript functions that are used in all of the SCO htm files.)
  • testsuite.jar  (java archive) file containing several java classes that are used by the test SCOs.
  • sco*.xml  (SCO Meta-data for each SCO) are located in this zip file at Lesson01\Meta-data
    
    
  NOTE:  The sco*.htm files expect the testsuite.jar file and the lmsrtefunctions.js file to be in the same location as the htm files at run-time.  Please make sure that you upload these files to the appropriate location when importing your course! It is critical for Run-time API execution that the SCOs be launched from the same URL domain as the LMS.  The test SCOs use JavaScript to locate the LMS's API adapter object, which requires the use of cross frame and/or cross window scripting.  For security reasons Microsoft Internet Explorer requires that content that performs cross frame or cross window scripting be loaded from the same domain.  See  http://msdn.microsoft.com/workshop/Author/om/xframe_scripting_security.asp  for more information.
  
  
• Step 2 - Import ADL SCORM Test Course II
  
  This step is similar to Step 1.
  
  The Test Content Package located at:
  C:\ADL\TestSuite1_2_7\TestSuite\LMSRTE\Courses\LMSTestCourse02.zip
  should be imported into the Test Subject LMS.
  
  Understanding the hierarchy and order of the SCOs as described in the provided <organization> of the Manifest found in the Content Package is critical for correctly configuring the test course within the test subject LMS. The Manifest (imsmanifest.xml) document can be viewed using an XML editor or a general purpose text editor, such as Windows Notepad.
  
  The contents of this course are located in this zip file at Lesson01\Resources and includes the following:
  
  
  • sco01.htm  (Sharable Content Object 01)
  • sco02.htm  (Sharable Content Object 02)
  • sco03.htm  (Sharable Content Object 03)
  • lmsrtefunctions.js  (A file containing several javascript functions that are used in all of the SCO htm files.)
  • testsuite.jar  (java archive) file containing several java classes that are used by the test SCOs.
  • sco*.xml  (SCO Meta-data for each SCO) are located in this zip file at Lesson01\Meta-data
    
  
  NOTE:  The sco*.htm files expect the testsuite.jar file and the lmsrtefunctions.js file to be in the same location as the htm files at run-time.   Please make sure that you upload these files to the appropriate location when importing your course!  It is critical for Run-time API execution that the SCOs be launched from the same URL domain as the LMS.  The test SCOs use JavaScript to locate the LMS's API adapter object, which requires the use of cross frame and/or cross window scripting.  For security reasons Microsoft Internet Explorer requires that content that performs cross frame or cross window scripting be loaded from the same domain.  See   http://msdn.microsoft.com/workshop/Author/om/xframe_scripting_security.asp  for more information.
  
  
• Step 3 - Enroll a student in ADL SCORM Test Course I
  
  The purpose of this step is to enroll or register a fictitious test student for ADL SCORM Test Course I. The student's name must be registered as "Joe Student" (first name: Joe, last name: Student).
  
  The SCORM Version 1.2 Run-Time Environment Data Model supports a "credit/no-credit" feature in the form of the cmi.core.credit data model element.  How the value of cmi.core.credit is determined by an LMS's implementation is outside the scope of the SCORM specification and LMS Conformance Test. Assure that this test student is registered for the course and all of its SCOs for credit (i.e. a value of "credit" will be returned for the cmi.core.credit data model element).
  
  The SCORM Version 1.2 Run-Time Environment Data Model also supports the ability for LMSs to operate in "browse", "review", and/or "normal" modes in the form of the cmi.core.lesson_mode optional data model element.  Whether an LMS implements this optional element and how an LMS determines the value of this element are outside the scope of the SCORM specification and the LMS Conformance Test.  If the test subject LMS supports the "Mode" feature, assure that this student is registered for this course such that the student experiences all SCOs in "normal" mode (i.e. a value of "normal" is returned by the LMS for the cmi.core.lesson_mode"data model element).
  
  Note: It is permissible to create a "class", "session" or other type of student grouping if required by the LMS for the registration of the student for this course.
  
  
• Step 4 - Enroll a student in ADL SCORM Test Course II
  
  The purpose of this step is to enroll or register a fictitious test student for ADL SCORM Test Course II.  The student's name must be registered as "Mary Learner " (first name: Mary, last name: Learner).
  
  The SCORM Version 1.2 Run-Time Environment Data Model supports a "credit/no-credit" feature in the form of the cmi.core.credit data model element.  If the LMS supports the ability to register the student for a course (or SCOs) for "no-credit", assure that this test student is registered for the course and all of its SCOs for no-credit (i.e. a value of "no-credit" will be returned for the cmi.core.credit data model element).
  
  The SCORM Version 1.2 Run-Time Environment Data Model also supports the ability for LMSs to operate in "browse", "review", and/or "normal" modes in the form of the cmi.core.lesson_mode optional data model element.  If the test subject LMS supports the "Mode" feature, assure that this student is registered for this course such that the student experiences all SCOs in "browse" mode (i.e. a value of "browse" is returned by the LMS for the cmi.core.lesson_mode "data model element).
  
  Note: It is permissible to create a "class", "session" or other type of student grouping if required by the LMS for the registration of the student for this course.
  
  
• Step 5 - Take the ADL SCORM Test Course I
  
  Launch the LMS and log in as Joe Student.  After successfully logging in to the LMS as Joe Student, begin taking ADL SCORM Test Course I.
  
  If the LMS supports automatic sequencing of SCOs, the first SCO in the LMS Test Course should be launched when you begin the course.  If the LMS does NOT support automatic sequencing of SCOs, then manually select or navigate through each SCO in the sequence in which they are displayed using whatever mechanism is provided by the LMS (e.g. menu, back/next buttons, etc.).
  
  Each SCO contained in the Test Course will perform a specific testing function.  The final SCO in the course will provide an opportunity for "ad-hoc" LMS API testing.  This will allow you to issue API calls to the LMS in any order or manner you desire for the purpose of assessing the LMS's support of the SCORM Version 1.2 Run-Time Environment beyond the tests performed automatically by the preceeding SCOs.
  
  As the test progresses through each SCO, information about the actions being performed and their outcomes will be written to the test log.  You will be able to view any errors that may be encountered, as well as the step-by-step progression of the test.
  
  If a SCO encounters a problem communicating with the LMS, or an unexpected fatal error occurs and the testing software is not able to continue, the test will be stopped.  Whenever possible the test software will attempt to continue when conformance errors are encountered.
  
  
• Step 6 - Take the ADL SCORM Test Course II
  
  Access the LMS and log in as Mary Learner.  After successfully logging in to the LMS as Mary Learner, begin taking ADL SCORM Test Course II.
  
  If the LMS supports automatic sequencing of SCOs, the first SCO in the LMS Test course should be launched when you begin the course.  If the LMS does NOT support automatic sequencing of SCOs, then manually select or navigate through each SCO in the sequence in which they are displayed using whatever mechanism is provided by the LMS (e.g. menu, back/next buttons, etc.).
  
  Each SCO contained in the LMS Test course will perform a specific testing function.  The final SCO in the course will provide an opportunity for "ad-hoc" LMS API testing.  This will allow you to issue API calls to the LMS in any order or manner you desire for the purpose of assessing the LMS's API implementation beyond the tests performed automatically by the preceeding SCOs.
  
  As the test progresses through each SCO, information about the actions being performed and their outcomes will be written to the test log.  You will be able to view any errors that may be encountered, as well as the step-by-step progression of the test.
  
  If a SCO encounters a problem communicating with the LMS, or an unexpected fatal error occurs and the testing software is not able to continue, the test will be stopped.  Whenever possible the test software will attempt to continue when conformance errors are encountered.
  
  Upon Completion of this step, an indication of the conformance category achieved by the test subject LMS will be written to the log.
  
  
• Print Log:  This link has been removed from the log frame. Note: Printing can be accomplished by right-clicking in the log frame and choosing print. This will only print the Summary Log. If you want to print the Detailed Log, the link will need to be explored and printed using the browsers print feature.
  
  
• Save Log:  Clicking on this link will cause a "Save As" dialog box to appear. This allows the Tester to save the ADL SCORM Conformance Test Suite Log.  Note: Please, only provide a filename;  The extension is fixed as ".htm".  Note: The "Save Log" functionality saves the Summary Log only. The Detailed Log is automatically saved in following directory: C:\ADL\TestSuite1_2_7\TestSuite\LMSRTE\tempdir\LMSLogs\<yyyymmddhhmmss>_LMSRTE_Log.htm
  
• Add Comments:  Clicking on this link will cause a window to appear to allow the tester to add comments to the Test Suite Log.
  
  
• Log Legend. Clicking on this link will cause a window to appear describing the meaning of the colors and symbols used in the log.

1. The ability to use Netscape 4.7 is only tested for the SCO RTE Conformance Test.
2. If using Microsoft Internet Explorer, it is critical for Run-Time API execution that the SCOs be launched from the same URL domain as the LMS (Test Suite).  The SCOs being tested will likely use some sort of scripting language (i.e. JavaScript) to locate the LMS's API adapter object, which requires the use of cross frame and/or cross-window scripting.  For security reasons Microsoft Internet Explorer requires that content that performs cross frame or cross-window scripting be loaded from the same domain.  See http://msdn.microsoft.com/workshop/Author/om/xframe_scripting_security.asp
3. If using Netscape 4.7, SCOs may be tested remotely or from another domain.
   
   

• The test can be run on a Single Sharable Content Object or Multiple Sharable Content Objects.
  
  
• Single SCO Testing:
  
  
  1. Provide the SCO Name, SCO Version/Release Number and SCO Vendor/Developer information
  2. Click the "Continue" button
  3. Enter a timeout period (default is 20 seconds). This is the number of seconds the Test Suite will wait for a LMSInitialize(""). If the call is not made within this time, the Test Suite will end and the SCO will be deemed Non-Conformant.
     
     Note: If there is a possibility that the SCO may not call LMSInitialize("") in the first 20 seconds, this default value will need to be changed. No warning or error will be logged for changing this value.
     
     
  4. Click the "Continue" button
  5. Optionally, you may enter initialization values for any of the following elements: Student ID, Student Name, credit/no-credit, Lesson Mode, or Launch Data.  (These values are typically defaults that are provided by the LMS or via a Manifest.)
     
  6. Click the ;"Continue" button
  7. Make sure the  "Single SCO Test"  radio button is selected
  8. Click the ;"Continue" button
  9. Click the  "Browse"  button to select the SCO that will be tested
  10. Then click the  "Launch SCO(s)" button
  11. Follow the necessary steps that are presented by the SCO.
  12. Click the  "Complete Test" button to finish the test.
      
      
• Multiple SCO Testing:
  
  
  1. Provide the SCO Name, SCO Version/Release Number and Vendor/Developer information
  2. Click the ;"Continue" button
  3. Enter a timeout period (default is 20 seconds).  This is the number of seconds the Test Suite will wait for a LMSInitialize("").  If the call is not made within this time, the Test Suite will end and the SCO will be deemed Non-Conformant
     
     Note: If there is a possibility that the SCO may not call LMSInitialize("") in the first 20 seconds, this default value will need to be changed. No warning or error will be logged for changing this value.
     
     
  4. Click the ;"Continue" button
  5. Optionally, you may enter initialization values for any of the following elements: Student ID, Student Name, credit/no-credit, Lesson Mode, or Launch Data.  (These values are typically defaults that are provided by the LMS or via a Manifest.)
     
  6. Click the ;"Continue" button
  7. Make sure the  "Multiple SCO Test"  radio button is selected
  8. Press the  "Browse"  button to select the first SCO that will be tested
  9. Click the  "Add to List"  button to add the SCO to the list of SCOs
  10. Repeat steps 4 and 5 for all SCO's to be tested
  11. Then click the  "Launch SCO(s)" button
  12. Follow the necessary steps that are presented by the SCO.
  13. Click the  "Complete Test"  button to finish the test. This will then cause the next SCO in the list of SCOs to be launched.
      
      
• Once the  "Launch SCO(s)"  button is pressed the Test Suite will launch the selected SCO.
  
  
• The Test Suite will then wait for a call to LMSInitialize("").  The Test Suite will either wait for the call or the timeout period to expire (whatever comes first).
  
  
• The Test Suite will then wait for calls to any of the API functions listed above.
  
  
• Once the SCO RTE Tests surrogate LMS receives a call to LMSFinish(""), the SCO Test will either end (if testing) Single SCO or close the current SCO and launch the next SCO (if testing Multiple SCOs).  The "Complete Test" button should be pressed once the Self Test is complete. This will close the last remaining SCO window.
  
  
• The  "Abort Test" button should be used if a call to LMSFinish("") is not received from the SCO being tested.  The tester should wait for a period of time to see if the call will be invoked.  If not, the "Abort Test" button will send a call to LMSFinish("") and end the testing, marking the SCO as being Non-Conformant.
  
  
• At the end of a successful test the Test Suite will send to the Test Suite Log a set of supported features.  These indicate what SCORM features a SCO supports.  The SCORM features are as follows:
  
  
  API Support:
  • Find an LMS provided API Adapter
  
  
  Execution State:
  • LMSInitialize()
  • LMSFinish()
  
  
  Data Transfer:
  • LMSGetValue()
  • LMSSetValue()
  • LMSCommit()
  
  
  State Management:
  • LMSGetLastError()
  • LMSGetErrorString()
  • LMSGetDiagnostic()
  
  
  Data Model Support:
  • SCORM® Run-Time Environment Data Model
  
  
  
• Print Log:  In earlier versions of the Test Suite, a Print Log Link was provided in the Log frame.  This link has been removed from the log frame. Printing can be accomplished by right-clicking in the log frame and choosing print
  
  
• Save Log:  Clicking on this link will cause a  "Save As"  dialog box appear to allow the tester to save the Test Suite Log.  Note: Please, only provide a filename.  The extension is hard coded to be ".htm"
  
  
• Add Comments:  Clicking on this link will cause a window to appear to allow the tester to add comments to the Test Suite Log
  
  
• Log Legend. Clicking on this link will cause a window to appear describing the meaning of the colors and symbols used in the log.

• The test can be run on a Single Meta-data document
  
  
  1. Provide the Meta-data document Name, Meta-data document Version/Release Number and Vendor/Developer information
  2. Click the "Continue" button
  3. Choose the type of Meta-data to be tested (i.e. Asset, SCO, Content Aggregation, Package)
  4. Click the "Continue" button
  5. Press the "Browse" button to select the Meta-data document that will be tested
  6. Then select the "Begin Test" button
  
  
• Once the "Begin Test" button is pressed the Test Suite will check the meta-data for XML well-formedness
  
  
• Next, the Test Suite will validate the Meta-data against the XML Schema
  
  
• The Test Suite will then check the Meta-data for mandatory elements as well as the restrictions and rules that are described in the SCORM Content Aggregation Model of the SCORM
  
  
• The Test Suite will then check the Meta-data for use of optional elements as well as the restrictions and rules that are described in the SCORM Content Aggregation Model of the SCORM
  
  
• The Test Suite will then check the Meta-data for use of extension elements
  
  
• Lastly, the Test Suite will report the level of conformance reached by the Meta-data with the appropriate label
  
  
• Please Note:  Summary information about the actions being performed and their outcomes will be written to the Summary Log. The details of the test will be written to the Detail Log, which can be viewed by clicking on the link presented in the Summary Log. You will be able to view any errors that may be encountered, as well as the step- by-step progression of the test through the Summary and Detailed Logs.
  
  
• Print Log:  In earlier versions of the Test Suite, a Print Log Link was provided in the Log frame.  This link has been removed from the log frame.  Note: Printing can be accomplished by right-clicking in the log frame and choosing print. This will only print the Summary Log. If you want to print the Detailed Log, the link will need to be explored and printed using the browsers print feature.
  
  
• Save Log:  Clicking on this link will cause a "Save As" dialog box to appear. This allows the Tester to save the ADL SCORM Conformance Test Suite Log.  Please, only provide a filename;  The extension is fixed as ".htm".  Note: The "Save Log" functionality saves the Summary Log only. The Detailed Log is automatically saved in following directory: C:\ADL\TestSuite1_2_7\TestSuite\metadata\tempdir\MDLogs\<yyyymmddhhmmss>_MD_Log.htm
  
  
• Add Comments. Clicking on this link will cause a window to appear to allow the tester to add comments to the Test Suite Log
  
  
• Log Legend. Clicking on this link will cause a window to appear describing the meaning of the colors and symbols used in the log.

1. Provide the Content Package Name, Content Package document Version/Release Number and Vendor/Developer information
2. Click the "Continue" button
3. Select the type of test to be performed by selecting the appropriate radio button.  You can test a stand-alone manifest XML document, a Package Interchange File in the form of a PKZIP 2.0.4 (or compatible), or an uncompressed Content Package (on CD-ROM for example).
   
   Note: If the manifest radio button is selected, regardless of the test type, all referenced files must be present.
   
   
4. Select the type of ADL Content Package Application Profile to be tested (i.e., Content Aggregation Package or Resource Package) by pressing the appropriate radio button.
   
   
5. Press the  "Browse"  button to select the manifest or PIF zip file that is to be tested.
   
   
6. Once the  "Begin Test"   button is pressed the Test Suite will test the manifest and any referenced or in-line meta-data for conformance.
   
   
7. Any SCOs referenced by the manifest will be tested after the manifest test is complete. If any SCOs need testing, the test will continue with steps 4 - 6. Otherwise, testing is complete at step 3.
   
   
   • Enter a timeout period (default is 20 seconds). This is the number of seconds the Test Suite will wait for a LMSInitialize(""). If the call is not made within this time, the Test Suite will end and the SCO will be deemed Non-Conformant.
     
     
   • Optionally, you may enter initialization values for any of the following elements: Student ID, Student Name, credit/no-credit, Lesson Mode, or Launch Data. (These values represent defaults typically provided by the LMS or via a Manifest.).
     
     
   • Click the "Continue" button.
     
     
   • Click the "Launch SCO" button to launch the first SCO for testing.
     
     
   • After the first SCO has completed testing, click the "Complete Test" button to quit that SCO test.
     
     
   • Any following SCOs will be launched and tested once the "OK" button is clicked on the pop-up window.
     
     
   • The "Abort Test" button should be used if a call to LMSFinish("") is not received from the SCO being tested. The tester should wait for a period of time to see if the call will be invoked. If not, the "Abort Test" button will send a call to LMSFinish("") and end the testing, marking the SCO as being Non-Conformant.
     
     
8. Print Log:  In earlier versions of the Test Suite, a Print Log Link was provided in the Log frame. This link has been removed from the log frame. Printing can be accomplished by right-clicking in the log frame and choosing print. This will only print the summary log. If you want to print the detailed log, each link will need to be explored and printed using the browsers print feature.
   
   
9. Save Log.  Clicking on this link will cause a "Save As" dialog box to appear. This allows the Tester to save the ADL SCORM Conformance Test Suite Log.  Please, only provide a filename;  The extension is fixed as ".htm".  Note: The "Save Log" functionality saves the summary log only. The Detailed Log Folder is automatically saved in following directory: C:\ADL\TestSuite1_2_7\TestSuite\contentpackage\tempdir\Log_<yyyymmddhhmmss>
   
   
10. Add Comments.  Clicking on this link will cause a window to appear to allow the tester to add comments to the Test Suite Log
    
    
11. Log Legend. Clicking on this link will cause a window to appear describing the meaning of the colors and symbols used in the log.

Known Issues

• This version of the software has not been fully prepared for execution in Netscape. Netscape 6 and above can be used for the SCO RTE Conformance Test ONLY.
  
  
• It is critical for the LMS and SCO RTE Conformance Tests that the SCOs be launched from the same URL domain as the LMS.  The SCOs use JavaScript to locate the LMS's API adapter object, which requires the use of cross frame and/or cross-window scripting.  For security reasons Microsoft Internet Explorer requires that content that performs cross frame or cross-window scripting be loaded from the same domain.  See http://msdn.microsoft.com/workshop/Author/om/xframe_scripting_security.asp for additional information.
  
  
• Due to problems encountered with the Java 2 Run-Time Environment, the "Save Log" function will display an intermediate button that must be clicked in order to display the Save File dialog.  This button will appear in the top left portion of the screen.  Also note that the location the log will save to, by default, will be the user's home directory.
  
  
• Due to limitations with the Xerces XML parser, it is necessary to copy any necessary XML Schemas (.xsd files) to the Windows Desktop for both Meta-data and Content Package testing.
  
  
• The Meta-data and Content Package test is unable to test a content package or meta-data document using the http or ftp protocol.
  
  
• The ADL SCORM® Version 1.2 Conformance Test Suite Version 1.2.7 (Self Test) may not appear in the "Add/Remove Programs" menu. If it does not appear, use the second method for un-installing listed in the Installation section above.
  
  
• When saving the log during Content Package, Meta-data and LMS testing, only the summary log is saved. The summary logs contains links to detail logs that are located at:
  
  for LMS Testing
  C:\ADL\TestSuite1_2_7\TestSuite\LMSRTE\tempdir\LMSLogs\<yyyymmddhhmmss>_Log.htm
  
  for Standalone Meta-data Testing    C:\ADL\TestSuite1_2_7\TestSuite\metadata\tempdir\MDLogs\<yyyymmddhhmmss>_MD_Log.htm
  
  for Meta-data Testing in a Content Package    C:\ADL\TestSuite1_2_7\TestSuite\contentpackage\tempdir\Log_<yyyymmddhhmmss>\
  
  for Content Package Testing
  C:\ADL\TestSuite1_2_7\TestSuite\contentpackage\tempdir\Log_<yyyymmddhhmmss>\
  
  
• The SCO RTE test incorrectly passes a SCO that makes a call to the following API functions with no parameter:
  • LMSInitialize()
  • LMSFinish()
  • LMSCommit()
  • LMSGetDiagnostic()
  
  

Functionality

• The detailed logs can be searched to quickly find errors and warnings by using the browsers find function with the "ERROR" or "WARNING" keywords.
  
  
• The Content Package Test handles Package Level Meta-Data in two ways. Due to the nature of XML, if the meta-data is in-line well-formedness and schema validation testing is inherently performed with the imsmanifest test. If the meta-data is external to the manifest (uses the location element) the Content Package Test ignores the Meta-Data since there is no explicity Application Profile for Package Level Meta-Data.
  
  
• The table below describes a list of Browser and Sun Java Run-Time Environment (JRE) configuration compatibility with each conformance test. Please note that the browser versions stated in the table are based on Microsoft Internet Explorer (5.5x and 6.0x) and Netscape (6 and above). Also note that if a Java version does not appear in the table, it has not been tested.
  
  

JRE Version	LMS Test	Content Package Test	SCO Test	Meta-Data Test
1.4.2_04	No Support	No Support	Netscape	Internet Explorer
1.4.2_03	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.2_02	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.2_01	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.2	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.1_07	No Support	No Support	No Support	No Support
1.4.1_06	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.1_05	Internet Explorer	Internet Explorer	Internet Explorer	Internet Explorer
1.4.1_04	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.1_03	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.1_02	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.1_01	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer
1.4.1	Internet Explorer	Internet Explorer	Internet Explorer Netscape	Internet Explorer