Moderate drift detected. Response shape changed and latency increased after mapper update.
Use Case
CI integration
Gate every pull request on runtime behavior, not just test pass rates.
GitHub Actions
- name: Install Logito run: curl -fsSL https://get.logito.dev | sh - name: Logito check run: logito ci check
Add two steps to your existing workflow. Logito handles the rest.
Install CLI
Takes ~30 seconds. No signup required.
Runs locally. No data leaves your system.
Works with any API, service, or local environment.
What happens after you install:
- 1. Start a run
- 2. Trigger your system
- 3. See exactly what changed
Problem
Tests pass. Behavior still changed.
- Unit tests cover logic, not runtime drift.
- Latency regressions, missing response fields, and error rate shifts slip through green builds.
- By the time a behavior change reaches production, nobody remembers which PR introduced it.
Hidden Issue
The hidden issue is that CI only validates code, not system behavior.
A passing test suite tells you the code works in isolation. It does not tell you whether the running system behaves the same as yesterday.
- Response shapes can shift without breaking any assertion.
- Performance regressions only surface under real request patterns.
- Config and dependency changes affect behavior without touching a test file.
Logito Flow
Capture -> Compare -> Gate -> Report
Capture Run your test scenario in CI to generate runtime data.
Compare Logito compares the run against a known good baseline.
Gate The build passes, warns, or fails based on your drift threshold.
Report A summary posts to the PR with key issues and likely contributors.
Example
Run it once. Review what changed. Act with context.
GitHub Actions
- name: Install Logito run: curl -fsSL https://get.logito.dev | sh - name: Logito check run: logito ci check
Add two steps to your existing workflow. Logito handles the rest.
CI check output
+ /v1/quotes latency regressed by 18%+ estimate payload now omits carrier_notes- baseline response timing was within range
Review the flagged endpoints, fix or accept the drift, then merge with confidence.
Install Fast
Install, start, and review the next run.
Fast path
brew tap progadigital/tap brew install logito logito dev start
Takes ~30 seconds. No signup required.
Benefits
Why teams use this loop
- Catch runtime regressions before they reach production.
- Gate PRs on behavioral drift, not just test assertions.
- Get a clear summary of what changed and why on every pull request.
Positioning
Why this catches drift faster
Tests tell you the code compiles and passes assertions.
CI dashboards tell you the build succeeded.
Logito CI tells you whether the system still behaves the same.
Every PR without a behavioral gate is a chance for silent drift to land in production. The earlier you compare, the cheaper the fix.
Install
Add Logito to your CI pipeline today.
Two workflow steps. One drift threshold. Full behavioral coverage on every PR.
Takes ~30 seconds. No signup required.
Runs locally. No data leaves your system.
Works with any API, service, or local environment.
Also Useful For