Starting material
Public repo + test command
Factoriesengineering
Working14-day run0
each with a before and after test
81%
the rest reported as unconfirmed
0
commented instead of duplicated
$0.00
of $25.00 cost budget
| Task | Status |
|---|---|
| Read Vercel deployment events | Idle |
| Reproduce a checkout error | Idle |
| Review 4 draft pull requests | Idle |
| Write a failing test for the session bug | Idle |
| Comment the fix on a Linear issue | Idle |
Run plan
Each factory run reads deployment events, open issues, and code, then opens a tested draft pull request for each bug nobody filed.
Ready for your review
Review 4 draft pull requests
Each one names the bug, reproduction steps, root cause, fix, and test results.
Sample run: Engineering
A sample run, start to finish. It reruns a suspect test to measure its pass rate, isolates the condition that makes it fail, and returns a patch with its pass rate after the change.
FactoriesEngineering run
IdleIllustrative runTypeError: Cannot read properties of undefined (reading 'currency')fix(checkout): price a cart that has no region yet
fix/checkout-missing-region into main
Start with your source
The trial begins with the material below. No mandatory OAuth connection is needed for accessible public sources or material you supply.
Public repo + test command
Set the targets, questions, acceptance criteria, and exclusions. The scope controls what the report investigates.
Manual is the default. Choose hourly, daily, or weekly recurrence when repeated observation is useful.
How the trial runs
Prepare the suite, measure each suspect test's pass rate, isolate what triggers failure, patch and rerun, then return the ledger.
Check out the current commit, install dependencies, and confirm the suspect tests run.
Run each suspect test repeatedly and record its pass rate over N runs.
Vary ordering, timing, and shared state to find the condition that makes the test fail.
Write a patch for the trigger and measure the pass rate again over the same number of runs.
Return each test's before and after pass rate, the failure condition, and the patch for review.
What you review
Failure conditions, timing or shared-state hypotheses, repeated-run requirements, and repair plans.
Public sources can be read again. Uploaded files remain snapshots: provide a fresh upload to assess new private facts. Earlier saved evidence provides a comparison baseline, not a live connection to the original system.
Browser interaction, code execution, authenticated access, and unsupported file formats may be unavailable in a run. Missing access or tools appear as coverage gaps, never as a passed test. Proposed fixes and drafts remain in the report.
Returns a report and proposed next steps for your review. External messages, source changes, payments, and submissions are outside this trial.
Inputs, recurrence, evidence, and the boundary of the report.
Need help defining the source or scope? Contact us
Supply the source, review the scope, and get an initial report before choosing a recurring cadence.