skills.rest
0X6C7879
0X6C7879COMMUNITY
Explore all skills by this author →
GitHub

test-engineering

Automate TDD workflows with red-green-refactor and minimum four test cases per feature.

Updated Aug 23, 2026
Search Tags:#testing#tdd#mocking#quality-assurance#test-automation#regression-testing#test-engineering
One-click install
npx skills add https://github.com/0X6C7879/aegissec --skill test-engineering-0x6c7879
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-engineering
Source: https://github.com/0X6C7879/aegissec/tree/main/skills/test-engineering
Command: npx skills add https://github.com/0X6C7879/aegissec --skill test-engineering-0x6c7879

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The testing discipline for software projects is often weak, leading to flaky releases and hidden defects. This Skill codifies a rigorous approach to test engineering, ensuring tests are intentional, repeatable, and maintainable.

Core Features & Use Cases

  • Enforces TDD red-green-refactor workflow to validate bugs and features.
  • Requires minimum 4 test scenarios per feature: normal, boundary, error, and permissions.
  • Supports mocking external dependencies and using factories for test data to keep tests reliable.
  • Provides naming conventions and documentation that doubles as executable guidance for teams.

Quick Start

Write a failing test first to reproduce a bug, then implement the fix and run the test to confirm.

Frequently Asked Questions about test-engineering

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

FAQPage Schema
How do I enforce the TDD red-green-refactor loop in my software project?▼

To enforce TDD red-green-refactor, you write a failing test to reproduce a bug, implement the fix, then run the test to confirm. This validates features while ensuring tests remain intentional and repeatable.

What test scenarios should I include for full feature coverage?▼

Full feature coverage requires a minimum of four test scenarios per feature: normal, boundary, error, and permissions. This disciplined approach ensures your test engineering handles edge cases and access control reliably.

How do I keep regression tests reliable when external dependencies are involved?▼

To keep regression tests reliable with external dependencies, use mocking and test data factories. This isolates the modules under test and provides consistent, repeatable test data across your test automation workflows.

Does this test engineering approach work for both new features and bug fixes?▼

Yes, this test engineering approach works for both new features and bug fixes by applying the TDD red-green-refactor workflow. It validates bugs and features equally by requiring failing tests before implementation.

What's the best way to standardize test naming conventions across software modules?▼

The best way to standardize test naming conventions is using consistent documentation that doubles as executable guidance for teams. This ensures maintainability and clarity across all modules and features in your project.

Related Skills

Explore More Software Engineering Skills→
qdzshqdzsh
12

tdd

Automates red-green-refactor cycles for vertical slices with failing tests first.

Community
Advanced
MontimageMontimage
9

test-coverage

Analyze coverage reports and generate targeted tests for untested branches.

Official
Advanced
s4kr4s4kr4
1

tdd

Guide Red-Green-Refactor TDD workflows with test naming and AAA patterns.

Community
Basic
iCesofTiCesofT
1

bdd-patterns

Apply Behavior-Driven Development patterns with Given-When-Then scenarios and feature files.

Community
Intermediate