backend-tester

backend-tester is a skill for Claude Code from olehsvyrydov/AI-development-team. It costs 49 tokens per session (2,187 once invoked), scanned A, original, MIT.

A Java testing guide for checking Java and Spring applications with unit, integration, and API tests. It covers JUnit, Mockito, Testcontainers, and reactive-code testing, where programs handle results that arrive over time.

In plain words
What is it for?
Use it to write unit tests, integration tests that run with real supporting services in containers, API tests, test fixtures, mocks, and tests for reactive code.
Why use it?
It gives developers a repeatable way to catch backend defects and check behavior before implementation is considered complete. TDD, or test-driven development, means writing the test before the code it checks.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ai-dev-team plugin — 43 skills, 50 commands shipped together

Good fit Use it to write unit tests, integration tests that run with real supporting services in containers, API tests, test fixtures, mocks, and tests for reactive code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/olehsvyrydov/ai-development-team/backend-tester
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add olehsvyrydov/AI-development-team --skill backend-tester
Clone the repo
git clone --depth 1 https://github.com/olehsvyrydov/AI-development-team

Made for: Claude Code.

Or install ai-dev-team, the plugin that ships this one along with the rest of its 43 skills, 50 commands.

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 backend-tester

README.md
[![agentmods](https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/backend-tester/github.svg)](https://agentmods.dev/skills/olehsvyrydov/ai-development-team/backend-tester)
Your own site
<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/backend-tester"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/backend-tester/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 backend-tester

Your own site · 80×15
<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/backend-tester"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/backend-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,187 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.00049 $0.02187
Opus 5.5 $0.00020 $0.00875
Sonnet 5.5 $0.00010 $0.00437
Haiku 4.5 $0.00005 $0.00219

Measured today against content hash 5403010826c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

backend-tester 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 today.

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/skills/quality/testing/backend-tester/SKILL.md · 327 lines

How it starts

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

Backend Tester

Trigger

Use this skill when:

  • Writing unit tests for Java/Spring code
  • Creating integration tests with Testcontainers
  • Implementing API tests
  • Setting up test fixtures and mocks
  • Achieving test coverage targets
  • Following TDD methodology
  • Testing reactive code with StepVerifier

Context

You are a Senior QA Engineer with 10+ years of experience in Java testing. You are a TDD evangelist who writes tests before implementation code. You have extensive experience with JUnit 6, Mockito, Testcontainers, and testing reactive applications. You believe that tests are first-class citizens and documentation that never lies.

Documentation Lookup (MANDATORY)

Before writing backend tests, always check for the latest documentation:

Context7 MCP

Use Context7 MCP to retrieve up-to-date documentation for any library or framework:

  1. Resolve library: Call mcp__context7__resolve-library-id with the library name
  2. Query docs: Call mcp__context7__query-docs with the resolved library ID and your question

When to use: JUnit 5 assertions, Testcontainers setup, Mockito patterns, StepVerifier usage

Example queries:

  • "JUnit 5 parameterized tests and extensions"
  • "Testcontainers PostgreSQL and Kafka modules"
  • "Mockito 5 argument matchers and verification"
  • "StepVerifier reactive stream testing"

Web Research

Use WebSearch and WebFetch for current best practices, version updates, CVEs, and community guidance.

Rule: When uncertain about any API or pattern — search first, test second.

Expertise

Testing Frameworks

JUnit 6 (Jupiter)
  • Test lifecycle (@BeforeAll, @BeforeEach, @AfterEach, @AfterAll)
  • Nested test classes
  • Parameterized tests
  • Dynamic tests
Mockito 5.x
  • Mock creation (@Mock, @Spy)
  • Stubbing (when/thenReturn, given/willReturn)
  • Verification
  • Argument captors
  • BDD style
Testcontainers
  • PostgreSQL container
  • Redis container
  • Kafka container
  • Container reuse
StepVerifier (Reactive Testing)
  • expectNext / expectNextCount
  • expectError / expectErrorMatches
  • verifyComplete / verifyError
  • withVirtualTime

Read the full file on GitHub · 327 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. today First seen · 327 lines · 49 tokens per session scan A 5403010826c3

Subscribe to this mod's changes

backend-tester is a skill published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 2,187 once invoked, about $0.0002 per session on Opus 5.5. 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-10-19.

Related

Other skills, from other repositories

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

affaan-m/ECC · 31 tokens

cpp-testing

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

affaan-m/ECC · 34 tokens

principle-test-behavior-not-implementation

Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.

michael-denyer/pstack-claude · 50 tokens

unit-test-philosophy

Risk-based unit testing and Allure-readable behavioral spec style for open-agreements. Use when user says "add tests," "test quality," "coverage expansion," "unit test style," or "Allure test spec." Applies when adding/updating tests, expanding coverage, or reviewing test quality across src, integration-tests, and…

open-agreements/open-agreements · 74 tokens

python-testing

Expert in Python testing with pytest and test-driven development.

Mindrally/skills · 13 tokens

testing-expert

Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices. Use when the user mentions TDD, BDD, unit tests, integration tests, or end-to-end tests, or when the task involves Testing Fundamentals, Unit Testing, Integration Testing, or End-to-End Testing.

personamanagmentlayer/pcl · 73 tokens