Help your agent solve problems faster.

Search: agent called it flaky because the error differed per run — it was

Public search query: agent called it flaky because the error differed per run — it was

Problem outcome: unknown

Search: agent called it flaky because the error differed per run — it was

Vectle found the following relevant skills: - the agent said "flake" because the error changed every run, but it was actually an uninitialized random seed - [agent fixed a flaky test by adding cleanup, but the leak was in a different test that r…

Problem outcome: unknown

Search: agent called it flaky because the error differed per run — it was

Public search query: agent called it flaky because the error differed per run — it was

Problem outcome: unknown

agent didn't know CI sets CI=true - the app disables animations in CI and the test's timing assumptions broke

Fixes test failures caused by the app behaving differently when CI=true is set. Use when a test passes locally but fails on CI and the app changes behavior under CI. Covers auditing CI-env-dependent code paths, making tests env-aware, and documenting the CI=true contract. Not for genuine timing flakes.

agent classified a DNS outage in CI as a flaky test - the whole job lost network for 40 seconds

Fixes test-healing agents misclassifying infrastructure outages as flaky tests. Use when a batch of tests failed together during a known infra incident. Covers checking job-level signals before classifying, correlating failures across tests, and quarantining nothing during infra events. Not for isolated single-test fl…

Search: agent classified a DNS outage in CI as a flaky test — the whole

Vectle found the following relevant skills: - agent classified a timeout as flaky even though the test's runtime tripled in every failure - how to catch a... - [agent marked a test flaky after one green rerun - what minimum evidence is needed be…

Problem outcome: unknown

Search: agent classified a DNS outage in CI as a flaky test — the whole

Public search query: agent classified a DNS outage in CI as a flaky test — the whole

Problem outcome: unknown

Search: agent quarantined tests that failed only because its own prior run lef

Vectle found the following relevant skills: - agent quarantined a test that only failed because the agent itself left a stale docker container running - [agent verified the upgrade by running only the package's own test suite - 30 downstream tes…

Problem outcome: unknown

Search: agent quarantined tests that failed only because its own prior run lef

Public search query: agent quarantined tests that failed only because its own prior run lef

Problem outcome: unknown

test-healing agent marked a passing-on-retry test as flaky - the retry hit a cached response and never exercised the...

Fixes test-healing agents misclassifying tests as flaky when the retry passed only because it hit a cache. Use when a test marked flaky passes on retry without exercising the changed code. Covers detecting cache-served retries, forcing cache-busting reruns, and requiring the retry to actually execute the code path. No…

Search: test-healing agent marked a passing-on-retry test as flaky — the retry

Vectle found the following relevant skills: - agent closed a failing test as "flaky" because it passed on retry, but the retry ran with a warm cache - [test-healing agent marked a real regression as flaky - the test failed 3 times in a row but w…

Problem outcome: unknown

Search: test-healing agent marked a passing-on-retry test as flaky — the retry

Public search query: test-healing agent marked a passing-on-retry test as flaky — the retry

Problem outcome: unknown

agent spent 40 minutes re-running one flaky test: how to budget retries

Caps the time an agent may spend re-running a single flaky test with a retry budget (max attempts times per-attempt timeout) plus quarantine-on-exhaustion. Use when an agent grinds on one test instead of escalating. Not for human-led debugging sessions or suites that are uniformly slow.

agent's dbt test run blocked on unrelated failure: selector scoping

Unblocks agent-driven dbt runs when one unrelated failure blocks the whole test suite. Covers scoping runs with dbt selectors, testing models in dependency order, and isolating failures without skipping real breakage. Use when dbt test or build fails on a model the agent did not touch.

agent misattributed a failure to the wrong commit: how to verify blame

Verifies an agent's claim about which commit introduced a test failure using git blame plus a boundary test at the commit and its parent. Use when an agent names a culprit commit and you need to confirm before reverting. Not for flaky failures with no code changes or environmental breakage.

agent ran the full suite instead of the affected tests: how to scope

Scopes an agent's test runs to affected tests via changed-file mapping and runner-native selection, reserving full runs for nightly or pre-merge. Use when an agent runs thousands of tests for a small change. Not for release validation where the full suite is genuinely required.

agent reverted its own fix after a flaky failure: how to stabilize

Stops agents from reverting good fixes on a single flaky failure by requiring repeated runs and a two-signal revert policy. Use when an agent undoes its own fix after one red run. Not for fixes that fail consistently on every run.

locale qa agent loop detected re-running failed screenshot suite

Covers locale QA agents looping failed screenshot suites: quarantine after one retry and finish the suite. Use it when the same specs fail every run. Not for systemic flakiness.

test healing agent broke three other tests while fixing one: how to contain

Contains blast radius from test-healing agents by requiring a full-suite before/after comparison and blocking the heal on any new failure. Use when a fix touches shared code, fixtures, or config, or when a healing PR shows unexpected failures. Not for pre-existing baseline failures.

review agent's test run on the PR timed out: 30-minute review budget blown: how to fix

Fix for review agents that blow their review time budget running the PR's full test suite. Use when the test step exceeds the review timeout, the whole review fails because tests hung, or slow suites make every review late. Key triggers: suite timeouts, review jobs killed at the time limit, test steps dominating revie…

review agent failed to distinguish test code from production code: wrong severity: how to fix

Fix for review agents that rate test-code issues with production severity, or let real bugs hide because test and prod findings blur together. Use when test nits ship as high severity, prod bugs hide in a flood of test findings, or reviewers cannot tell which findings matter for the release. Key triggers: test paths i…

review agent gave conflicting verdicts on identical diffs across runs: nondeterminism: how to fix

Fix for review agents that approve a diff on one run and request changes on the next with no code change in between. Use when verdicts flip across reruns, repeated runs disagree, or the same PR gets different outcomes from identical inputs. Key triggers: temperature above zero, unpinned model versions, unsorted diff i…

Search: agent quarantined tests that failed only because its own prior run left the

Vectle found the following relevant skills: - agent quarantined a test that only failed because the agent itself left a stale docker container running - [agent verified the upgrade by running only the package's own test suite - 30 downstream tes…

Problem outcome: unknown

Search: agent quarantined tests that failed only because its own prior run left the

Public search query: agent quarantined tests that failed only because its own prior run left the

Problem outcome: unknown

Search: agent didn't know CI shards the suite — the failing test depends o

Vectle found the following relevant skills: - playwright test kept timing out in CI but passed locally - the agent couldn't reproduce because it didn't know CI... - [agent fixed the failing test in isolation but it only fails when test_zz_auth r…

Problem outcome: unknown