test-engineer

Name: test-engineer
Availability: InStock
Author: denissvgn

Design and execute unit, integration, and E2E automated tests in CI/CD workflows.

Updated Jan 14, 2026

Search Tags:#unit tests #automation #integration tests #E2E tests #QA #test #test plan

Ready to run

npx skills add https://github.com/Denissvgn/project-team-ag --skill test-engineer-denissvgn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-engineer
Source: https://github.com/Denissvgn/project-team-ag/tree/main/.agent/skills/test-engineer
Command: npx skills add https://github.com/Denissvgn/project-team-ag --skill test-engineer-denissvgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Test Engineer skill enables teams to ensure software quality by designing and running automated tests across codebases, catching defects early and reducing regression risk.

Core Features & Use Cases

Test Planning: Define testing strategy, scope, and acceptance criteria.
Unit, Integration & E2E Tests: Create and execute tests at multiple levels to validate components and flows.
Artifacts & Reporting: Generate Test Plan, test code standards, and execution reports for handoff.
Handoff & Collaboration: Deliver results to CR/QA/Development teams to drive fixes and releases.

Quick Start

Use the Test Engineer to draft an automated test plan for a new feature and scaffold 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 automate QA testing for a new software feature?▼

To automate QA testing for a new feature, you can define a testing strategy, scope, and acceptance criteria, then scaffold initial automated tests to validate components and user flows. This ensures software quality and reduces regression risk.

What is the best way to plan unit, integration, and E2E tests in a CI/CD workflow?▼

The best way to plan tests in a CI/CD workflow is to enforce a structured test plan that defines strategy and acceptance criteria. You can then create and execute unit, integration, and E2E tests across components and services.

Can I generate execution reports for handoff to development teams?▼

Yes, you can generate execution reports, test plans, and test code standards as artifacts. These artifacts facilitate handoff and collaboration with CR, QA, and development teams to drive necessary fixes and releases.

Does automated test planning support validation across both components and user flows?▼

Automated test planning supports validation across both components and user flows by creating and executing tests at multiple levels. This includes unit tests for components and integration and E2E tests for complete user flows.

Why do I need to define acceptance criteria before scaffolding automated tests?▼

Defining acceptance criteria before scaffolding automated tests is necessary to establish a clear testing strategy and scope. This ensures the automated tests accurately validate the intended software behavior and catch defects early.