Top 4 Tips for E-Learning QA Testing

Quality Assurance (QA) testing is a big part of e-learning course development. While I think it’s safe to say that this is not anyone’s favorite part of the process, that doesn’t make it any less important. Here are four tips for making sure your review process is fast, seamless, and effective.

1. Get Someone with a Fresh Set of Eyes to Review Your Course

When you’ve been working on a project for awhile, it’s often difficult to spot typos, spelling mistakes, and other small errors. Whenever possible, find someone who is not directly involved with the project to review your course—for example, a co-worker, a manager, a trusted friend, or even a parent. However, be careful not to share any confidential information with someone who has not signed a confidentiality waiver.

2. Include a Set Number of Review Cycles in Your Project Plan

Depending on the project and the number of stakeholders involved, you might have more or fewer review cycles. This is something you should determine at the beginning of the project, as more review cycles leads to more production time, which should be factored into your project plan. In addition to setting a fixed number of review cycles, set a timeline for each review cycle so you’re not sitting around waiting for feedback instead of moving the project forward.

3. Specify the Kind of Feedback You’re Looking For in Each Review Cycle

At each stage of the creation process, you’re focused on different aspects of your course. As the course designer, you know that, but your course reviewers might not. Make sure to give them guidelines about the type of feedback you’re looking for in each review cycle.

Say, for instance, your team is reviewing a storyboard. Feedback should be about content, not graphic design. And when they’re reviewing a prototype, their feedback should be about functionality and design.

If you don’t make it clear what type of feedback you’re looking for at each phase, the review process might end up being a real time-suck. For example, if your reviewers don’t understand they need to nail down the content in the first phase of development, they might keep giving you content-related feedback throughout the course creation process. If you have to keep going back and editing the content in the later stages of development, it could delay the course delivery date.

4. Use a Review App to Keep Track of Feedback

Keeping track of all the feedback received during review cycles used to be a huge challenge. I remember having to put together gigantic spreadsheets to try and keep tabs on it all. What a headache! Thankfully, now there’s Review 360.

Review 360 takes the pain out of the review process because it allows stakeholders to leave their comments in context: right next to the slide! Not to mention that the comments are preserved even when you upload a new version of the course, so you don’t have to worry about losing track of them. Just send them a link and they can add their feedback. Easy-peasy! Click here to learn more about why we love Review 360 (and why you will too).


Obviously, these suggestions are only the tip of the iceberg. Check out these resources for more great advice about the review process:

What about you? What does your QA testing process look like?

And if you found this article helpful, remember to subscribe to our newsletter to get the latest e-learning inspiration and insights directly in your inbox. You can also find us on LinkedIn and X (Formerly Twitter). And if you have questions, please share them in the comments.