skills.rest
Acendas
AcendasOFFICIAL
Explore all skills by this author →
GitHub

ad-bisect-flaky

Bisect flaky Android tests by authoring Debug Plans and looping am instrument runs.

3|Updated May 10, 2026
Search Tags:#automation#testing#instrumentation#android#bisect#flaky-tests#debug-plan
One-click install
npx skills add https://github.com/Acendas/android-debugger --skill ad-bisect-flaky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ad-bisect-flaky
Source: https://github.com/Acendas/android-debugger/tree/main/skills/ad-bisect-flaky
Command: npx skills add https://github.com/Acendas/android-debugger --skill ad-bisect-flaky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineers systematically identify the cause of flaky Android tests by authoring a Debug Plan, executing the test in cycles, and comparing results to locate the first divergence.

Core Features & Use Cases

  • Structured bisect workflow: creates and runs Debug Plans, collects per-round snapshots and locals, and surfaces the trigger.
  • Plan templating and validation: uses a predefined plan-template.json to install class and line breakpoints and harvest results.
  • Use Case: when a test passes sometimes and fails other times, the skill guides you to the exact code path or timing window causing the flake.

Quick Start

Draft a Debug Plan, run the test in instrument mode, attach the debugger per round, and compare results to identify the divergence.

Frequently Asked Questions about ad-bisect-flaky

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug flaky Android instrumentation tests that pass sometimes and fail other times?▼

To debug flaky Android instrumentation tests, author a structured Debug Plan using a plan-template.json schema, run the test in cycles with am instrument, and compare per-round snapshots to locate the exact divergence causing the flake.

What is a Debug Plan for bisecting flaky tests and how does it work?▼

A Debug Plan for bisecting flaky tests is a structured schema that installs class and line breakpoints. It executes looping test runs, captures per-run locals and snapshots, and reports divergences to isolate the specific trigger.

Can I use this bisect workflow for Android tests not running with am instrument?▼

No, this bisect workflow specifically applies to instrumentation-based tests running with am instrument. It requires capturing per-run snapshots and attaching the debugger per round to observe divergences.

How do I locate the first divergence in an Android flaky test run?▼

You locate the first divergence in an Android flaky test by submitting per-round Debug Plans that install breakpoints, harvesting per-run locals and snapshots across looped test runs, and comparing results until the divergence is observed.

What do I need to start bisecting flaky Android tests?▼

To start bisecting flaky Android tests you need the plan-template.json schema, the ability to capture per-run snapshots and locals, and an environment supporting am instrument for strict validation of plan structure.

Related Skills

Explore More Software Engineering Skills→
AcendasAcendas
3

ad-catch

Identifies and traps specified Android exceptions, captures frame locals, and generates a root-cause report.

Official
Intermediate
Camilo8902Camilo8902

flaky-test-detective

Diagnose flaky tests by analyzing execution logs and failure patterns.

Community
Advanced
skydovesskydoves
303

scripting-adb-for-ci

Parses instrumentation status codes and orchestrates adb-based Android test runs for CI.

Community
Advanced
canyonlabzcanyonlabz
4

jmeter-debugging

Debug JMeter scripts through iterative smoke tests and log analysis.

Community
Advanced