.NET
Artifacts: VSTest TRX (auto-enabled or imported via -f)
# Pulse automatically injects --logger:trx$pulse-agent test -- dotnet test$pulse-agent summary --vcs-token ${GITHUB_TOKEN}Test · TRX, nextest & JUnit
Nothing erodes trust in CI faster than intermittent red builds. Developers click “Re-run failed jobs” three times, waste 40 minutes waiting for runners, and eventually start ignoring test failures altogether.
Codebase Pulse ingests VSTest TRX, cargo nextest / libtest JSON, and JUnit XML alongside live runner hardware telemetry. It separates real code regressions from same-commit flaky tests and from infrastructure outages — posting a clean verdict on the pull request.
End blind CI reruns
Know immediately if a test failed because of your commit, a known flaky race condition, or a starved CI VM.
Protect clean baselines
Mass failures (DB container crash) and noisy runs skip candidate and baseline updates so outages do not flood the flaky list.
Actionable root-cause hints
See whether a flaky test fails alongside its class (shared fixture) or, when timing data exists, during parallel execution overlap (race hint).
PR-first workflow
When a test step finishes, Pulse posts the pass rate, normalized duration delta, and a categorized breakdown of failures. Developers see right on the PR whether they broke a test or hit an existing flaky candidate.
Rollout without friction
Start passively or pass --warn-only to post the PR report with exit code 0. Enable --guard when your team is ready to block merges on regressions.
┌──────────────────────────────────────────────────────────────────────────────┐ │ Regression detected: 1 of 617 test(s) failed; test process exited with code 1│ └──────────────────────────────────────────────────────────────────────────────┘
┌─────────┬───────┐ │ Metric │ Count │ ├─────────┼───────┤ │ Total │ 617 │ │ Passed │ 616 │ │ Failed │ 1 │ │ Skipped │ 0 │ │ Flaky │ 1 │ │ Slow │ 2 │ └─────────┴───────┘
┌──────────────────────────────────────────────────────────────────────────────────┬────────────────────────────────────────────────┐ │ Test │ Error │ ├──────────────────────────────────────────────────────────────────────────────────┼────────────────────────────────────────────────┤ │ AcmePlatform.Backend.Payments.Tests.WebhookDispatcherTests › Should_Sign_Payload │ Expected HMAC signature to match payload bytes │ └──────────────────────────────────────────────────────────────────────────────────┴────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┬─────────────────────────────┐ │ Test │ Duration │ ├──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┼─────────────────────────────┤ │ AcmePlatform.Agent.Application.Tests.Features.Run.SystemMetricsMonitorTests › AcmePlatform.Agent.Application.Tests.Features.Run.SystemMetricsMonitorTests.MonitorSession_ShouldAccumulateSnapshotsAndProduceValidDTO │ 12.19s (+22.0% vs baseline) │ │ AcmePlatform.Agent.Infra.Tests.Services.AgentEnvironmentDetectorTests › AcmePlatform.Agent.Infra.Tests.Services.AgentEnvironmentDetectorTests.Detect_ShouldReturnHardwareMetricsAndSignature │ 5.69s (+22.0% vs baseline) │ └──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┴─────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────────────┬────────────┐ │ Test │ Confidence │ ├──────────────────────────────────────────────────────────────────────────────────────┼────────────┤ │ AcmePlatform.Backend.Payments.Tests.StripeRetryTests › Concurrent_Charge_Idempotency │ 80% │ └──────────────────────────────────────────────────────────────────────────────────────┴────────────┘
Under the hood
Tests: PR guard failed — 1 failing test, 1 in-run flaky, duration +6.9% vs baseline (within +20% gate).
First, NoiseDetector flags runs with CPU saturation, disk I/O surges vs hardware baseline, RAM pressure, or VM core mismatches — often together with a duration spike. Second, IsMassFailure detects suite-wide infrastructure crashes (many failures at once when a shared dependency dies). Third, selector-change detection spots when the effective test filter changed between runs.
Pulse tracks commit SHAs across a sliding window of recent runs. A test that flips between pass and fail on the same commit or passes on retry is scored as Flaky. A test that breaks on a new commit and stays red is classified as a real bug (NewFailure).
For every flaky candidate, FlakyDiagnosticsCalculator computes co-failed counts in the same test class/group (shared fixtures or DB state), concurrent timeline overlap when start/end timestamps exist (race or contention hints), and normalized failure signatures.
Engineering questions answered
Pulse checks whether the test flipped on the same commit SHA or passed on retry versus transitioning from green to red across commits.
Mass-failure protection recognizes infrastructure outages and prevents hundreds of tests from polluting your flaky candidate list or duration baselines.
Inspect whether the test fails alone under high parallel overlap (race condition / resource contention) or always fails together with sibling tests in the same fixture.
No. After enough consecutive clean passes — fewer for a fixed failure, more for a long-lived flaky candidate — Pulse evicts it automatically.
Forensic web UI
Most runs end with CI output or a PR comment. When you need to investigate a structural bottleneck, audit a release branch, or compare historical runs, open the full Tests views in Codebase Pulse.
01 · Flaky Diagnostics
Prioritize the flaky tests that hurt the team most. Each candidate shows its flip rate, whether it passed on retry, how many distinct error signatures it produces (stripped of random GUIDs and timestamps), and whether it correlates with parallel execution.
Zero-code on the runner
No SDK in your application. Pulse enables and reads the artifacts your toolchain already emits and uploads metadata to the product backend.
.NET
Artifacts: VSTest TRX (auto-enabled or imported via -f)
# Pulse automatically injects --logger:trx$pulse-agent test -- dotnet test$pulse-agent summary --vcs-token ${GITHUB_TOKEN}Rust
Artifacts: cargo nextest JSON (auto-enabled); cargo test libtest JSON on nightly or with -Z flags
# nextest: libtest JSON enabled automatically$pulse-agent test -- cargo nextest run$pulse-agent summary --vcs-token ${GITHUB_TOKEN}