Implement a feature or fix a bug using strict TDD. Analyzes the requirement, creates tests first, implements minimal code, then refactors. Use for feature requests, bug fixes, or enhancements that need test coverage.
Automate browser interactions, test web pages and work with Playwright tests.
Comprehensive E2E test development guidance for Eclipse Che / Red Hat OpenShift Dev Spaces. Use this skill when writing, modifying, or reviewing TypeScript Mocha Selenium tests, page objects, utilities, or test infrastructure. Provides code style rules, patterns, dependency injection setup, and best practices.
Reproduce CI test failures on a GCP VM matching the CI environment. Use when a CI job fails and the issue cannot be reproduced locally (e.g., kernel-dependent BPF verifier failures, kernel version-specific bugs).
Use when running tests in the Nango monorepo - knows unit vs integration configs, vitest commands, Docker setup, and common test patterns
Recover from CS2012 DLL lock failures when running Quartz unit tests
Build dependencies and run acceptance tests locally in the Optimism monorepo. Handles contracts, cannon prestates, Rust binaries, and optional kona prestate.
Write unit tests, integration tests, and architecture tests for FSH features. Use when adding tests or understanding the testing strategy.
This skill should be used when the user wants to add, modify, or debug a limits test. Trigger when the user mentions "limits test", "Generator subclass", "many objects", "scaling test", or wants to stress-test Materialize with large numbers of objects (tables, views, sources, indexes, etc.). Also trigger when the user edits test/limits/mzcompose.py.
This skill should be used when the user wants to create, modify, or debug a platform check. Trigger when the user mentions "platform check", "platform-checks", "upgrade check", "restart check", or wants to write a Check class that tests feature survival across restarts/upgrades. Also trigger when the user edits files in misc/python/materialize/checks/all_checks/.
General guide for running tests and choosing the right test framework in Materialize. Trigger when the user wants to "run tests", "run testdrive", "run sqllogictest", "run mzcompose", "run cargo test", "run pgtest", "rewrite test results", "add a test", "reproduce a bug", "write a regression test", or mentions testing, testdrive, sqllogictest, mzcompose, pgtest, cargo test, nextest, flaky tests, or test failures. Use this skill even if the user just says "test this" or "how do I verify this works" without naming a specific framework. For deep guidance on specific frameworks, see the dedicated skills: mz-platform-checks (upgrade/restart survival), mz-parallel-workload (concurrent stress testing), and mz-limits-test (scaling to many objects).
Workflow 1.5: Bridge between idea discovery and auto review. Reads EXPERIMENT_PLAN.md, implements experiment code, deploys to GPU, collects initial results. Use when user says "实现实验", "implement experiments", "bridge", "从计划到跑实验", "deploy the plan", or has an experiment plan ready to execute.
Deploy and run ML experiments on local, remote, Vast.ai, or Modal serverless GPU. Use when user says "run experiment", "deploy to server", "跑实验", or needs to launch training jobs.
Workflow 1.5: Bridge between idea discovery and auto review. Reads EXPERIMENT_PLAN.md, implements experiment code, deploys to GPU, collects initial results. Use when user says "实现实验", "implement experiments", "bridge", "从计划到跑实验", "deploy the plan", or has an experiment plan ready to execute.
Deploy and run ML experiments on local or remote GPU servers. Use when user says "run experiment", "deploy to server", "跑实验", or needs to launch training jobs.
Run end-to-end Python tests after making changes to verify correctness. Use this when you want to verify your changes from an end-to-end perspective, after ensuring the build and Rust tests pass.
Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.
