create-unit-test

Create and run unit tests following the project's architecture and guidelines (Robolectric, naming, location).

⭐15stars🔀1forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

This Claude skill automates the creation and execution of unit tests for Android and Kotlin projects, ensuring strict adherence to project-specific architectural guidelines. By leveraging Robolectric for Android component testing and emphasizing the 'Arrange-Act-Assert' pattern, it helps developers maintain high code quality, consistency, and reliability through structured automated testing workflows.

Use Cases

  • Automated Test Generation: Quickly generate boilerplate-free unit tests for new Kotlin classes, following standard naming and directory conventions.
  • Android Component Testing: Utilize Robolectric to test Android-specific components like Activities and Fragments in a local JVM environment without needing a physical device.
  • Edge Case Identification: Analyze source code to identify potential error states and edge cases, creating robust test suites that prevent regressions and improve software stability.
  • Test Debugging and Maintenance: Diagnose failing tests by analyzing Gradle XML reports and fixing implementation or test logic to ensure a green build before commits.
namecreate-unit-test
descriptionCreate and run unit tests following the project's architecture and guidelines (Robolectric, naming, location).

Create Unit Test

This skill guides the creation of unit tests to ensuring consistency and correctness.

Workflow

  1. Analyze and Plan:

    • Goal: Understand what needs testing.
    • Action: Examine the source code.
    • Action: Identify "happy path" cases (core functionality).
    • Action: Identify "error cases" and "edge cases" based on likelihood.
    • Action: Do not suggest implementation details unless asked; focus on behavior.
  2. Setup Test File:

    • Naming: [OriginalClassName]Test.kt.
    • Location: [module]/src/test/java/[package/path]/.
    • Runner: If testing Android components, you MUST use Robolectric.
    • Mocking: Prefer creating Fakes over Mocks or patches. Use Mocks only if Fakes are too complex.
  3. Implement Tests:

    • Write clear, descriptive test methods.
    • Follow the "Arrange-Act-Assert" pattern.
    • Ensure all resources (strings, themes) are properly mocked or provided via Robolectric.
  4. Run Tests:

    • Command: ./gradlew :[module]:testDebugUnitTest
    • Example: ./gradlew :database:testDebugUnitTest
    • Tip: Before any commit, run ./gradlew testDebugUnitTest to ensure everything passes.
  5. Handle Failures:

    • Goal: Diagnose and fix issues.
    • Action: If a test fails, locate the full error report.
    • Path: [module]/build/test-results/testDebugUnitTest/TEST-[package.name.TestClassName].xml.
    • Example: app/build/test-results/testDebugUnitTest/TEST-com.anysoftkeyboard.janus.app.MainActivityTest.xml.

Guidelines

  • Consistency: Always place tests in the test source set, not androidTest (unless specifically writing instrumentation tests, which is rare for this skill).
  • Reliability: Avoid flaky tests. Ensure deterministic behavior.