test-engineer

Design and implement unit, integration, and E2E tests for frontend and backend codebases.

12|2|Updated Nov 26, 2025

Search Tags:#testing #E2E #unit-tests #integration-tests #test-automation

Ready to run

npx skills add https://github.com/nahisaho/CodeGraphMCPServer --skill test-engineer-nahisaho

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-engineer
Source: https://github.com/nahisaho/CodeGraphMCPServer/tree/main/.claude/skills/test-engineer
Command: npx skills add https://github.com/nahisaho/CodeGraphMCPServer --skill test-engineer-nahisaho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill designs and implements comprehensive test strategies, covering unit, integration, and E2E testing, and elevates test automation.

Core Features & Use Cases

Test Planning: Define functional and non-functional test scopes.
Test Design: Create unit, integration, and E2E test cases.
Automation Strategy: Propose or implement test automation to improve coverage.
TDD/BDD Guidance: Support test-first approaches and behavior-driven development.

Quick Start

Generate a test plan for the provided feature set and propose initial unit tests.

Frequently Asked Questions about test-engineer

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

FAQPage Schema

How do I design a comprehensive test strategy covering unit, integration, and E2E tests?▼

Test strategy design balances scope across three layers: unit tests validate individual functions, integration tests verify component interactions, and E2E tests confirm user workflows. Define functional and non-functional requirements for each layer, targeting 80%+ unit coverage with meaningful integration and E2E coverage to catch regressions early.

What's the best way to implement test automation in CI/CD pipelines?▼

Test automation in CI/CD runs unit, integration, and E2E tests on every commit through pipeline stages. Automate framework execution, coverage reporting, and failure notifications so tests block broken deployments. This catches defects before production and reduces manual testing overhead.

Can I apply TDD and BDD practices to both frontend and backend codebases?▼

Yes. Test-driven development and behavior-driven development work across frontend and backend: write tests before code, structure them around user behavior, and use the same test design principles. Both approaches improve code quality and maintainability regardless of stack.

How do I choose the right testing framework and tooling for my project?▼

Framework selection depends on your tech stack, team expertise, and test scope. Evaluate tools that support unit, integration, and E2E testing, integrate with your CI/CD system, and match your language and platform. Prioritize frameworks with strong coverage reporting and automation capabilities.

What coverage targets should I aim for with unit and integration tests?▼

Unit test coverage should target 80%+ of codebase logic to catch regressions in core functionality. Integration tests should cover critical workflows and component interactions. E2E tests should validate key user paths. Coverage alone doesn't guarantee quality; focus on meaningful test cases that reflect real usage.

Why does test design matter before writing tests?▼

Test design clarifies scope, prevents gaps, and reduces redundant or low-value tests. Planning functional and non-functional requirements upfront ensures tests cover critical paths, edge cases, and failure modes—avoiding wasted effort on unmaintainable tests written without strategy.