User Acceptance Testing (UAT)

Contents

User Acceptance Testing (UAT) should occur throughout the development of learning experiences, with final UAT serving as the last validation step before broad release. It involves representative learners and relevant business stakeholders testing the solution against agreed acceptance criteria to confirm that usability, navigation, accessibility, content clarity, assessment rules, completion recording, and learner pathways function as intended.

In practice, "UAT complete" means testing has been finalised, issues have been identified, logged, triaged and resolved (or formally accepted with an agreed workaround), and a clear go/no-go decision has been made confirming the solution is fit for release.

To be effective, UAT should be planned at the beginning of the project and incorporated into the course development timeline, rather than being treated as an activity conducted only at the end of the build. Early planning ensures that testing requirements, test scenarios, acceptance criteria, LMS configurations, reporting requirements, accessibility obligations, adaptive learning pathways, and assessment rules are considered during the design phase. This influences how the solution is developed, reduces the risk of costly rework, and ensures sufficient time is allocated for testing, defect remediation, retesting, and stakeholder sign-off prior to release.

Why is it important?

UAT protects the credibility of APS learning by confirming learners can successfully complete the experience and that it meets business needs. Real users commonly identify issues designers and developers don’t anticipate especially around navigation, clarity, and system behaviour (including how completion is recorded).

UAT also supports whole of government expectations for user centred, inclusive and measurable staff facing experiences. Completing UAT reduces risk and ensures the learning is ready for broad release, rather than relying on rework once problems are visible at scale. 

What are the benefits?

  • Undertaking UAT throughout the project can help identify unexpected challenges early in the process. 
  • Completing final user acceptance testing confirms the solution meets business requirements and works as intended, reducing the risk of defects or issues after release. 
  • User sign off provides confidence that the product is fit for purpose, supporting a smoother go live and reducing the need for rework or urgent fixes post implementation. 
  • Learning works as intended in real conditions (devices, browsers, accessibility needs).
  • Issues are found early, reducing frustration and support calls after launch.
  • Learners have more trust in the learning product, improving uptake and completion.
  • Better value for money by reducing avoidable rework after launch. 

Suitable for

  • L&D teams launching or updating learning solutions (eLearning, blended, workshops with digital components).
  • Pilot participants / representative learners and supervisors.
  • Business sponsors / product owners for the learning solution.

SCORM (eLearn) UAT checklist example 

This User Acceptance Testing (UAT) Checklist has been developed to validate that the WHS SCORM package functions as intended within the Learning Management System (LMS), meets business and technical requirements, accurately tracks learner activity and completion, and provides an accessible and effective learning experience before release to learners.

The checklist supports testing of:

☐ Course launches successfully.

☐ SCORM package uploads successfully.

☐ LMS tracking is accurate.

☐ Adaptive learning pathways function correctly.

☐ Branching pathways function correctly.

☐ Assessments behave as designed.

☐ Bookmarking and resume functionality operate correctly.

☐ Three-attempt restriction works correctly.

☐ Dynamic learner messaging operates correctly.

☐ Accessibility requirements have been met.

☐ All critical defects have been resolved.

☐ Course approved for production release.

 

Overview

Thank you for participating in the [Phase - Alpha/Beta/Production] testing for ‘Name of L&D Solution’ on [where they will be going]. 

Provide an explanation of the learning experience to provide context to the tester.

Phase testing 

The purpose of this testing is to test:

  • Bullet point what they are testing.

Your role 

As a tester, you are required to: 

  • Bullet point what they are to be doing.

Testing period 

The testing period is open from Date until Date.

Please ensure you complete your review within this time period as no extensions can be given due to [xxx] timelines.

The testing will take approximately XXXX to complete inclusive of XXXX.

The learning experience is [mode of delivery] and can be completed any time within the testing period. You can choose to complete it in one session or complete it over multiple sessions.

Testing instructions

Testing instructions start on page X of this document. Please read through all the instructions prior to commencing as it contains important information on what you are being asked to review and how to report any errors/issues (where applicable).

Overview steps

  • System: Clear cache in Google, Edge (go to settings and type cache). 
  • Does testing require being in incognito (or private) browser at the same time to test scenarios? 
  • Document your steps and what you see each step throughout the process. 
  • Run through the different scenarios in each browser. If you encounter an error, insert a screen shot or video recording.
  • If fail, add notes into the Error/Bug register.
  • Retest any fixes after deployment.
  • Have a document that outline how the SCORM behaves and what the answers are. If people don’t know how it is to perform, how will they know the results are right or wrong. 

Contact 

For feedback or questions, please contact [X].

Item Details

Course Name

  

Version

  

Vendor

  

Authoring Tool

  

SCORM Version

  

URL

Username:

Password:

Open / cohort locked:

LMS Environment

Username:

Password:

Open / cohort locked:

Test Date

  

Tester

 Provide tools and resources to help users to learn from each other.

1. Package Validation

Test Item Pass / Fail Comments

SCORM package publishes successfully from authoring tool

    

Package uploads into LMS without errors

    

Package launches correctly from LMS

    

Course title displays correctly

    

Clear instructions on what the learner needs to do before they start: 

-    Assessments

-    Pass/ fail 

-    Forced pathways or dynamic

-    Locked / Review mode / Attempts

-    Accessibility options 

-    What to do when exiting

    

All assets load correctly (images, videos, audio)

    

Speed between sections is [X]. Learner is forced to wait before the information has loaded and can move to the next section

    

Navigation functions correctly

    

No broken links or missing content

    

Package matches approved storyboard

    

☐ SCORM was built correctly in the authoring platform.

☐ Package matches approved storyboard and design.

☐ Package follows intended learner journey.

2. LMS Tracking & Reporting

Test Item Pass / Fail Comments

LMS records course launch

    

LMS records learner progress

    

LMS records completion correctly

    

LMS records quiz score correctly

    
LMS records pass status correctly    

LMS records fail status correctly

    

LMS records lesson status correctly

    

LMS bookmarking functions correctly

    

☐ LMS tracks and records SCORM data exactly as configured.

☐ LMS receives completion status correctly.

☐ LMS receives score correctly.

☐ LMS receives pass/fail status correctly.

☐ Reporting data appears correctly in LMS reporting.

3. Accessibility (WCAG)

Test Item Pass / Fail Comments

WCAG compliant checklist has been completed

    

4. Adaptive Learning Path Testing

Expected Result

User completes introduction and assessment.
User achieves 100%.
User immediately passes and receives completion.

Test

 

Test Item Pass / Fail Comments

Introduction displays correctly

    

Assessment functions correctly

    

User achieves 100%

    

Course automatically marks complete

    
LMS receives completion status    

LMS receives passing score

    

User is not shown learning modules unnecessarily

    

Pending on design: Incorrect answer feedback does not reveal correct answer

    

Expected Result

User fails initial assessment.
User is presented with required modules only.
Completed knowledge areas are ticked.
Failed knowledge areas remain incomplete.

Test

 

Test Item Pass / Fail Comments

User fails when score is below 100%

    

Correct modules are marked complete

    

Failed modules remain incomplete

    

User can access required modules

    
User must review content before reassessment    

Module knowledge checks display correctly

    

Module becomes complete after successful completion

    

User reaches 100% overall completion

    

LMS receives completion status

    

Pending on design: Correct answers are NOT displayed after incorrect responses

    

Expected Result

User can/can't skips or does/does not complete self-assessment and progresses through modules sequentially.

Test

 

Test Item Pass / Fail Comments

User can complete modules sequentially

    

Modules unlock/display correctly

    

Knowledge checks function correctly

    

Completion awarded after all requirements met

    
LMS records progress    

Feedback behaviour matches approved design

    

☐ Confirm whether users receive the correct answer after an incorrect response.

☐ Confirm behaviour aligns with requirements.

5. Branching Logic Testing

Test Item Pass / Fail Comments

Learner follows correct branch pathway

    

Branching decisions are accurate

    

Content displayed matches learner responses

    

Learner does not receive unnecessary content

    
Completion logic remains accurate    

Reporting remains accurate regardless of pathway

    

6. Quiz and Question Behaviour

Test Item Pass / Fail Comments

All questions display correctly

    

Correct answers are scored correctly

    

Incorrect answers are scored correctly

    

Questions align with storyboard

    
Branching logic functions correctly    

No answer data corruption occurs

    

Results calculations are accurate

    

Question feedback behaves as intended

    

☐ SCORM behaves exactly as designed.

☐ All learner responses are recorded correctly.

7. Failed Attempt Management

Requirement

After three failed attempts:

  • User cannot reattempt.
  • SCORM enters review mode or is greyed out.
  • SCORM does not send completion.
  • SCORM remains incomplete in LMS.
  • User must seek manager approval.
  • LMS Administrator must unlock access.

Test

 

Test Item Pass / Fail Comments

Maximum attempts set to three

    

Attempt counter functions correctly

    

User locked after third fail

    

SCORM enters review mode OR becomes greyed out

    
User cannot launch another attempt    

SCORM does not send completion to LMS

    

LMS status remains incomplete

    

LMS reporting reflects failed status

    

Lock persists after logout/login

    

8. Progress Tracking & Bookmarking

Steps

  1. Launch course.
  2. Complete part of content.
  3. Exit course.
  4. Relaunch course.

Test

 

Test Item Pass / Fail Comments

User progress saved correctly

    

Course remembers learner location

    

Learner prompted to resume or restart

    

Resume launches at correct location

    
Restart functions correctly    

Progress remains accurate after multiple launches

    

9. eLearning Functional Testing

Test Item Pass / Fail Comments

Sections and headings align correctly

    

Content meets course specifications

    

All links function correctly

    

Pop-ups appear correctly

    
Show/hide interactions work    

User can skip modules where permitted

    

Completion status updates correctly

    

User understands how to exit course

    
Test Item Pass / Fail Comments

Audio prompt visible

    

Audio plays correctly

    

Audio controls work correctly

    

Audio is clear and audible

    
Test Item Pass / Fail Comments

Video prompt visible

    

Video plays correctly

    

Video controls work correctly

    

Transcript available

    
Transcript formatted correctly    

Auto-play behaviour functions as designed

    
Test Item Pass / Fail Comments

Hover states visible

    

Buttons clickable

    

Links clickable

    

Correct destination opens

    
User understands destination before clicking    

Pages open correctly

    
Test Item Pass / Fail Comments

Hover state visible

    

Accordion opens

    

Accordion closes

    

Multiple accordions open simultaneously

    
Test Item Pass / Fail Comments

Hover state visible

    

User navigates to correct section

    

Page scrolls correctly

    

Return-to-top anchor functions correctly

    
Test Item Pass / Fail Comments

File link visible

    

Hover state visible

    

File opens/downloads correctly

    

Correct file opens

    
File type displayed    

File size displayed

    

File is accessible

    

File editing permissions correct

    

Download speed acceptable

    
Test Item Pass / Fail Comments

Valid form submits successfully

    

User receives confirmation message

    

Invalid form displays error

    

Blank required fields display error

    
Invalid email format rejected    

Error location clearly identified

    
Test Item Pass / Fail Comments

Yes/No response works

    

Free text accepted

    

Form submits successfully

    

Confirmation displayed

    
Validation errors displayed correctly    

Share

 

Test Item Pass / Fail Comments

Share icon visible

    

Share options display correctly

    

Share via email works

    

Share via link works

    

Print

 

Test Item Pass / Fail Comments

Print icon visible

    

Print function launches

    

PDF generated successfully

    

Printable content displayed correctly

    
Test Item Pass / Fail Comments

Search bar available

    

Search returns expected results

    

Keyword tested documented

    

Screenshot captured

    

Keyword Tested: ___________________________________

Test Item Pass / Fail Comments

Partner icons display correctly

    

Partner links open correctly

    

Social media icons display correctly

    

Social media links open correctly

    
Test Item Pass / Fail Comments

Phone link works

    

Email link opens mail client

    

Contact details accurate

    
Test Item Pass / Fail Comments

Most important information appears first

    

Headings used effectively

    

Content makes sense

    

Plain English used

    
Content concise and readable    

No grammar or spelling issues

    

Calls-to-action are clear

    

Failure Message

☐ Message displays after lockout.

Example:

You have reached the maximum number of attempts for this course. Please discuss your training requirements with your manager. Following manager approval, contact your LMS Administrator to request access to be reinstated.

Completion Message

☐ Successful completion message displays correctly.

10. Cross-System Compatibility

Test Item Pass / Fail Comments

SCORM 1.2 uploads successfully

    

SCORM 1.2 reporting functions correctly

    

SCORM 2004 uploads successfully

    

SCORM 2004 completion tracking functions correctly

    
SCORM 2004 score tracking functions correctly    

Any unavailable reporting elements documented

    

Note: Validate all reporting and tracking outcomes individually.

11. User Feedback Collection

Test Item Pass / Fail Comments

Test users provided feedback

    

Feedback document completed

    

Learning experience validated

    

Navigation validated

    
Content accuracy validated    

Accessibility feedback gathered

    

Defects logged

    

Defects resolved and retested

    

12. UAT Sign-Off

Role Name Signature Date

Business Owner

      

Learning Team

      

LMS Administrator

      

Vendor

      
Final Approval      

Final Acceptance Criteria 

☐ Course launches successfully. 

☐ All adaptive and branching pathways function as designed. 

☐ LMS tracking is accurate. 

☐ Accessibility requirements are met.

☐ Completion and failure statuses are recorded correctly. 

☐ Attempt restrictions work correctly. 

☐ Dynamic learner messaging functions correctly. 

☐ No critical defects remain open. 

☐ Course approved for publication.

General Practices

 

Good Practice
  • Use a documented plan that sets out who, when and how testing will occur.
  • Provide clear instructions what needs to be tested.
  • Ensure there are no functionality problems.
  • Ensure there is design consistency and no design deficiencies. 
  • Every link and interaction has been checked. 
  • Include representative users (not only L&D staff). 
  • Record, triage and resolve issues; document any accepted residual risks.
  • Capture a clear go/no go sign off before launch. 
  • WCAG completed.

 

Practices to avoid
  • ONLY the technical and SME should complete final checks. The technical team will check for functionality, and the SME will ensure the L&D solution is performing as designed and there are no content mistakes. The SME may be the person who created the content and design the learning experience.
  • Skipping UAT due to deadlines and launching untested.
  • Using only L&D staff as testers (missing real user needs).
  • Vague acceptance criteria and unclear instructions.
  • No one knows what they are testing against and what the results and expected behaviour should be. 
  • Ignoring or losing feedback because it isn’t logged and managed. 

Hypothetical examples

 

Example - Assessment Completion Not Reporting Correctly to the LMS

The WHS SCORM package was uploaded to the LMS and completed by several pilot users. Due to project time pressures, the course was released without comprehensive User Acceptance Testing (UAT).

After launch, users successfully completed the final assessment and received a "Course Completed" message within the SCORM. However, the LMS continued to display their status as Incomplete, preventing training records from being updated and causing confusion for managers and reporting teams.

Potential Issue

Not completing final user acceptance testing can lead to undetected issues and reduced confidence at release. In this scenario, the SCORM completion status was not communicating correctly with the LMS. As a result:

  • Learners believed they had completed mandatory training when the LMS showed otherwise.
  • Managers could not verify completion through LMS reports.
  • The LMS team received a high volume of support requests.
  • Significant effort was required to investigate, remediate and retest the SCORM package.
  • Stakeholder confidence in the quality and reliability of the learning solution was reduced.

Better Approach

By thoroughly conducting end-to-end UAT, including SCORM tracking and LMS reporting validation, the issue would have been identified before release.

Testing would have confirmed that:

  • Completion status was being sent correctly from the SCORM package.
  • LMS reports reflected learner activity accurately.
  • Pass/fail and completion criteria functioned as designed.
  • Any configuration issues were resolved before learners accessed the course.

This would have resulted in a smoother implementation, fewer post-release defects, accurate reporting, and greater confidence that the learning solution was fit for purpose.

 

Example - Adaptive Learning Pathway and Attempt Restrictions Not Functioning as Designed

A WHS adaptive learning course was designed to allow learners who scored 100% on the pre-assessment to immediately achieve completion. Learners scoring below 100% were required to complete only the modules relevant to their knowledge gaps. The course also contained a business rule requiring users to be locked after three failed assessment attempts and directed to contact their manager before reattempting.

The solution was released before all adaptive learning and attempt-management scenarios were tested.

Potential Issue

Without comprehensive testing of all learning pathways, critical business and compliance requirements may not function correctly.

Following release:

  • Learners who scored 100% were incorrectly directed to complete all modules.
  • Some learners who failed multiple times were able to continue attempting assessments indefinitely.
  • Other users were locked out after a single failed attempt.
  • Dynamic messaging advising learners to contact their manager did not appear.
  • LMS reporting showed inconsistent completion and assessment outcomes.

These issues created an inconsistent learning experience, increased support requests, and introduced compliance risks because assessment and completion rules were not being applied as intended.

Better Approach

By executing all UAT scenarios, including adaptive learning pathways, branching logic, bookmarking, completion rules, and failed-attempt management, defects could have been identified and remedied before release.

Testing would have confirmed that:

  • Learners scoring 100% received immediate completion.
  • Learners scoring below 100% followed the correct learning pathway.
  • Module completion indicators behaved correctly.
  • Three-attempt restrictions functioned consistently.
  • Completion and failure messages displayed appropriately.
  • LMS reporting accurately reflected learner outcomes.

This proactive approach would have reduced operational risk, improved the learner experience, ensured compliance requirements were met, and provided stakeholders with confidence that the solution was fully tested and ready for production deployment.
Topics
Communication
Project management
Risk management
Service design
L&D Section
Learning solutions and experiences
L&D Groups
Discovery and planning
L&D Categories
Learning Design and Administration
Was this page helpful?
Last updated