auditing-compose-test-suite

Audit Jetpack Compose UI test suites across six phases for flakiness and anti-patterns.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill auditing-compose-test-suite-trancee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auditing-compose-test-suite
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/compose/audit/auditing-compose-test-suite
Command: npx skills add https://github.com/trancee/MeshLink-template --skill auditing-compose-test-suite-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common pain points of flaky, slow, or brittle Jetpack Compose UI tests by providing a structured, six-phase audit that identifies architectural smells and testing anti-patterns.

Core Features & Use Cases

  • Six-Phase Audit Pipeline: Sequentially evaluates setup, finder discipline, assertion strength, action correctness, idle synchronization, and debug output.
  • Actionable Routing: Automatically maps identified test smells to specific, specialized sibling skills for remediation.
  • Use Case: Use this when your CI pipeline reports intermittent test failures or when you need to ensure a new feature's test suite adheres to industry-standard Compose testing best practices.

Quick Start

Use the auditing-compose-test-suite skill to perform a full audit on the provided MyFeatureTest.kt file and generate a prioritized issue report.

Frequently Asked Questions about auditing-compose-test-suite

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

FAQPage Schema
How do I fix flaky Jetpack Compose UI tests in my CI pipeline?

To fix flaky Jetpack Compose UI tests, you need a systematic audit that identifies architectural smells and synchronization issues. A six-phase audit evaluates test setup, semantics tree navigation, and idle synchronization to pinpoint intermittent failure causes and map them to remediation.

What are common Jetpack Compose UI test smells and anti-patterns?

Common Jetpack Compose UI test smells include weak assertion strength, incorrect action logic, and poor semantics tree navigation. A structured audit evaluates finder discipline and synchronization to detect these anti-patterns before they cause brittle tests.

How do I audit my Compose UI test suite for performance bottlenecks?

To audit a Compose UI test suite for performance bottlenecks, execute a sequential evaluation across six phases covering setup, finder discipline, and idle synchronization. This identifies slow test execution and architectural anti-patterns in Android and host-side environments.

Does the Compose UI test audit work for both Android and host-side test environments?

Yes, the Compose UI test audit evaluates synchronization logic and test smells across both Android and host-side test environments. It assesses setup and semantics tree navigation to ensure deterministic and maintainable UI testing across your stack.

What is the best way to ensure my Compose UI tests follow industry-standard best practices?

The best way to ensure Compose UI tests follow industry-standard best practices is to run a comprehensive audit evaluating assertion strength and finder discipline. This maps identified test smells to specialized remediation steps for robust test architecture.