sub-test-engineer

Name: sub-test-engineer
Availability: InStock
Author: hungrytech

Automate type-aware test generation and validation across Java, Kotlin, TypeScript, and Go backends.

3|Updated Mar 30, 2026

Search Tags:#automation #typescript #testing #go #java #kotlin #type-driven

Ready to run

npx skills add https://github.com/hungrytech/hungrytech-claude-skills --skill sub-test-engineer

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, gradle, maven, docker, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the end-to-end workflow for generating, analyzing, and validating high-quality tests across Java, Kotlin, TypeScript, and Go backends, with a focus on type-driven test discovery and coverage goals.

Core Features & Use Cases

3-phase analysis workflow: Discover targets, derive type information, and plan test strategy.
Type-driven generation: Create tests guided by type information, enums, sealed classes, and validation annotations.
Gap-based refinement: Iterate on uncovered paths or surviving mutations to strengthen tests.
Cross-module support: Operates across multi-module projects and integrates with common build tools.

Quick Start

Write a request to generate tests for a target like OrderService with loop 2 to target coverage and mutation goals.

Frequently Asked Questions about sub-test-engineer

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

FAQPage Schema

How does type-driven test generation work for multi-language backends?▼

Type-driven test generation uses type information, enums, and sealed classes to automatically discover test targets and validate paths across Java, Kotlin, TypeScript, and Go backends. It analyzes the codebase structure to plan a targeted test strategy.

Can I automate test generation and mutation testing across multi-module projects?▼

Yes, you can automate test generation and mutation testing across multi-module projects. The workflow integrates with common build tools like Gradle and Maven, running in CI pipelines to iterate on surviving mutations and strengthen test coverage.

What's the best way to close test coverage gaps in a TypeScript or Go backend?▼

The best way to close coverage gaps is through gap-based refinement, which iterates on uncovered paths and surviving mutations. This approach targets specific weaknesses in your tests, refining them until configurable coverage goals are met.

Do I need ast-grep to run type-aware test generation?▼

Yes, ast-grep is required to run type-aware test generation and derive type information for test planning. Optional ClassGraph enrichment can be added to further enhance type discovery capabilities across your backend modules.

Does this test automation workflow support Docker and CI pipelines?▼

Yes, this test automation workflow supports Docker and integrates directly into CI pipelines. It operates across multi-module projects using dependencies like jq, Gradle, and Maven to execute automated test generation and validation.

Why are my automated tests missing edge cases for sealed classes and validation annotations?▼

Automated tests often miss edge cases when type information is not fully utilized. By using type-driven generation guided by sealed classes and validation annotations, the workflow ensures these specific edge cases are discovered and covered during the strategy phase.