Join the waitlist

Fairlead RebalanceIn development

Test pyramid rebalancing

Fix the inverted pyramid.

Push slow, flaky end to end and manual tests down to fast, reliable layers. Analyze coverage and criticality to keep the same coverage with far fewer expensive tests.

Join the waitlist

Fairlead Rebalance is on the roadmap and not yet generally available. Join the waitlist to get early access and shape it with us.

The same suite, turned the right way up

Today

Rebalanced

Today is the sample suite drawn below. Rebalanced shows the shape Rebalance works toward.

Lower testing cost
Up to 70%
Faster feedback
80%
More unit tests
~10×

Flip the inverted pyramid

Top-heavy suites put most of the work in slow, flaky manual and end to end checks while faster layers stay thin. Rebalance maps the current mix, scores coverage and criticality, then moves checks toward faster layers without giving up what they cover.

What it readsYour test suitesevery layer, manual cases tooYour servicesinstrumented while tests runRun historyduration, failures and rerunsFor example, an end to end run that takes hours, or a manual pass before every releasefairleadREBALANCEYour teamMaptests per layerTracewhat each test runsScorewhat can movePush downto faster layersVerifysame coverageDeliverPR/MR per repoPer testservices it crossesmethods it runslines it coverssame code coveredpassesstable on rerunsa coverage gapis rewritten orthe check staysalreadycoveredbelowCovered below: removed in the same PRa criticaljourneyCritical journey: kept end to endReviewPR/MR per repositoryFaster testsunit, integration and APIRemoved teststhe checks they replacethen mergeLayer mixafter mergetodayafterManualEnd to endInterfaceAPIIntegrationUnitmeasured on every runReportcheck by checkKept checksand why each one staysManual casesthe new tests coverfor QA and the team
Illustrative workflow. A check moves only when faster tests cover the same code. Checks already covered lower are removed in the same pull request, and critical journeys stay end to end. The layer mix is the sample suite from the top of the page; the rebalanced bars show the direction of travel, not measured target counts. Each run maps the suite again, so merged changes set the next starting point.
What it readsYour test suitesevery layer, manual cases tooYour servicesinstrumented while tests runRun historyduration, failures and rerunsFor example, an end to end run that takes hours,or a manual pass before every releasefairleadREBALANCEMaptests and cases per layerTracethe code each test runsScorecost, criticality, flakinesscan movepushed downcovered belowremovedcritical journeykeptPush downthe lowest layer that proves itVerifythe same code coveredsame code coveredpassesstable on rerunsa coverage gapis rewritten orthe check staysDeliverPR/MR per repositoryYour teamReviewPR/MR per repositoryFaster testsunit, integration and APIRemoved teststhe checks they replacethen mergeReportcheck by checkKept checksand whyManual casesnow coveredfor QALayer mixafter mergetodayafterManualEnd to endInterfaceAPIIntegrationUnitmeasured on every run
Illustrative workflow. A check moves only when faster tests cover the same code. Checks already covered lower are removed in the same pull request, and critical journeys stay end to end. The layer mix is the sample suite from the top of the page; the rebalanced bars show the direction of travel, not measured target counts. Each run maps the suite again, so merged changes set the next starting point.

What it does

  • Coverage and criticality analysis

    Finds which expensive end to end checks can move to faster, cheaper layers without losing coverage.

  • Push tests down the pyramid

    Replaces slow, flaky end to end tests with deterministic integration and unit tests.

  • Grow the base

    Grows unit (~10×) and integration, the layers usually written as an afterthought.

  • Shrink the top

    Reduces the brittle manual and end to end tests that bloat scope every release.

Target outcomes

The same coverage, with far fewer end to end tests.

Up to 70%

Lower testing cost

80%

Faster feedback

Hear when Fairlead Rebalance is ready

Fairlead Rebalance is in development. Leave an address and a line about your stack, and we will write when it can run on it.

Use your company email address so we can reply about your request.

Include your languages, repository host and team size.

More from Fairlead