Compose Tests Agent Skill

Use when writing Compose UI tests in stripe-android — covers composeRule setup, Robolectric annotations, node assertions, and test tag patterns

981 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

1532

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/stripe/stripe-android --skill compose-tests

The instruction itself

9 sections, as written by the author

Compose UI Tests

Patterns for testing Jetpack Compose UI in the Stripe Android SDK.

Test Class Setup

Every Compose test needs three rules and Robolectric:

@RunWith(RobolectricTestRunner::class)
internal class MyComposableTest {
    @get:Rule
    val composeRule = createComposeRule()

    @get:Rule
    val composeCleanupRule = createComposeCleanupRule()

    @get:Rule
    val coroutineTestRule = CoroutineTestRule(UnconfinedTestDispatcher())
}

createComposeRule() — provides the Compose test harness
createComposeCleanupRule() — workaround for Robolectric resource leak (import from com.stripe.android.testing)
CoroutineTestRule — controls coroutine dispatching in tests

runScenario for Compose Tests

Use the same runScenario pattern from write-unit-tests, wrapping composeRule.setContent:

@Test
fun `required fields are visible`() = runScenario {
    page.country.assertIsDisplayed()
    page.zipCode.assertIsDisplayed()
    page.line1.assertDoesNotExist()
}

@Test
fun `input changes update state`() = runScenario(
    addressCollectionMode = AddressCollectionMode.Full,
) {
    page.zipCode.performTextReplacement("94100")
    assertThat(formState?.postalCode?.value).isEqualTo("94100")
}

private fun runScenario(
    addressCollectionMode: AddressCollectionMode = AddressCollectionMode.Automatic,
    block: TestScenario.() -> Unit,
) {
    composeRule.setContent {
        MyComposableUI(addressCollectionMode = addressCollectionMode)
    }
    block(TestScenario(MyPage(composeRule)))
}

private data class TestScenario(val page: MyPage)

Finding Nodes

| Finder | Use when |

|--------|----------|

| onNodeWithTag(TAG) | Element has a test tag (preferred) |

| onNodeWithContentDescription("desc") | Testing accessibility only — prefer test tags otherwise |

| onAllNodesWithTag(TAG) | Multiple elements share a tag |

| onNode(hasTestTag(TAG).and(hasText("x"))) | Combining matchers |

Assertions

| Assertion | Purpose |

|-----------|---------|

| assertIsDisplayed() | Element is visible |

| assertExists() | Element exists (may not be visible) |

| assertDoesNotExist() | Element not in hierarchy |

| assertIsNotDisplayed() | Exists but not visible |

| assertIsEnabled() / assertIsNotEnabled() | Enabled state |

| assertTextContains("text") | Text field contains value |

| assertContentDescriptionContains("desc") | Accessibility description |

| assert(hasText("text")) | General matcher assertion |

Actions

| Action | Purpose |

|--------|---------|

| performClick() | Tap element |

| performTextReplacement("text") | Set text field value |

| performScrollTo() | Scroll element into view |

Test Tags

Define tags as constants in production code, use Modifier.testTag():

// In production code:
internal const val SAVE_BUTTON_TEST_TAG = "save_button"

Box(modifier = Modifier.testTag(SAVE_BUTTON_TEST_TAG)) { ... }

// In test code:
composeRule.onNodeWithTag(SAVE_BUTTON_TEST_TAG).assertIsDisplayed()

Waiting for Recomposition

// Wait for pending recompositions
composeRule.waitForIdle()

// Wait for async content with timeout
composeRule.waitUntil(timeoutMillis = DEFAULT_UI_TIMEOUT.inWholeMilliseconds) {
    composeRule.onAllNodesWithTag(MY_TAG).fetchSemanticsNodes().isNotEmpty()
}

Common Mistakes

Missing composeCleanupRule — causes resource leaks with Robolectric, flaky tests
Missing @RunWith(RobolectricTestRunner::class) — Compose tests need Android framework
Using onNodeWithText for dynamic content — prefer test tags for stability
Not calling waitForIdle() after state changes — assertions may run before recomposition

Other skills for the same job

different authors, same section of the catalogue

Webapp Testing

by anthropics

vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens

Test Driven Development

by w95

×7

Use when implementing any feature or bugfix, before writing implementation code

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts

Verification Before Completion

by ZhanlinCui

×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

How to use it

Copy the folder

Take stripe/compose-tests from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.