Give one untested module its first regression suite.

We capture how one module behaves today, write its regression suite, set it up to run in your existing CI, and deliver a mutation report that shows what the tests still cannot see.

One untested module · up to 300 source lines · existing CI

JavaScript, TypeScript, or Python · no existing tests · up to 300 source lines

ONE MODULE NOT SEEN

No test says when the behavior moves.

An existing module can be important, familiar, and still have no test that says when its behavior moves. Module Baseline starts with the behavior the module has today. It does not quietly redesign the code or decide what it should have done.

The result is a regression suite running in your own CI, plus a mutation report that identifies the changes the suite fails to notice.

THE REGRESSION SUITE ONE MODULE TODAY'S BEHAVIOR, HELD

One module with no tests.

Module Baseline fits one existing JavaScript, TypeScript, or Python module that:

  • has no tests at all;
  • is up to 300 source lines, excluding blank and comment lines;
  • is already in use; and
  • belongs to a team with an existing CI pipeline and runner.

A module with even a partial test suite is outside this offer. A module over 300 source lines is declined rather than quoted.

INSIDE ONE ENGAGEMENT ONE MODULE UP TO 300 SOURCE LINES NO EXISTING TESTS YOUR EXISTING CI

From an agreed description to evidence about the suite.

  1. Intake. We read the module and write down what it appears to do, including behavior that may be accidental. You correct that description before implementation begins.
  2. Regression suite. We write tests for today's agreed behavior. If we find something that looks like a defect, we list it for you; we do not quietly change what callers receive.
  3. Running in your CI. The last stage is getting the suite to pass in your existing pipeline, on your runner. If your runner cannot run it, we say why in writing. The configuration change is part of the work.
  4. Mutation report. We make small deliberate changes and check whether the tests notice. The report names the changes they miss, so it shows where the suite can and cannot see.
THE SUITE NOTICED THIS CHANGE IT DID NOT — WHAT THE TESTS STILL CANNOT SEE THE SUITE NOTICED THIS CHANGE IT DID NOT — WHAT THE TESTS STILL CANNOT SEE

$ your test command regression suite — one module ✓ returns the same value for a known input ✓ raises on an empty path ✓ keeps the order it was given ✓ leaves what the caller passed unchanged suite green on your runner GREEN

Used first in our own trial.

As a trial, we chose an open-source module and ran the same four-stage method on it ourselves. The mutation report showed us which tests were doing real work and which changes they slept through.

THE SUITE NOTICED THIS CHANGE IT DID NOT — WHAT THE TESTS STILL CANNOT SEE

One module, with a hard edge around the work.

  • It is not a codebase or a second module.
  • It is not for a module that already has tests.
  • It is not for a module over 300 source lines. A larger module is outside this offer.
  • We do not rewrite or redesign the module, and we do not change what it does.
  • It is not a security review, compliance assessment, or legal opinion.
  • It ends in no certificate or sign-off.
  • We do not build a CI pipeline; the team needs one already.
  • There is no monitoring, subscription, retainer, or recurring work.
  • We promise no score, number of findings, or guaranteed outcome. The mutation report is a finding, not a score to hit.
OUTSIDE IT A SECOND MODULE OR A CODEBASE A REWRITE OR A REDESIGN A PIPELINE WE BUILD FOR YOU A SCORE OR A GUARANTEE

Ask about Module Baseline.

Module Baseline covers one untested JavaScript, TypeScript, or Python module of up to 300 source lines, through an agreed behavior description, a regression suite, green CI on the customer's runner, and a mutation report. Email us to ask about the service and pricing.

contact@theadage.co
A WRITTEN QUESTION A WRITTEN ANSWER A CALL OR A BOOKING