Contains subcommands for handling specific test release instances. For more information about the testing model, please see /test.
The following subcommands are available for this route:
|Returns an array of test session records that belong to a release instance.|
|/finalize||Finalize a release instance.|
|/unfinalize||Unfinalize a release instance.|
Returns an array of session records belonging to a release instance.
|GET /release/sessions/<release_id> HTTP/1.1|
Finalizes a release instance. This has the effect of:
- Submitting all un-submitted test session records where record has a status of PROG ("In Progress"). Sessions that have not been started by a student will be left alone, but will not be available for use any longer.
- Scoring any un-scored responses from sessions that have been submitted as part of the previous step.
- Locking the release to prevent any further testing to be conducted in the release.
- Generating relevant performance statistics for the release as a whole.
Important: This command should not be issued until ALL testing has been completed in a release, and all scores have been input for each response, including instances where human-scored responses are required. Any requests to manipulate session records belonging to this release will first require the release to be un-finalized.
|POST /release/finalize/<release_id> HTTP/1.1|
Un-finalizes a release instance. This method should be used whenever alterations need to be made to individual session records (such as retroactively changing response scores) or if you require more students to be assessed in the release after it has already been finalized.
Important: Remember to re-finalize the release once all desired activity is complete. Statistics from un-finalized releases are not included in student or item performance reports, and are only re-generated on /release/finalize.
|POST /release/unfinalize/<release_id> HTTP/1.1|