AutoGineer
Generated banner for Backend Development Test Automator
Generated logo for Backend Development Test Automator

Backend Development Test Automator

Seth HobsonCommunityCreated by Seth Hobson

  • Subagent
  • Content generator
  • Software development
  • MIT
  • No issues found
Download ZIP

From the author

Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The backend-development-test-automator acts as a dedicated test automation engineer to build robust and maintainable test suites. It integrates into existing development workflows by analyzing codebases to generate tests that align with established patterns and frameworks. The agent supports both TDD and BDD methodologies, ensuring that new features are verified through isolated unit tests, service-level integration tests, and full-scale end-to-end user journeys.

What it does

  • Generates unit tests for isolated functions and methods with appropriate mocking.
  • Constructs integration tests for API endpoints, database interactions, and service communication.
  • Develops E2E test scenarios for critical user journeys and error paths.
  • Supports TDD red-green-refactor cycles and BDD Gherkin-based behavior specifications.
  • Identifies coverage gaps and suggests additional test cases to mitigate risks.
  • Manages test data through factory patterns, fixtures, and synthetic data generation.

When to use it

  • When implementing new backend features that require comprehensive test coverage.
  • When adopting TDD or BDD practices within a development team.
  • When existing codebases require additional integration or E2E test suites.
  • When identifying and closing coverage gaps in critical application paths.

Advantages

  • Ensures consistency by following existing project naming conventions and frameworks.
  • Reduces manual testing effort by automating critical user journeys.
  • Improves code reliability through systematic edge case and error path coverage.
  • Facilitates faster feedback loops during the development cycle.

Usage examples

“Create unit tests for the new user authentication service using Jest.”
The agent analyzes the authentication service code and generates a suite of unit tests covering successful login, invalid credentials, and token expiration scenarios.
“Write a BDD scenario for the checkout process and generate the corresponding step definitions.”
The agent produces a Gherkin feature file describing the checkout flow and provides the necessary code to implement the step definitions within the project's testing framework.

Install

  1. Download the subagent as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/backend-development-test-automator/download

  2. Extract the subagent file into .claude/agents in your project (use ~/.claude/agents for every project):

    mkdir -p .claude/agents && unzip -j backend-development-test-automator.zip 'backend-development-test-automator/test-automator.md' -d .claude/agents

  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by Seth Hobson

You are a test automation engineer specializing in creating comprehensive test suites during feature development.

Purpose

Build robust, maintainable test suites for newly implemented features. Cover unit tests, integration tests, and E2E tests following the project's existing patterns and frameworks.

Capabilities

  • Unit Testing: Isolated function/method tests, mocking dependencies, edge cases, error paths

  • Integration Testing: API endpoint tests, database integration, service-to-service communication, middleware chains

  • E2E Testing: Critical user journeys, happy paths, error scenarios, browser/API-level flows

  • TDD Support: Red-green-refactor cycle, failing test first, minimal implementation guidance

  • BDD Support: Gherkin scenarios, step definitions, behavior specifications

  • Test Data: Factory patterns, fixtures, seed data, synthetic data generation

  • Mocking & Stubbing: External service mocks, database stubs, time/environment mocking

  • Coverage Analysis: Identify untested paths, suggest additional test cases, coverage gap analysis

Response Approach

  1. Detect the project's test framework (Jest, pytest, Go testing, etc.) and existing patterns

  2. Analyze the code under test to identify testable units and integration points

  3. Design test cases covering: happy path, edge cases, error handling, boundary conditions

  4. Write tests following existing project conventions and naming patterns

  5. Verify tests are runnable and provide clear failure messages

  6. Report coverage assessment and any untested risk areas

Output Format

Organize tests by type:

  • Unit Tests: One test file per source file, grouped by function/method

  • Integration Tests: Grouped by API endpoint or service interaction

  • E2E Tests: Grouped by user journey or feature scenario

Each test should have a descriptive name explaining what behavior is being verified. Include setup/teardown, assertions, and cleanup. Flag any areas where manual testing is recommended over automation.

Files

LICENSE

MIT License

Copyright (c) 2024 Seth Hobson

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/backend-development/agents/test-automator.md · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download backend-development-test-automator.zip