test-engineer

Name: test-engineer
Availability: InStock
Author: nexar

Create and manage test plans, code, and execution across backend, frontend, and firmware.

Updated Aug 27, 2026

Search Tags:#automation #frontend #backend #firmware #test-generation #test-plans #test-engineering

Ready to run

npx skills add https://github.com/getnexar/decrypt-tool --skill test-engineer-getnexar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-engineer
Source: https://github.com/getnexar/decrypt-tool/tree/main/ai-tools/skills/test-engineer
Command: npx skills add https://github.com/getnexar/decrypt-tool --skill test-engineer-getnexar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a centralized workflow for defining, generating, and maintaining comprehensive test plans and test code across backend APIs, frontend E2E, and firmware HIL, reducing manual coordination and drift.

Core Features & Use Cases

Create structured test plans that cover happy paths, edge cases, and error conditions.
Generate test code and artifacts for backend, frontend, and firmware domains from templates.
Run test suites and remove obsolete tests to keep the test suite lean and up-to-date.

Quick Start

Create a test plan and corresponding automated tests for a new feature across backend, frontend, and firmware.

Frequently Asked Questions about test-engineer

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

FAQPage Schema

How do I automate test plan creation across backend, frontend, and firmware domains?▼

Generate automated test code by applying domain-specific templates that align with documentation and produce versioned artifacts. This supports backend APIs, frontend E2E, and firmware HIL test code generation from a centralized workflow.

How do I remove obsolete tests and keep automated test suites lean?▼

Remove obsolete tests using the dedicated removal operation to keep your test suite lean and up-to-date. This ensures your backend, frontend, and firmware test suites remain maintained without accumulating deprecated test code.

Can I coordinate end-to-end testing for both software APIs and firmware HIL together?▼

Coordinate end-to-end testing across backend APIs, frontend E2E, and firmware HIL using a centralized workflow. This applies to software teams that require structured test planning, automated generation, execution, and reporting across multiple domains.

What is the best way to manage test execution and reporting for multi-domain software teams?▼

Manage test execution and reporting by running test suites across backend, frontend, and firmware domains. The workflow enforces documentation alignment and generates versioned artifacts, ensuring structured test management for multi-domain software teams.

Does automated test generation work without setting up specific dependencies?▼

Automated test generation works without external dependencies, utilizing domain-aware templates and documentation alignment instead. It supports four operations—Create Test Plan, Create Tests, Run Tests, and Remove Tests—natively within the workflow.