Unit Testing

Building commissioning workflows including MBCx procedures, testing protocols, report generation, and energy conservation measure verification following ASHRAE Guideline 0 and NEBB standards

Allra 백엔드 테스트 작성 표준. Use when writing test code, choosing test helpers, generating test data with Fixture Monkey, or verifying test coverage.

Create well-structured user stories from requirements with clear acceptance criteria, technical context, and test scenarios. Use when creating user stories, refining backlog items, or breaking down epics.

Create detailed implementation plans from feature specs or bug reports with testable acceptance criteria. Use proactively when planning features, refactors, or fixes. Every task MUST have minimum 2 testable ACs and map to requirements.

Automate security testing, create reusable test suites, integrate with CI/CD, and measure security improvements over time.

Analyze recent changes and add test coverage for HEAD commit

Default testing standard for all implementation work - ensures code actually works through mandatory execution validation before confirming to user. Applies automatically whenever writing, modifying, debugging, or implementing any code (scripts, APIs, UI, configs, data operations, logic changes). This is the baseline expectation, not an optional extra - every implementation must be verified through actual execution, not assumed correct.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Comprehensive Playwright automation testing skill with E2E testing standards, test generation workflows, and browser automation best practices. Use when writing automated browser tests, testing user flows, or performing web application QA.

Generate comprehensive dbt test suites following FF Analytics data quality standards and dbt 1.10+ syntax. This skill should be used when creating tests for new dbt models, adding tests to existing models, standardizing test coverage, or implementing data quality gates. Covers grain uniqueness, FK relationships, enum validation, and freshness tests.

Create a new business use case (Request + UseCase + Test) following TDD workflow. Use when user asks to implement new business logic, domain operations, or create commands/queries. Always follow Red-Green-Refactor cycle.

Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.

Implement tasks from plans with test-first approach, user-story-centric execution, and AC verification. Use proactively when executing implementation plans. Enforces quality gates, MVP-first delivery, and Article VII story-by-story implementation.

Implementation Agent: Full TDD workflow in a single context window. Writes tests, implements code, and iterates until all tests pass.

Scaffolds new frontend pages/features with TDD approach, following established UI patterns from BuildProject/Baker pages. Generates page component, test file, updates routing, and maintains 90%+ test coverage before implementing production code. Use this when creating new pages or features in the Bucket app.

Automates TEST_CATALOG updates after test execution. Records test metrics, pass/fail status, coverage data, and execution time. Maintains single source of truth for all test files and their health status.

Debug SystemVerilog testbench failures in the SVC project. Use when a testbench fails (make <module>_tb), to analyze CHECK_* assertion failures, watchdog timeouts, or unexpected signal values. Provides systematic debugging workflow using VCD waveforms and failure output analysis.

This skill should be used when the user asks to "add unit tests", "write tests", "set up Vitest", "create a utility function", "add test coverage", or mentions TDD, test-driven development, or testing utilities. Provides guidance for unit testing with Vitest in TypeScript/Next.js projects using TDD approach.

Validate requirements quality - unique keys, acceptance criteria, testability, clarity. Sensor detecting requirement quality issues. Use before moving to Design stage or as quality gate.

WHEN: Go project review, error handling, goroutines, interfaces, testingWHAT: Error handling patterns + Concurrency safety + Interface design + Testing + Idiomatic GoWHEN NOT: Go API frameworks → go-api-reviewer, Rust → rust-reviewer