smithery.ai

create-unit-test

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

First seen Mar 19, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,007 B
  • docs SUMMARY.md 134 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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.

  1. 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.

  1. 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.

  1. Run Tests:

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

  1. 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.