Testing
13 packages, each available for 11 model families.
accessibility
Testing for accessibility — what automation catches, what it cannot, and the keyboard and screen-reader checks that find real barriers.
e2e
End-to-end tests that are worth their cost — user-visible selectors, deterministic waiting, and keeping the suite small enough to trust.
go-testing
Testing in Go with the standard toolchain — table-driven subtests, t.Helper, httptest and fstest, golden files, benchmarks, the race detector,…
integration
Testing across real boundaries — real databases in containers, isolation between tests, and faking third parties without faking their behaviour.
load
Load testing that predicts production behaviour — modelling real traffic, measuring percentiles not averages, and finding the knee before users do.
performance
Testing performance as a regression gate — budgets in CI, lab versus field data, and measuring the metrics users actually feel.
pytest
A pytest suite that stays fast and trustworthy — layout, fixtures with the right scope, parametrize instead of loops, markers that mean something,…
regression
Preventing bugs from returning — the failing test that must come first, choosing what to keep, and stopping a suite from becoming archaeology.
security
Testing for security defects — what SAST, DAST and dependency scanning each catch, and the abuse-case tests only a human writes.
stress
Pushing a system past its limit deliberately — finding the breaking point, verifying it degrades gracefully, and confirming it recovers.
test-strategy
Deciding what to test and at which level — the shape of a suite, what to do with legacy code, and the signals that a strategy is failing.
unit
Writing unit tests that catch regressions without cementing implementation — what to assert, what to fake, and why most flaky tests are design…
visual
Visual regression testing that is not permanently red — deterministic rendering, masking dynamic content, and reviewing diffs instead of regenerating…