auditing-compose-test-suite

Audit Jetpack Compose UI test suites for flakiness, slowness, and incorrect test logic.

303|10|Updated May 15, 2026

Search Tags:#debugging #jetpack-compose #ui-testing #flaky-tests #test-audit #compose-semantics #ci-performance

Ready to run

npx skills add https://github.com/skydoves/android-testing-skills --skill auditing-compose-test-suite

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auditing-compose-test-suite
Source: https://github.com/skydoves/android-testing-skills/tree/main/compose/audit/auditing-compose-test-suite
Command: npx skills add https://github.com/skydoves/android-testing-skills --skill auditing-compose-test-suite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies why an existing Jetpack Compose UI test suite is flaky, slow, or unreliable by running a structured, multi-phase review across setup, finders, assertions, actions, idle/time behavior, and debug quality.

Core Features & Use Cases

Six-phase test suite audit: Checks configuration correctness, semantics finder discipline, assertion strength, action correctness, timing/idle correctness, and actionable debug output.
Finding-to-fix routing: Each audit finding points to the specific sibling skill responsible for the fix, so the user can apply improvements without guesswork.
Non-mutating review: Produces a prioritized issue list and guidance without editing the test code, making it safe for iterative adoption.
Use cases: Run when you ask to review Compose tests, investigate CI-only failures, diagnose slow/flaky behavior, or want to know what to rewrite next.

Quick Start

Ask the AI to review your pasted Compose test file or test class for flakiness and slowness, and to produce a prioritized audit with routed fixes.

Frequently Asked Questions about auditing-compose-test-suite

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

FAQPage Schema

Why are my Jetpack Compose UI tests flaky on CI but pass locally?▼

Jetpack Compose UI tests flake on CI due to timing, idle resource, or finder issues. A structured test suite audit reviews setup, semantics finders, and assertions to diagnose configuration correctness and identify CI-specific failures.

How do I audit Jetpack Compose tests for incorrect test logic and slowness?▼

To audit Jetpack Compose tests, run a six-phase review checking setup, finders, assertions, actions, timing, and debug output. This non-mutating analysis produces a prioritized issue list to identify slow or incorrect test logic.

What is the best way to find high-severity issues in Compose test suites?▼

The best way to find high-severity issues in Compose test suites is enforcing safety rules that flag Thread.sleep and deprecated performGesture. A multi-phase audit routes these findings to specific fixes for actionable improvements.

Can I review existing Compose Test.kt files without modifying the test code?▼

Yes, you can review existing Compose Test.kt files through a non-mutating audit that generates a prioritized issue list and guidance. This approach diagnoses flakiness and slowness safely without editing your test code.

Does a Compose test audit check semantics finder discipline and assertion strength?▼

Yes, a Compose test audit checks semantics finder discipline and assertion strength across six phases. It evaluates configuration correctness, action correctness, timing behavior, and actionable debug output to ensure reliable test execution.

When do I need to audit my Compose test suite for flakiness?▼

You need to audit your Compose test suite for flakiness when tests behave differently between local and CI runs, after migrating between Compose test APIs, or when you want to know what test logic to rewrite next.