Skip to content
Qualflare

CI/CD & Velocity

Monorepo testing

Also known as: monorepo test aggregation

Monorepo testing is running and aggregating tests for many projects or packages that live in one repository, where a single commit can touch code shared across several of them.

A monorepo concentrates many projects — often in different languages and frameworks — in one place. That makes sharing code easy but testing harder: a change to a shared library can affect dozens of packages, several test runners produce results in different formats, and it gets unclear who owns which failing test.

The two core monorepo testing problems are selection and aggregation. Selection means running only the packages a change actually affects, rather than the whole repo, on every commit. Aggregation means combining results from Playwright, Jest, pytest, JUnit, and others into one view of the run instead of several disconnected reports.

  • One repo, many packages/frameworks — a single change can affect many of them.
  • Selection: run only the affected packages, not the whole repo, per change.
  • Aggregation: unify multiple runners’ results into one report and ownership view.

Learn more

Related terms

Smart test selection Test impact analysis (TIA) Test sharding Test parallelization Flaky test

See it in your own test results

Qualflare detects flaky tests, clusters failures by root cause, and scores release risk from the test results you already produce in CI. Start free.

Start free with Qualflare

← Back to the testing & observability glossary.

Last reviewed June 11, 2026