Skip to content

Testing Guide — V2 Course Area

What to test, in which order, and what to do when it breaks.

Start here

The scope tells you what is in and what is out. Skip it and you will file bugs against a different product.

Six flows

The test is a single line, end to end: create → build → publish → enroll → take → complete. Each step depends on the one before it.

Report like this

A finding without reproduction steps becomes a queue item, not a fix. The format is short on purpose.

Already known

Known limitations lists what is already mapped. Check it before filing — it saves your time and ours.