skills.rest
medispis
medispisCOMMUNITY
Explore all skills by this author →
GitHub

testing

Generates test strategies, test plans, and test suites for existing codebases.

Updated Jun 2, 2026
Search Tags:#unit tests#testing#pytest#test generation#e2e tests#jest#test coverage
One-click install
npx skills add https://github.com/medispis/opencode-config --skill testing-medispis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/medispis/opencode-config/tree/main/skills/testing
Command: npx skills add https://github.com/medispis/opencode-config --skill testing-medispis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing comprehensive tests is time-consuming and often skipped, leaving codebases with poor coverage and undetected bugs. This Skill automates test strategy design and test suite generation so teams can reach meaningful coverage without starting from scratch. ## Core Features & Use Cases - Framework Detection: Automatically identifies the project's test framework (Jest, Vitest, pytest, Go test) and follows existing conventions. - Layered Test Strategy: Designs unit, integration, and e2e tests with coverage targets based on code criticality. - Test Generation & Verification: Writes test files following project naming conventions, then runs them and reports pass/fail results. - Use Case: You just built a new API endpoint with no tests. Ask for a test suite and get unit tests with mocked dependencies, integration tests against the endpoint, and a coverage report. ## Quick Start Generate a test suite with unit and integration tests for the authentication module and run them to verify they pass.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I generate a test suite for an existing codebase?▼

Detect the project's test framework from existing tests and config files, then analyze the code for testable units and edge cases. Generate test files following the project's naming conventions and run them to verify they pass.

How to write unit tests with mocking in Jest or pytest?▼

Mock external services like APIs, databases, and file systems while keeping the code under test real. Follow the Arrange-Act-Assert pattern: set up test data and mocks, call the function, then verify the expected outcome.

What test coverage should I target for different code types?▼

Target 95%+ for critical business logic, 90%+ for API endpoints, 80%+ for utility functions, and 70%+ for UI components. Configuration files should be verified rather than tested.

Does this work with any test framework?▼

Yes, it detects the framework from existing tests and configuration rather than assuming one. Supported examples include Jest, Vitest, pytest, and Go test, and it follows whatever conventions the project already uses.

Should I rewrite existing tests or extend them?▼

Extend existing tests rather than rewriting them. Place new test files where the project expects them, use descriptive test names explaining expected behavior, and keep one concept per test function.

Related Skills

Explore More Software Engineering Skills→
organvm-i-theoriaorganvm-i-theoria

tdd-workflow

Implements red-green-refactor test-driven development with unit, integration, and E2E coverage requirements.

Official
Intermediate
testdriveraitestdriverai
238

testdriver:ci-cd

Orchestrate TestDriver tests in CI/CD pipelines with parallel execution across platforms.

Official
Intermediate
BasedHardwareBasedHardware
13.1k

agent-review

Reviews agent-generated code for bugs and quality issues before merging.

Official
Basic
rubrical-worksrubrical-works

property-based-testing

Guides developers through property-based testing with property patterns, generators, and shrinking.

Official
Intermediate