“testing”

Use when adding, updating, or reviewing tests in agent-eval, choosing test coverage, organizing Vitest tests, or isolating filesystem, Docker, and other…

Implements Test-Driven Development for this project—unit tests, integration tests with testcontainers, mocks, and regression tests.

Use when writing tests or deciding on a testing strategy.

Guide for offline-first game extraction testing, writing domain tests, and validating calculations

Use when writing or fixing Jest tests, mocks, or test layout under test/ in contentstack-js-core.

Use for creating, updating, or reviewing automated tests and test-plan adequacy.

Rules for writing tests - which level to test at, when a mock is allowed, isolation, waiting, structure and fixtures.

Use when writing, changing or reviewing a test, or deciding what to test.

Use for Jest, Playwright e2e, API tests, and bundler smoke tests in contentstack-typescript.

Stack-specific test patterns — pytest (asyncio_mode=auto), Jest/Vitest, Go — fixtures, mocking, coverage.

Use for flaky or nondeterministic tests, especially local-vs-CI inconsistencies.

Use for JUnit tests, integration (*IT) tests, fixtures, and credentials handling in contentstack-java.

Use for Jest e2e and TypeScript test suites, jest configs, and test layout in contentstack-javascript.

Use for Mocha/NYC unit tests, API tests, and Jest TypeScript tests in contentstack-marketplace-sdk.

Write and run tests, and report real test-run output as evidence for the Verification Policy rule.

used when designing, writing, and validating tests or test failures.

Use for JVM unit tests, Robolectric, AndroidX Test, and JaCoCo in contentstack-android.

Write, extend, or evaluate automated tests — unit, integration, or end-to-end — in a way that matches the project's existing framework and conventions.

Use when writing or reviewing Foundry tests, deciding whether a suite is enough to deploy, or when a green run or a coverage number is offered as proof that a…

Testing and verification rules for FlowBit V2 customer apps.

Skill validation framework PLUS daily test-suite health and regression intelligence.

Run tests and checks in the sandbox, read the failures and report what passes and what does not.

Testing doctrine, pyramid (unit, integration, API, security, smoke), AAA pattern, and coverage enforcement.

Test abstractions, not hardware — discovery, capabilities, NAT/firewall generation, cleanup, rollback, uplink switching.