qa-agent

Write, run, and evaluate FP-first tests for Rust, Scala, and TypeScript projects.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/asalhamed/dev-agents --skill qa-agent-asalhamed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-agent
Source: https://github.com/asalhamed/dev-agents/tree/main/qa-agent
Command: npx skills add https://github.com/asalhamed/dev-agents --skill qa-agent-asalhamed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing robust tests that reflect domain behavior across multiple stacks is hard. This Skill provides FP-first testing guidelines and practical patterns to write, run, and evaluate tests for backend and frontend code.

Core Features & Use Cases

  • Enforces FP testing: tests validate behavior, not implementation, with pure functions tested directly.
  • Supports Rust, Scala 3/2, and TypeScript across unit, integration, and property-based tests.
  • Provides a standard approach to test planning, infrastructure boundaries, and QA reporting.
  • Includes examples and templates to accelerate adoption within projects.

Quick Start

Create tests that express domain behavior for a new feature, then run unit and integration tests to verify invariants and generate a QA report.

Frequently Asked Questions about qa-agent

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

FAQPage Schema
How do I write FP-first tests that validate domain invariants in Scala and Rust?

FP-first testing validates pure function behavior directly without mocking internals, enforcing domain invariants across Scala and Rust codebases. Tests focus on behavior over implementation, mocking only at infrastructure boundaries.

What is the best way to structure integration tests for TypeScript and Scala backend boundaries?

Structure integration tests for TypeScript and Scala by testing pure functions directly and mocking only at infrastructure boundaries. This approach enforces domain behavior validation and outputs QA-ready test plans.

Can I use property-based testing to evaluate domain invariants across Rust and TypeScript projects?

Yes, property-based testing evaluates domain invariants across Rust and TypeScript projects. The approach supports unit, integration, and property-based tests, applying FP testing guidelines to validate pure function behavior.

Does this testing approach work with both Scala 3 and Scala 2 codebases?

Yes, this testing approach works with both Scala 3 and Scala 2 codebases. It provides FP-first testing guidelines, standard test planning, and QA reporting patterns that apply across supported languages.

When should I use mocks when writing tests for pure functions?

Use mocks only at infrastructure boundaries when testing pure functions. FP-first testing validates behavior directly without mocking internal modules, ensuring tests reflect true domain invariants and integration limits.

How do I generate QA-ready test plans and reports for multi-stack backend and frontend code?

Generate QA-ready test plans by expressing domain behavior for features, running unit and integration tests to verify invariants, and producing reports. This applies standard FP testing patterns across backend and frontend codebases.