test-writer

Generate automated tests for unit, integration, end-to-end, contract, and snapshot testing.

2|1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill test-writer-code-saurabh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-writer
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/test-writer
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill test-writer-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false confidence from weak, brittle, incomplete, or flaky tests by guiding the creation of executable specifications that detect regressions across application behavior and failure paths.

Core Features & Use Cases

  • Comprehensive Test Design: Generate unit, integration, end-to-end, contract, and snapshot tests based on the system's boundaries and risks.
  • Edge-Case Coverage: Address validation failures, dependency errors, timeouts, boundary conditions, concurrency, and unexpected data.
  • Production-Ready Practices: Apply Arrange/Act/Assert structure, behavior-focused assertions, reliable mocks, test factories, coverage thresholds, and CI requirements.
  • Use Case: When adding a user service method, use this Skill to define diagnostic tests for successful lookups, missing users, invalid input, repository failures, and integration behavior.

Quick Start

Ask the test-writer skill to inspect the target module and generate a complete test suite covering its behavior, edge cases, dependencies, and definition of done.

Frequently Asked Questions about test-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate automated tests that catch behavioral regressions?

You can generate behavior-focused assertions with independent, deterministic tests and controlled dependencies to detect regressions across application logic and failure paths before release.

What is the best way to cover edge cases and failure paths in integration testing?

Cover edge cases in integration testing by addressing validation failures, dependency errors, timeouts, boundary conditions, concurrency, and unexpected data to prevent false confidence in software quality.

How do I structure unit tests to avoid flaky behavior and false confidence?

Structure unit tests using Arrange/Act/Assert patterns, behavior-focused assertions, reliable mocks, and test data factories to ensure independent, deterministic execution and prevent false confidence.

Does this approach support e2e testing and contract testing for external service boundaries?

Yes, this approach supports e2e testing and contract testing by generating executable specifications for user journeys, APIs, repositories, and external service boundaries to detect regressions.

When do I need mocking and test factories for regression testing?

Use mocking and test factories during regression testing to control dependencies, isolate business logic, and ensure deterministic tests that accurately validate behavior without external interference.

Why do my test suites miss regressions even with high test coverage?

High test coverage misses regressions when tests lack behavior-focused assertions, failure-path coverage, and boundary condition validation, creating false confidence instead of executable specifications.