Import and validate a QTI 3.0 assessment package into a QTI-conformant delivery platform
domain: imsglobal.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Validate the ZIP package structure: the root must contain imsmanifest.xml (or a QTI 3 package manifest) referencing all item and test XML files with correct relative paths.
Run the package through the 1EdTech QTI 3 online validation tool (available to 1EdTech members) to check schema conformance before uploading; review any reported errors by element and line number.
Upload the package to the delivery platform via its import API or admin UI; note the returned packageId or assessmentId for subsequent delivery configuration.
Trigger a delivery session by associating the assessmentId with a course context (e.g., via LTI Deep Linking or the platform's assignment API), and configure time limits and shuffle settings at the test level.
After a learner session, retrieve QTI Results Reporting XML (QTI-RR) from the platform's results endpoint; parse assessmentResult / itemResult / outcomeVariable elements to extract SCORE and RESPONSE values.
Map the SCORE outcome against your grade book line item using LTI Advantage AGS if the delivery was launched via LTI.
Known gotchas
Many platforms perform partial QTI 3.0 support — they may import single items but not the full assessmentTest element; test a minimal package first to identify gaps.
Custom interaction types (Portable Custom Interactions) require the delivery engine to have the corresponding JavaScript module registered; generic platforms will render them as empty.
QTI Results Reporting is a separate schema from the item/test schema; parsers written for QTI 2.x assessment results are not directly compatible with QTI 3.0 result documents.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?