test-engineer

Design and implement deterministic automated tests for .NET/C# and Rust codebases.

2|1|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill test-engineer-thiagoguislotti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-engineer
Source: https://github.com/ThiagoGuislotti/copilot-instructions/tree/main/.codex/skills/test-engineer
Command: npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill test-engineer-thiagoguislotti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Test Engineer skill helps teams design, implement, and stabilize automated tests across .NET/C#, Rust, APIs, and frontend flows to increase coverage, catch regressions early, and reduce flaky failures.

Core Features & Use Cases

  • Test design & implementation: Recommend test layers and write deterministic unit, integration, and E2E tests following AAA and isolation patterns.
  • Stabilization & debugging: Identify flaky tests, map high-risk scenarios, and propose fixes to make tests reliable and repeatable.
  • Integrations & validation: Provide guidance to run dotnet test and cargo test, coordinate dependency vulnerability audits, and apply quality gates for releases.
  • Use Case: When an API change breaks behavior, create the smallest test that proves the correct behavior, extend integration tests as needed, and run vulnerability and quality checks before merging.

Quick Start

Use the test-engineer skill to add deterministic unit and integration tests for a changed backend API and stabilize any flaky E2E flows.

Frequently Asked Questions about test-engineer

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

FAQPage Schema
How do I write deterministic unit and integration tests for Rust and .NET?

Deterministic unit and integration tests follow AAA patterns and isolation principles, integrating with cargo test and dotnet test to increase coverage and reduce regressions across .NET/C# and Rust stacks.

Why are my E2E tests flaky and how do I stabilize them?

Flaky E2E tests are stabilized by identifying high-risk scenarios and mapping dependencies to propose fixes that make tests reliable, repeatable, and isolated from frontend state variations.

What is the best way to add test coverage after an API change breaks behavior?

The best way to add test coverage after an API change is creating the smallest test that proves correct behavior, extending integration tests as needed, and running vulnerability and quality checks before merging.

Can I run vulnerability audits and quality gate checks before merging test changes?

Yes, vulnerability audits and quality gate checks can be coordinated alongside automated test runs to validate releases, ensuring dependency security and test stability are verified before merging code.

Does this testing approach support both frontend E2E flows and backend API stacks?

Yes, the testing approach supports frontend E2E flows and backend API stacks by designing automated tests across .NET/C#, Rust, APIs, and frontend layers to catch regressions early.

When do I need to isolate tests using AAA patterns for test engineering?

You need to isolate tests using AAA patterns when designing automated tests to ensure deterministic results, prevent flaky failures, and maintain reliable regression coverage across unit, integration, and E2E testing layers.