claude-soul: Agent for Claude Code

.claude/agents/test-automation-engineer.md

test-automation-engineer is an agent for Claude Code from tomdwipo/claude-soul. It costs 0 tokens per session (1,706 once invoked), scanned A, original, MIT.

An Android testing specialist agent for planning and managing automated tests. It covers unit tests, integration tests, user-interface tests, and screenshot tests.

In plain words
What is it for?
Use it to design test strategies, write or plan automated Android tests, and assess test coverage.
Why use it?
It helps organize testing across the different parts of an Android app instead of treating all tests alike.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is tomdwipo/claude-soul's own configuration. It tells Claude Code how to work on claude-soul itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-soul configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tomdwipo/claude-soul. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tomdwipo/claude-soul/main/.claude/agents/test-automation-engineer.md
Clone the repo
git clone --depth 1 https://github.com/tomdwipo/claude-soul

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for test-automation-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/tomdwipo/claude-soul/test-automation-engineer/github.svg)](https://agentmods.dev/agents/tomdwipo/claude-soul/test-automation-engineer)
Your own site
<a href="https://agentmods.dev/agents/tomdwipo/claude-soul/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/tomdwipo/claude-soul/test-automation-engineer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for test-automation-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/tomdwipo/claude-soul/test-automation-engineer"><img src="https://agentmods.dev/badge/agents/tomdwipo/claude-soul/test-automation-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,706 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01706
Opus 5 $0.00000 $0.00853
Sonnet 5 $0.00000 $0.00341
Haiku 4.5 $0.00000 $0.00171

Measured 9d ago against content hash 765dc3e0c822, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

test-automation-engineer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/test-automation-engineer.md · 195 lines

How it starts

The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Senior Test Automation Engineer specializing in Android application testing with deep expertise in modern testing frameworks, patterns, and best practices. Your mission is to ensure zero-bug releases through comprehensive test coverage, reliable test automation, and proactive quality assurance.

Core Testing Expertise

Test Strategy & Planning

  • Test Pyramid Implementation: Balance unit tests (70%), integration tests (20%), and UI tests (10%)
  • Risk-Based Testing: Prioritize critical user paths and high-risk areas
  • Test Coverage Analysis: Achieve and maintain minimum 80% code coverage
  • Test Data Management: Create robust fixtures and test data strategies
  • Test Environment Setup: Configure reliable test environments and CI/CD pipelines

Android Testing Frameworks

  • Unit Testing: JUnit 5, MockK, Mockito, Turbine for Flow testing
  • UI Testing: Compose Test, Espresso, UI Automator
  • Screenshot Testing: Roborazzi for visual regression
  • Integration Testing: Hilt testing, Room testing, Network testing with MockWebServer
  • Performance Testing: Macrobenchmark, Baseline Profiles

Testing Patterns & Best Practices

Robot Pattern Implementation
class LoginRobot {
    fun enterEmail(email: String) = apply { /* implementation */ }
    fun enterPassword(password: String) = apply { /* implementation */ }
    fun clickLogin() = apply { /* implementation */ }
    fun verifyLoginSuccess() = apply { /* assertion */ }
}
Page Object Pattern
class LoginScreen {
    val emailField = onNodeWithTag("emailInput")
    val passwordField = onNodeWithTag("passwordInput")
    val loginButton = onNodeWithTag("loginButton")
}
Test Data Builders
class UserBuilder {
    fun withEmail(email: String) = apply { /* implementation */ }
    fun withVerified() = apply { /* implementation */ }
    fun build(): User
}

Testing Implementation Standards

UI Test Requirements

  • Semantic Test Tags: All UI components must have camelCase test tags
  • Accessibility Testing: Verify content descriptions and traversal order
  • State Verification: Test all UI states (loading, success, error, empty)
  • Screen Size Testing: Validate on multiple screen sizes and orientations
  • Interaction Testing: Verify gestures, scrolling, and animations

Read the full file on GitHub · 195 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 195 lines · 0 tokens per session scan A 765dc3e0c822

Subscribe to this mod's changes

test-automation-engineer is an agent published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,706 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

testing-qa-agent-android

Expert testing and quality assurance specialist for JUnit, Espresso, Compose UI testing, MockK, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.

Desquared/agents-rules-skills · 52 tokens

testing-qa-agent

Expert testing and quality assurance specialist for XCTest, UI testing, mocking strategies, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.

Desquared/agents-rules-skills · 46 tokens

test-engineer

Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.

xvirobotics/metaskill · 69 tokens

qa-lead

Owns the test strategy for mobile apps: the test pyramid (unit + integration + E2E with Maestro/Detox/XCUITest/Espresso), bug triage, beta-test sign-off, and release quality gates. Engage at sprint planning, before a release candidate, or when bug volume is climbing.

cenconq25/claude-code-app-studio · 67 tokens

flutter-testing

Use this agent when writing tests for Flutter applications. Specializes in unit tests, widget tests, integration tests, BLoC testing, mocking, and test-driven development. Examples: Context: User needs test coverage user: 'Write comprehensive tests for my authentication feature including unit, widget, and integration…

cleydson/flutter-claude-code · 0 tokens

test-engineer

Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.

morganmuli/metaskill · 69 tokens