Developers
Reliability Notes
What is backed by automated tests today, and what should still be validated in your own project.
Automated coverage today
- Learner access, identity matching, enrollment idempotency, LMS-domain URL handling, progress services, certificate issuance, certificate PDFs, verification payloads, selected REST/controller paths, and license-server behavior.
- Selected Playwright journeys cover learner access, learning loops, certificate completion, course-builder concepts, full learner journeys, and license purchase activation when the matching local stack is configured.
Validate per project
- The foundation-redesign theme, foundation-demo-core setup plugin, checkout flow, docs UI, and cross-version WooCommerce compatibility should be treated as project-specific validation surfaces until dedicated tests are added.
- Payment gateway refund/cancellation behavior should be tested with the gateway and order statuses used in production.