ava-tests

Overview

Per github.com/avajs/ava:

AVA's distinguishing properties:

• Concurrent by default: each test file runs in a separate Node process; tests within a file run concurrently unless serial.
• No globals: import test from 'ava' - explicit, easier to type, no dependency-injection hacks.
• Async-first: native promise/async-await support; no done callback dance.
• Powerful assertion failures: t.is/t.deepEqual etc. produce diff-rich failure output.
• Snapshot support: t.snapshot() built-in.

The per-file process isolation eliminates entire test-interference classes that Jest/Mocha allow.

When to use

• Library / utility / SDK projects (file-level isolation is high-value).
• Async-heavy code (concurrent test execution shines).
• Team prefers explicit imports over global injection.
• Migration from Mocha where parallelism matters.

For React component testing, prefer vitest-tests or jest-tests (ecosystem density).

Step 1 - Install

Per ava-gh:

npm init ava
# or manually:
npm install --save-dev ava

Step 2 - First test

// test/sum.test.js
import test from 'ava';
import { sum } from '../src/sum.js';

test('adds 1 + 2 to equal 3', t => {
  t.is(sum(1, 2), 3);
});

test('async addition', async t => {
  const result = await Promise.resolve(sum(2, 3));
  t.is(result, 5);
});

t is the AVA-injected test context; assertion methods live on it (t.is, t.deepEqual, t.truthy, t.snapshot, t.throws, etc.). No global expect / assert - explicit per test.

Step 3 - Configuration

Config lives in package.json ava key OR ava.config.js:

// package.json
{
  "ava": {
    "files": ["test/**/*.test.js"],
    "extensions": ["js", "ts"],
    "require": ["ts-node/register"],
    "timeout": "30s",
    "concurrency": 4,
    "failFast": false,
    "verbose": true,
    "snapshotDir": "test/snapshots"
  }
}

For TypeScript with the @ava/typescript adapter:

npm install --save-dev @ava/typescript typescript

{
  "ava": {
    "typescript": {
      "rewritePaths": { "src/": "build/" },
      "compile": "tsc"
    }
  }
}

Step 4 - Concurrency model

• Each test file runs in its own Node worker process.
• Tests within a file run concurrently by default.
• Use test.serial(...) to force serial execution within a file:

test.serial('this runs first', t => { /* ... */ });
test.serial('this runs second', t => { /* ... */ });
test('this runs concurrently with the next', t => { /* ... */ });
test('this runs concurrently with the previous', t => { /* ... */ });

For tests that share file-level state (rare, often a smell), serial is necessary.

Step 5 - Hooks

test.before(async t => {
  // runs once before all tests in file
});
test.after(async t => {
  // runs once after all tests
});
test.beforeEach(async t => {
  // runs before each test
});
test.afterEach(async t => {
  // runs after each test
});

// Hooks can pass context to tests via t.context:
test.beforeEach(t => {
  t.context.user = createUser();
});
test('uses fixture', t => {
  t.is(t.context.user.id, 1);
});

Step 6 - Assertion API

Common matchers (full list at github.com/avajs/ava/blob/main/docs/03-assertions.md):

Step 7 - Snapshot tests

test('snapshot user profile', t => {
  const profile = renderProfile(user);
  t.snapshot(profile);
});

Snapshots stored under test/snapshots/ per config (Step 3). Update via npx ava --update-snapshots (or -u).

Step 8 - Exclusive + skipped

test.only('runs only this', t => { /* ... */ });
test.skip('skipped', t => { /* ... */ });
test.failing('expected to fail (TODO marker)', t => {
  t.is(1, 2);   // PASSES the test (because it's marked failing)
});
test.todo('write this test');   // marker; doesn't run

test.failing is AVA-distinctive - encodes "this test is expected to fail" so the suite signals when the underlying bug is fixed.

Step 9 - CI integration

- run: npm ci
- run: npx ava --tap | npx tap-junit > junit.xml
# Or built-in TAP reporter for any TAP consumer:
- run: npx ava --reporter=tap > test-results.tap

AVA emits TAP by default; for JUnit XML, pipe through tap-junit or similar.

Anti-patterns

Limitations

• Per-file process isolation has memory + spinup cost at scale (1000s of files).
• Some Node native modules don't survive process boundaries cleanly.
• React component testing requires @ava/babel + jsdom; less ergonomic than Jest/Vitest.
• Mocking story is "use a separate mocking library" (sinon, jest's vi.fn equivalent); no built-in mocks.

References

• ava-gh - repository, install, basic usage
• github.com/avajs/ava/tree/main/docs - full documentation
• github.com/avajs/ava/blob/main/docs/03-assertions.md - assertion API
• github.com/avajs/typescript - @ava/typescript adapter
• jest-tests, vitest-tests, mocha-tests, jasmine-tests - sister tools
• test-code-conventions - cross-plugin: test code hygiene