For Discussion: eLearning Pre-Launch Testing

Email this to someoneTweet about this on TwitterShare on FacebookShare on Google+Pin on PinterestShare on LinkedIn

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!

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

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


6 + nine =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>