We have so much experience authoring content in various systems that our clients often ask us the best way to test their platforms. This is an example of a test protocol we developed for a client based on our knowledge of their system, the content, and the use cases.

After we authored and tagged thousands of assessment items in Excel, our client asked us to QA them in the digital platform to ensure that all content ingested correctly. We used this spreadsheet to log, triage, and correct defects and to track until approval.

This client had a copy-and-paste ingestion process for rendering PDF source content in their proprietary ebook platform. We performed a character-by-character proofread of source content against ingested content, which surfaced missing characters, dropped formatting, and broken links.

Our clients value our ability to craft a clear, concise defect description that pinpoints the defect and directly recommends a fix. The ePP team generated this bug report for one of the OER titles for which we performed a functionality review. 

Our team has listened to thousands of hours of audio generated by human talent and text-to-speech engines, including AWS, and our ears are uniquely attuned to identifying defects that may inhibit learning. This report resulted from ensuring that the voiceover is understandable, matches the onscreen text, uses correct pronunciation, and includes appropriate pauses and emphasis.

We often review all audio, images, interactivities, and media to confirm that they are to spec and meet quality criteria before build. We may then QA the entire build to ensure accurate deployment from the student and/or teacher perspective. Typically, we log bugs in a spreadsheet, digital bugbase, or comparable, and we regress until approved.