Testing

Write good software tests after proving every rule that can be proved. Use when you design, change, fix, review, or release software; choose test cases, boundaries, levels, doubles, fixtures, assertions, or checks; decide which tests to run; or fix a test suite that is weak, flaky, slow, hard to change, or gives a false picture. Put rules first in the design, types, exhaustive checks, schemas, constraints, static analysis, or direct proof. Then test the important risk left where proof ends.

nmnmcc Updated 3 repo stars

File contents

nmnmcc/preview commit 99f269f082

Frequently asked questions

npx get-skill add nmnmcc/testing-2