Fairlead platform overview
How the products work together to improve software quality and keep it from slipping as code changes.
Fairlead is a quality engineering platform for finding defects, fixing their causes, and building tests that catch regressions. Its products work from your project’s code, test results, and recorded evidence. Your team sets the priorities and decides which changes to merge.
How the platform works
Section titled “How the platform works”Start with a reported problem or a gap in test coverage. Fairlead uses the project context to investigate the problem or generate tests, runs checks, and returns changes and findings for review.
A browser recording can supply the evidence for a bug investigation. Test generation can start directly from the codebase. Both paths contribute changes that your team can review and keep in the repository.
Products
Section titled “Products”| Product | Role in the platform |
|---|---|
| Recorder | Capture browser actions, requests, console output, and screenshots taken during a check. Review and share the evidence to explain what happened. |
| Fix | Investigate a reported defect using code and available evidence. Propose a fix with reproduction tests, run checks, and deliver a pull or merge request for review. |
| Test | Find coverage gaps in selected code, generate unit tests, compile and run them, and deliver the tests as pull requests. |
| Rebalance (in development) | Identify checks that can move from expensive manual or end-to-end tests to faster integration and unit tests while preserving coverage. |
| Select (in development) | Use the relationship between code and tests to select which tests to run for each change. |
| Replay (in development) | Turn recorded manual checks into repeatable checks against new builds, and develop critical paths into regression tests. |
Improve quality, then maintain it
Section titled “Improve quality, then maintain it”Recorder helps make a problem understandable. Fix addresses its cause and adds a test for the failing behavior. Test broadens coverage beyond individual reported bugs. Together, these activities turn findings into fixes and lasting tests.
As the codebase grows, the planned roles of Rebalance, Select, and Replay are to keep that testing useful and manageable: move checks to the right layer, run the relevant tests for a change, and repeat important user journeys. New failures feed the next investigation, and the resulting tests protect the behavior on later changes.
The shared context is your project: its code, issues, evidence, and tests. You choose the scope of work; Fairlead returns proposed changes, check results, and findings for your team to assess. Repository access and a working build environment are needed for Fix and Test.
Recorder documentation
Section titled “Recorder documentation”- QA guides: record browser checks, assess outcomes, and share evidence.
- Developer guides: investigate failures, connect evidence to backend logs, and generate starter test scripts.
- Platform setup: connect your project and prepare the environment for platform work.
Shared concepts
Section titled “Shared concepts”Recording identifiers help connect browser evidence with backend logs. This requires connected recording and server-side logging of the supplied headers. Recorder can also be used locally, without an account.
For agents
Section titled “For agents”Use Open Markdown on a documentation page to read or copy its Markdown version. /llms.txt indexes the published content, and /llms-full.txt collects it in one file.