Skip to content
Documentation
Share via LTI
Test and troubleshoot
Test a course before you roll it out

Test a course before you roll it out

Test every course and every update on your own side and on the client’s side before learners get access. Linqur, Saltire, a sign-up URL and a test account in the client’s LMS each show you a different part of the chain.

A course in Linqur reaches a learner through a chain: the package, the course in Linqur, the way you share it (LTI tool, SCORM wrapper or sign-up URL) and the platform of your client. A problem in any link shows up at the learner, and by then it is costly to fix. Testing takes ten minutes per course and saves you that.

Test in Linqur first

Start with the package itself. After you add or update a SCORM package, Linqur shows the page of the package with an Enter button. Open it and click through the content: does it load, does every screen work, does the last screen send a completion? See add a SCORM package.

For a course that learners already use, don’t test on the live package. Duplicate the package in the course, update and test the copy, and only then update the package that learners use. The old file is gone once you save an update, so keep your own copy.

Do you want to test the connection rather than the content? Use one of the sample SCORM packages. They send a status or a grade when you click a button, so you see within a minute whether the result arrives.

Test the LTI connection with Saltire

Saltire is a free test platform that acts as an LMS. You add the launch details of a Legacy LTI (1.1) tool, launch it and see what Linqur sends back. That tells you whether the tool launches and whether the grade comes through, before your client sets anything up. Steps: test a Legacy LTI connection with Saltire and, for a full walk-through including grade synchronisation, set up and test an LTI connection with Saltire.

In Linqur, the test launch shows up on the details page of the tool under Registered users and SCORM results, see share the launch details of an LTI tool. The grade is in the Gradebook of the course: view grades in the Gradebook.

See the course as a learner with a sign-up URL

A sign-up URL lets you go through the course exactly as a learner does: sign up, receive the login link, open the course, finish it. Use it for your own courses and for anything you share with a sign-up URL. Create the URL on the test course (create a sign-up URL), sign up with your own address or a test address, and check afterwards in Sign-up URL Analytics that the registration and the result are there. Archive or delete the URL when you are done: manage sign-up URLs.

Test at the client’s side before you roll out

A launch that works in Saltire can still fail in your client’s LMS: a different LTI version, a wrong custom parameter, a privacy setting that withholds the user’s name, a browser that blocks the launch. So test the real thing before the client announces the course to learners.

Two ways to do that:

  • A test account in the client’s LMS. Ask the client for a learner account on their LMS, or for a test course with the tool in it. Launch the course yourself, finish it and check both sides: the result in Linqur and the result in the LMS of the client.
  • The client tests and confirms. Ask the client to launch the course with a test learner, finish it and report back. Ask specifically whether the course opened, whether the content showed correctly on the devices their learners use, and whether the completion and the grade appeared in their LMS. Get a written confirmation before the rollout, so both of you know the connection worked at that moment.

For a SCORM wrapper, the test is the same: the client uploads the wrapper to their LMS and launches it. The results are in SCORM Analytics.

Repeat this after every update that changes the content or the settings of the tool, not only at the first rollout.

When something fails

Last updated on
Look up LTI errors with the Debug assistant