Testing icons

The 95 testing icons in Developer Tools, described

Accessibility testaccessibility-test

A person with arms out — checked for everyone who will use it.

Add runadd-run

A run card with a plus under its play — queue another run in the list.

Arrange, act, assertarrange-act-assert

A clipboard with three lines — set it up, do the thing, check the result.

Assertassert-check

Assert — if this is false, everything stops, an invariant that must hold.

Assert failassert-fail

An X held between brackets — an assertion in the code that failed its check.

Assert passassert-pass

A check held between brackets — an assertion in the code that held true.

Assertionassertion

An assertion — the claim a test makes and expects to hold on every run.

Assertion failedassertion-fail

The flask with a cross in it — the check that came out wrong.

Approve baselinebaseline-approve

A bracket pair with a check and a line drawn under it — the current state accepted as the new normal.

Benchmark runbench-run

A benchmark run — how fast it goes, exactly, timed and measured against a baseline.

Benchmarkbenchmark-code

A code benchmark — how fast it runs, measured fairly and compared.

Chaos testchaos-test

The flask with a bolt in it — something broken on purpose to see what happens.

Code smellcode-smell

A bracket pair with a wisp in it — code that works but tells you something is off.

Contract testcontract-test

The flask with an equals sign — two sides checked against the same agreement.

Coveragecoverage

Test coverage — how much of the code the tests actually touch, as a percentage.

Branch coveragecoverage-branch

A bracket pair with a fork in it — both sides of every if, run.

Coverage gapcoverage-gap

A bracket pair with a line and a cross under it — the part no test reaches.

Line coveragecoverage-line

A bracket pair with a line and a check under it — this line ran.

Coverage trendcoverage-trend

A bracket pair with three bars climbing — coverage over time.

Cyclomatic complexitycyclomatic-complexity

A bracket pair with a decision diamond and a path out — how many ways through a function.

Dead code checkdead-code-check

A bracket pair with a line struck through — code nothing calls any more.

Dependency auditdependency-audit

A clipboard with a shield on it — every package checked against known problems.

Duplication checkduplication-check

A bracket pair with the same line twice, one shifted — code copied where it should have been shared.

End-to-end testend-to-end-test

The flask with a line from wall to wall — the whole path tested as a user would take it.

Factoryfactory-data

A works with a chimney over a tray — test data made to order, one record at a time.

Fakefake-service

A machine frame with a box in it — a working stand-in, simpler than the real thing.

Fault injectionfault-injection

The flask with an arrow dropping down its neck — a failure fed in by hand.

Favourite runfavorite-run

A run card with a heart under its play — a run configuration you keep coming back to.

Filter runfilter-run

A funnel with a play below its stem — run only what the filter selects.

Fixturefixture-data

A slab laid in a tray — the data a test starts from, prepared ahead.

Flaky testflaky-test

A flaky test — one that passes and fails on the same code, unreliable and intermittent.

Format checkformat-check

A bracket pair with lines set in from the margin — code laid out the way the formatter wants.

Fuzzfuzz

Fuzz testing — feed a program random chaos until it confesses a bug.

Generative testgenerative-test

A die showing three — property-based tests that roll random inputs.

Given, when, thengiven-when-then

A clipboard with a staircase on it — a test told as a story, step by step.

Golden filegolden-file

A golden file — the blessed output every run is measured against.

Integration testintegration-test

The flask with two points tied together — pieces tested as they work with each other.

Invariantinvariant

Two equal lines held between brackets — an invariant that must stay true throughout.

Lint rulelint-rule

A bracket pair with a line and a squiggle under it — the rule that underlines it.

Lintlint-run

Lint — the marks under whatever needs fixing, style warnings from a check.

Load testload-test

Axes with a line that ramps up, holds, and ramps down — expected traffic, applied on purpose.

Locked runlocked-run

A padlock with a play on its body — a run that cannot be started without permission.

Mockmock

A mock — a fake that stands in for the real dependency in a test.

Mockmock-server

A machine frame with quotation marks in it — a stand-in that expects to be called a certain way.

Mutant killmutant-kill

A crossed-out mutant — a mutation the test suite caught and killed.

Mutation scoremutation-score

A bracket pair with a target in it — how many planted bugs the tests caught.

Mutation testmutation-test

A mutation test — break the code on purpose and check that the tests notice.

Postconditionpostcondition

A check placed after the block — a postcondition that must hold once code has run.

Preconditionprecondition

A check placed before the block — a precondition that must hold before code runs.

Property testproperty-test

A property test — many generated inputs against one property that must always hold.

Regression testregression-test

A regression test — proof that the old thing still works after a change.

Review commentreview-comment

A bracket pair with a speech bubble in it — a note left on a line of code.

Run alertrun-alert

A play button beside an alert mark — a run that needs attention.

Run checkpointrun-checkpoint

A run card with a flag under its play — a checkpoint saved partway inside a run.

Run fasterrun-faster

A run card, a double chevron under its play — speed a run up, faster execution.

Run goalrun-goal

A trophy with a play in its bowl — what a run is trying to achieve.

Run historyrun-history

A run card with rows under its play — every run so far, most recent first.

Run idlerun-idle

A run card with a Z under its play — a runner with nothing to do right now.

Run labelrun-label

A label with a play inside — a run with a name attached to it.

Run nextrun-next

A run card with an arrow under its play — start the next run in the queue.

Run trendrun-trend

A run card with a rising line under its play — how runs are trending.

Runnerrunner

A play button inside a box — the runner that executes a job or a test suite.

Safe runsafe-run

A run card with a shield under its play — a run kept inside its guardrails.

Saved runsaved-run

A bookmark with a play inside — a run configuration saved to reuse.

Smoke suitesmoke-suite

The flask with a wisp in it — the handful of tests that say whether anything works at all.

Snapshot testsnapshot-test

A window with a lens in it — output captured once and compared against ever after.

Soak testsoak-test

Axes with a line that rises and then holds a long while — steady load kept up for hours.

Spike testspike-test

Axes with one sharp spike — a sudden burst, then nothing.

Spyspy-call

A machine frame with an eye in it — the real thing, with every call recorded.

Static analysisstatic-analysis

A bracket pair with an eye in it — code read for bugs without being run.

Stress teststress-test

Axes with a line that climbs off the chart — load pushed past what the system is for.

Stubstub-service

A machine frame with a short bar in it — a stand-in that answers with a fixed value.

Stubstub-tool

A stub — looks like the tool but does nothing, a hollow stand-in for tests.

Test data buildertest-data-builder

One block set down in a tray — test data assembled a field at a time.

Test doubletest-double

A test double — the understudy that takes the stage in place of a real dependency.

End-to-end testtest-e2e

An end-to-end test — the whole user journey checked from start to finish.

Test filetest-file

A page with a play button on it — a test file ready to run in the suite.

Focus testtest-focus

The run card with a target — only this test, for now.

Test historytest-history

A clipboard with a clock on it — how a test has done over its last runs.

Test ordertest-order

The run card with three lines — tests run in a fixed sequence.

Test ownertest-owner

A clipboard with a person on it — whose name is on this test when it breaks.

Parallel teststest-parallel

The run card with three bars side by side — tests run at the same time.

Test pyramidtest-pyramid

A clipboard with rows narrowing upward — many unit tests, fewer above.

Test quarantinetest-quarantine

The run card with a box in it — a flaky test set aside so it cannot block the rest.

Test reporttest-report

A clipboard with a check on it — what ran, what passed, what did not.

Test retrytest-retry

The run card with an arrow looping back — a failed test given another go.

Test runtest-run

A test run — the suite is going, tests in progress with results coming in.

Test selecttest-select

Test select — run just the one test that matters right now, not the whole suite.

Test shardtest-shard

A test shard — the suite split several ways so CI finishes sooner.

Skip testtest-skip

The run card with a skip mark — a test passed over without running.

Test timeouttest-timeout-q

The run card with an hourglass — a test stopped for taking too long.

Unit testtest-unit

A unit test — one small piece of code checked on its own, in isolation.

Unit testunit-test

The flask with one point in it — one small piece tested on its own.

Variantvariant

A variant — the same thing with one difference, an alternative version.

Visual diffvisual-diff

A window split in two with a point each side — two renderings compared pixel by pixel.

In code, each is one import — import { AccessibilityTest } from "@iconmind/react/icons/accessibility-test" — and the same name in Vue, Svelte, Solid, Preact, React Native, Astro, Blade and Flutter.

Narrow it by tag