TR

trail-sense-android-tests

Generates UI automation tests for the Trail-Sense Android application.

Install

mkdir -p .claude/skills/trail-sense-android-tests && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5298" && unzip -o skill.zip -d .claude/skills/trail-sense-android-tests && rm skill.zip

Installs to .claude/skills/trail-sense-android-tests

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Add UI automation tests to Trail-Sense Android app using AutomationLibrary. Use when asked to create, add, write, or implement automated tests, UI tests, integration tests, or androidTests for Trail Sense tools. Covers test class structure, AutomationLibrary functions, and testing patterns.
291 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Implements ToolTestBase inheritance for tool tests
  • Automates UI interaction via AutomationLibrary
  • Handles text-based view selection
  • Validates tool-specific quick actions
  • Structures tests within app/src/androidTest

How it works

Generates Kotlin test files that inherit from the custom TestBase class, utilizing library-specific click and input functions mapped to view resources.

Inputs & outputs

You give it
Tool name and target functionality requirements
You get back
Kotlin test class files with UI interaction logic

When to use trail-sense-android-tests

  • Write an integration test for a new tool
  • Create a UI automation script
  • Verify quick action functionality

About this skill

Trail Sense Android Tests

Create UI automation tests for Trail Sense tools using AutomationLibrary and ToolTestBase.

Test Structure

package com.kylecorry.trail_sense.tools.<toolname>

import com.kylecorry.trail_sense.R
import com.kylecorry.trail_sense.test_utils.AutomationLibrary.*
import com.kylecorry.trail_sense.test_utils.TestUtils
import com.kylecorry.trail_sense.test_utils.TestUtils.back
import com.kylecorry.trail_sense.test_utils.TestUtils.clickListItemMenu
import com.kylecorry.trail_sense.test_utils.ToolTestBase
import com.kylecorry.trail_sense.test_utils.views.*
import com.kylecorry.trail_sense.tools.tools.infrastructure.Tools
import org.junit.Test

class Tool<Name>Test : ToolTestBase(Tools.<TOOL_ID>) {

    @Test
    fun verifyBasicFunctionality() {
        hasText(R.id.title, string(R.string.tool_title))

        canCreateItem()
        canEditItem()
        canDeleteItem()
        verifyQuickAction()
    }

    private fun canCreateItem() { /* ... */ }
    private fun canEditItem() { /* ... */ }
    private fun canDeleteItem() { /* ... */ }
    private fun verifyQuickAction() { /* ... */ }
}

Location: app/src/androidTest/java/com/kylecorry/trail_sense/tools/<toolname>/Tool<Name>Test.kt

Workflow

  1. Inspect the target tool and nearby Tool*Test.kt files. This step is complete when the tool id, package, primary screen title, and existing test patterns are known.
  2. Add or update the test class under the location above. This step is complete when the test covers the requested workflow and uses stable selectors from the strategy below.
  3. Run a focused emulator integration test when an emulator is available. This step is complete when the requested test passes or the blocking reason is reported.

Selection Strategy: Text Over IDs

Prefer text-based selection for most interactions. Use IDs only when necessary.

Use Text For

// Clicking tabs, buttons, menu items, options
click(string(R.string.distance))
click(string(R.string.delete))
click("High")
click("Test Group")

// Verifying text anywhere on screen
hasText(string(R.string.no_paths))
hasText("Test Path")

// Dialog inputs (by label/hint)
input(string(R.string.name), "My Item")
input(string(R.string.distance), "1.0")

// Checkbox state by label
isChecked(string(R.string.tide_clock))

Use IDs Only For

// Title bars (for verification)
hasText(R.id.paths_title, string(R.string.paths))
hasText(R.id.tide_title, "Tide 1")

// Add/play buttons (no text label)
click(R.id.add_btn)
click(R.id.play_btn)

// Specific input fields
input(R.id.searchbox, "query")
input(R.id.tide_name, "Tide 1")
input(R.id.utm, "42, -72")

// Result/data views
hasText(R.id.result, "3.2808 ft")
hasText(R.id.total_percent_packed, "50% packed")

// Charts and special views
isVisible(R.id.chart)
scrollToEnd(R.id.scroll_view)

// Toolbar buttons
click(toolbarButton(R.id.paths_title, Side.Right))

Andromeda List Item IDs

List items use Andromeda library IDs:

click(com.kylecorry.andromeda.views.R.id.title)
hasText(com.kylecorry.andromeda.views.R.id.title, "Item Name")
hasText(com.kylecorry.andromeda.views.R.id.description, "Details")
click(com.kylecorry.andromeda.views.R.id.checkbox)
click(com.kylecorry.andromeda.views.R.id.trailing_icon_btn)
click(com.kylecorry.andromeda.views.R.id.menu_btn)

Common Patterns

Create/Edit/Delete Flow

private fun canCreateItem() {
    click(R.id.add_btn)
    click(string(R.string.new_item))
    input(string(R.string.name), "Test Item")
    clickOk()
    hasText("Test Item")
}

private fun canEditItem() {
    clickListItemMenu(string(R.string.edit))
    input("Test Item", "Test Item 2")
    clickOk()
    hasText("Test Item 2")
}

private fun canDeleteItem() {
    clickListItemMenu(string(R.string.delete))
    clickOk()
    not { hasText("Test Item 2", waitForTime = 0) }
}

Toolbar Menu

click(toolbarButton(R.id.title, Side.Right))
click(string(R.string.export))

Quick Actions

private fun verifyQuickAction() {
    TestUtils.openQuickActions()
    click(quickAction(Tools.QUICK_ACTION_ID))
    // Verify action occurred
    TestUtils.closeQuickActions()
}

Optional Elements

optional {
    hasText(string(R.string.disclaimer))
    clickOk()
}

Navigate Back

backUntil { isVisible(R.id.paths_title, waitForTime = 1000) }

Key Functions

FunctionUsage
click(text)Click by text (contains match)
click(text, exact = true)Click by exact text
click(R.id.x)Click by ID
hasText(text)Verify text on screen
hasText(R.id.x, text)Verify text in view
hasText(R.id.x, Regex(...))Verify regex pattern
input(R.id.x, text)Enter text by ID
input(label, text)Enter text by label
clickOk()Click OK in dialogs
clickListItemMenu(label)Click list item overflow menu
optional { }Ignore failures
not { }Assert action fails
string(R.string.x)Get string resource
scrollUntil { }Scroll until condition
backUntil { }Press back until condition

Running Tests

./scripts/run-emulator-integration-tests.sh
./scripts/run-emulator-integration-tests.sh com.kylecorry.trail_sense.tools.notes.ToolNotesTest 180

The script defaults to a 1800 second timeout. Most individual integration tests should finish in 60 to 180 seconds, so pass a shorter timeout for focused runs when practical.

Source Files

For complete API details and additional functions, read:

  • app/src/androidTest/java/com/kylecorry/trail_sense/test_utils/AutomationLibrary.kt
  • app/src/androidTest/java/com/kylecorry/trail_sense/test_utils/TestUtils.kt
  • app/src/androidTest/java/com/kylecorry/trail_sense/test_utils/views/

For example tests, see existing tool tests in:

  • app/src/androidTest/java/com/kylecorry/trail_sense/tools/*/Tool*Test.kt

When not to use it

  • Testing non-Android system components
  • Unit testing business logic without UI
  • Testing external network dependencies directly

Prerequisites

Trail-Sense codebaseAndroid Studio/Gradle environment

Limitations

  • Limited to Android platform integration
  • Requires familiarity with the internal view hierarchy
  • Dependent on AutomationLibrary updates

How it compares

It enforces a specific selection strategy of using visible text labels over brittle ID-based selectors.

Compared to similar skills

trail-sense-android-tests side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
trail-sense-android-tests (this skill)12moReviewIntermediate
android-kotlin74moNo flagsIntermediate
testing-android-code63moNo flagsIntermediate
android-emulator-skill04moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

android-kotlin

alinaqi

Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing

729

testing-android-code

bitwarden

This skill should be used when writing or reviewing tests for Android code in Bitwarden. Triggered by "BaseViewModelTest", "BitwardenComposeTest", "BaseServiceTest", "stateEventFlow", "bufferedMutableSharedFlow", "FakeDispatcherManager", "expectNoEvents", "assertCoroutineThrows", "createMockCipher", "createMockSend", "asSuccess", "Why is my Bitwarden test failing?", or testing questions about ViewModels, repositories, Compose screens, or data sources in Bitwarden.

611

android-emulator-skill

new-silvermoon

Production-ready scripts for Android app testing, building, and automation. Provides semantic UI navigation, build automation, log monitoring, and emulator lifecycle management. Optimized for AI agents with minimal token output.

00

android-kotlin-development

aj-geddes

Develop native Android apps with Kotlin. Covers MVVM with Jetpack, Compose for modern UI, Retrofit for API calls, Room for local storage, and navigation architecture.

268679

kotlin-multiplatform

vitorpamplona

Platform abstraction decision-making for Amethyst KMP project. Guides when to abstract vs keep platform-specific, source set placement (commonMain, jvmAndroid, platform-specific), expect/actual patterns. Covers primary targets (Android, JVM/Desktop, iOS) with web/wasm future considerations. Integrates with gradle-expert for dependency issues. Triggers on: abstraction decisions ("should I share this?"), source set placement questions, expect/actual creation, build.gradle.kts work, incorrect placement detection, KMP dependency suggestions.

32156

survey-sdk-audit

PostHog

Audit PostHog survey SDK features and version requirements

336

Search skills

Search the agent skills registry