Testing Cultures

What Testing Culture Covers

Testing culture includes more than a unit test library. It covers how tests are named, run, filtered, isolated, parallelized, documented, generated, mocked, fuzzed, benchmarked, and enforced in CI.

Some ecosystems ship strong standard testing tools. Go has the testing package and go test. Rust integrates tests into Cargo. Python ships unittest and has a large third-party testing culture. Java, .NET, JavaScript, and TypeScript depend heavily on external test frameworks and build integration. Groovy's JVM testing culture is especially visible through power assertions, JUnit integration, Spock specifications, and test DSLs around Java or Groovy code.

What To Compare

Look at how easy it is to write a small test, run one test, run the full suite, test async code, create fixtures, assert errors, fuzz inputs, collect coverage, run integration tests, and make tests deterministic in CI.

For libraries, examples and documentation tests can be part of the testing culture. For services, contract tests, migration tests, smoke tests, and deployment checks may matter more than unit tests alone.

Watch Points

A language can have excellent test tools and still have weak project discipline. Flaky tests, hidden network calls, global state, wall-clock assumptions, order dependence, and slow suites are design problems.

Make the default test command obvious and keep it fast enough that contributors actually run it.

Related Concepts

Testing connects Build Systems, Formatters And Linters, Documentation Cultures, and Structured Concurrency.