Subscribe to Our Newsletter
Get the latest updates delivered straight to your inbox.
Testing Course Resume and Results in a Saudi LMS
A new mandatory course arrives from an external agency. The learning team reviews it in the authoring tool’s preview, approves it, and publishes it in the LMS software to every employee on Sunday. By Tuesday, the messages start. Staff who took a phone call halfway through return to the first screen. A branch manager reports that her team passed the final quiz, but the LMS software still shows them as incomplete. And on the older tablets in two stores, the last interaction is cut off at the right-hand edge.
None of this was visible in the preview, because the preview was not the place where the course would actually run. A course package works for employees only when it works inside your LMS software, with your settings, on the devices your people really use.
This article sets out a pre-publishing test routine for Saudi HR, IT and procurement teams: a staging course in the real LMS software, a device matrix drawn from your workforce, resume scenarios and result checks, finished with a short sign-off. It is about each new package before publishing; moving an existing library is a separate project, covered in our guide to migrating a course library to a new LMS.
Why the Preview Is Not the TestAn authoring tool’s preview or a vendor’s review link runs the course in its own environment, not in your LMS software. Once published, the package has to communicate with your LMS software: it reports progress, saves where the learner stopped, and sends a result.
Packages commonly follow a standard for this conversation, such as SCORM, xAPI, or cmi5, but a package and a piece of LMS software that both ‘support’ a standard can still behave differently together. Compatibility is something to verify, not assume.
Resume shows why. The xAPI specification published by ADL describes a State Resource that is generally a scratch area for learning activities that need to persist state across devices. Whatever standard a package uses, resuming depends on two things working together: the course must save its place, and the learning management system must store it and hand it back. Neither half can be tested in a preview.
Set Up a Staging Course in the Real LMS SoftwareUpload the package to the LMS software you will actually use, either in a hidden test category of the live platform or in a test environment whose version and settings match it. Configure the staging course exactly as the live course will be: the same completion rule, pass mark, attempt limit, due date, and certificate. A test with different settings proves very little.
If you test in a separate environment, ask IT or the provider to confirm that it runs the same version of the LMS software and the same course settings as the live platform. A package that passes in an older test copy can still fail on the day it is published.
Create three or four test accounts in the LMS software: one with the interface in Arabic, one in English, one assigned through a manager, and one that will be used on several devices. Keep the staging course invisible to real employees, and do not mark the package as approved until every test below has passed.
Build a Device Matrix from Your Real WorkforceSaudi Arabia’s National eLearning Center standards include a requirement to ensure interoperability across common devices and operating systems, including computers, tablets, and smartphones, so that users can access learning without technical limitations. Whether or not your organization is within the standards’ scope, the practical question is which devices your employees actually use to open the LMS software.
Ask IT for the managed device list and ask two or three branches or sites what staff really use, then build a short matrix:
Check layout on the smallest phone first. W3C’s WCAG 2.2 criterion on reflow, a Level AA requirement, asks that content can be presented without loss of information or functionality, and without scrolling in two directions, at a width equivalent to 320 CSS pixels. Drag-and-drop exercises, wide tables and fixed-size slides are where course packages most often break this, in either language.
Resume Scenarios to Run in Your LMS SoftwareRun each scenario on at least one computer and one phone from the matrix, and write the expected result first:
Expect the learner to land where they stopped, with completed sections still marked and no duplicate attempt. If the LMS software or the course asks whether to resume or start again, check that the prompt is clear in Arabic and in English. A course that only saves at the end of each chapter may be acceptable for short chapters and frustrating for long ones; that is a design decision to make before publishing, not after complaints.
Check the Result the LMS Software Records, Not the ScreenThe score on the course’s final screen is what the package thinks. What counts is what the LMS software records. With the test accounts, run three paths: pass on the first attempt, fail and then pass, and view all content without passing. For each, open the learner’s record in the LMS software and the manager’s view, and check the status, the score, pass or fail, the completion date, the attempt count, and the certificate, including the learner’s name in Arabic.
Repeat at least one path on a phone. A result achieved on a phone should be recorded in the LMS software exactly as one achieved on a laptop. If the recorded status surprises you, check how your platform defines each status before changing the package; our guide to testing LMS completion reports lists the definitions to confirm.
Note how long the LMS software takes to show each result as well. Some records update immediately, others only after the session closes or a synchronization runs. Agree how long testers wait before logging a defect, so that a short delay is not reported as a failure, and a result that never arrives is not dismissed as a delay.
Sign-Off Before PublishingClose the routine with a one-page QA record for each package: its version, the staging settings, the devices tested, the resume scenarios, the result paths, and any defects with their owner. The content owner and the learning team sign it before the course goes live in the LMS software. Repeat the routine when the package is updated or the LMS software receives a major upgrade, because either side of the conversation may change. If you are still choosing a platform, add one resume scenario and one result path to the practical demo test for choosing an Arabic LMS in Saudi Arabia.
A Hypothetical Example: A Product Course for Telecom StoresThe following example is hypothetical and is included only to illustrate the method.
A telecom operator’s retail division in Saudi Arabia commissions a twenty-minute course on a new family plan, with short videos, a drag-and-drop matching task, and a final quiz. Before publishing, the learning team sets up a staging course in its LMS software with the live settings: pass mark 80%, three attempts, a certificate. It tests on a store tablet, two staff phones, and a laptop.
Four problems appear. On phones, switching to another app restarts the current video section because the package saves progress only at the end of each section. The LMS software marks the course complete when the last screen is viewed, even after a failed quiz, because the package’s completion setting conflicts with the course rule. The drag-and-drop task needs sideways scrolling on the smaller phone. And the Arabic certificate splits a four-part name across two lines in the wrong order.
The agency republishes the package with more frequent saving and a completion setting aligned with the pass mark, and replaces drag-and-drop with tap-to-select on small screens. The learning team corrects the certificate template. A second round on the same devices passes, and the course is published to all stores with a signed QA record.
SummaryA preview proves that a course plays; it does not prove that it resumes or records results inside your LMS software. Test each new package on a staging course with the live settings, on devices taken from your real workforce, including the smallest phone.
Run the resume scenarios, compare the recorded result with what the learner actually did, and sign a short QA record before publishing in the LMS software. That turns ‘it should be compatible’ into evidence, and spares Saudi employees and managers from discovering the gaps for you.
Click here if you want Skillup MENA to help you.




