Testing in the Sandbox
Every tool has a Sandbox: a private course that only you can see, with your tool already in it. Launches there are the genuine article — Voshi plays the part of the LMS, and everything downstream is real: the picker, provisioning, storage, roles, and a gradebook that takes your scores. If your tool works here, it works in a school's LMS.
The Sandbox always runs your draft, the code you last built or uploaded. See Versions.
Two ways in
- The Running Tool panel on the AI Builder page is a Sandbox launch of one location, as one role, with a Refresh button. It is the fast loop: build, look, change, build.
- The Sandbox tab is the whole course: its links, its launches, its gradebook. It is where you test the way an instructor and a student will actually use the tool.
Links
A link is a placement of your tool in the Sandbox course, like a placement in a real course.
New Link opens your tool's content picker — the same one an instructor sees, listing your offered locations. Pick one and confirm. For an assessment, this is also where the gradebook column is created, worth the location's points.
Launch a link as a student or as an instructor. Each role is a separate person in the course with its own saved work, and they share the course, so an instructor launch sees what the student launch saved — the right way to test an instructor setup screen or a review view.
Reset throws away everything stored at that link — the location's data, every persona's work, and their grades — so the next launch is a first launch again. This is the only place in Voshi where saved data is deliberately discarded. Remove deletes the link; the location itself is kept and can be placed again.
The Provisioned column shows whether the link's course setup has run. A hosted tool's provisioning is automatic, so it reads Yes as soon as the link is placed or first launched.
Launches and Grades
The Sandbox's Launches tab lists each launch in the course. Its Grades tab is the course gradebook: every score your tool reported, by link and by persona, with the result. A score refused by the gradebook shows the reason, so a wrong maxScore or a call made when canSubmitGrade was false is visible here, not just in the browser console.
What to check before publishing
- Every location launches and shows the right activity for its
extid. - A student can save and come back. Launch as a student, do some work, launch again: it should still be there.
- Roles are respected. An instructor sees the setup or review features; a student does not. A student launch never calls
submitGradefor an instructor, and an instructor previewing the activity does not score themself. - Grades land. Finish the activity as a student and find the score in the Grades tab.
- The frame fits. The tool should not scroll inside itself unless you mean it to; give the element
:host { display: block }and Voshi sizes the frame.
A Sandbox launch signs your browser in as the test student or instructor, not as yourself. Expect to sign back into the dashboard afterwards if you opened a launch in its own window.