For Discussion: eLearning Pre-Launch Testing

Danger

I need your help. I’m trying to get an idea of what elearning professionals are doing with regard to prelaunch testing. More companies are adopting Bring Your Own Device (BYOD) environments and making their learning more accessible, some by using cloud LM

S products rather than hiding their learning behind firewalls and gateways that make learning painful. This should mean that learning is more vulnerable technically, since it’s harder to deliver the same experience across platforms and external servers can’t be as tightly controlled. But is it a problem? Are companies running into more technicals problems when launching to large audiences?

I’ve never seen a big interest in (or budget for) significant technical testing of learning products. Developers might click around from a few browsers, or recruit a handful of users to test, but it’s hardly realistic when it’s a small group of testers (and platforms) doing manual testing. Moreover, with the increase in HTML5 over Flash for rich elearning output, layout and rendering issues should be on the rise

because each browser handles things a bit differently.

Tell me about your experiences and expectations in the comments. Does elearning need more performance and compatibility testing? How are you working it into your workflow, and what tools are you using to give your stakeholders more reassurance?

Thanks for your feedback!

author avatar
Ryan Moore Director
Ryan Moore (MA, PMP, BCom) is the Cofounder and Director of Uncanny Owl, creators of Uncanny Automator and a suite of popular add-ons for LearnDash. Since 2013, Ryan has helped thousands of companies add elearning and automation capabilities to their WordPress websites.
0 replies

Comments/Questions

Please note that this is not a support forum. If you are experiencing issues on your site, please open a support ticket instead. Site-specific support questions submitted as comments will be unanswered.

Leave a Reply

Your email address will not be published. Required fields are marked *