A course about testing code whose author was not the person now responsible for it, in a codebase growing faster than the testing practice around it. It starts with why coverage is a weaker signal here: the number always measured execution and was a proxy for the belief behind the assertions, and that proxy weakens when tests are derived from the implementation rather than from a statement of intent. It works the tautological test in its four forms and how to detect each, a repeatable method for reading a test for what it would catch, the ways a test double quietly removes all value from a suite, and mutation testing as the mechanical version of the same question. It then builds the strongest available answers: property based testing, with a catalogue of property patterns for ordinary business code rather than for list reversal; fuzzing where input handling is involved; error and edge handling as the boundary where defects concentrate and arriving tests are thinnest; and regression tests built from real defects. It closes with a triage for a team that cannot retrofit everything, the work that stops new code arriving untested, and four measures that have to be taken inside your own organisation.
Nothing. Every course, exam, and certificate on the catalog is free — including retakes. All you need is a free Safeguard account.
None. The flagship course, Safeguard Certified Practitioner, is a beginner-level course — basic familiarity with how software is built helps, but every exam question is answerable from the lessons themselves.
You can retake it after a 24-hour cooldown, as many times as you need. Retakes are free, and each attempt draws a fresh random set of questions.
The Safeguard Certified Practitioner credential is valid for 24 months from issue. The expiry date is printed on the certificate and shown live on its public verification page. Renewing means passing the current exam again.
