Total 30,734 skills, Testing & QA has 1242 skills
Showing 12 of 1242 skills
Testing framework for evaluating Databricks skills. Use when building test cases for skills, running skill evaluations, comparing skill versions, or creating ground truth datasets with the Generate-Review-Promote (GRP) pipeline. Triggers include "test skill", "evaluate skill", "skill regression", "ground truth", "GRP pipeline", "skill quality", and "skill metrics".
TypeScript/JavaScript Test-Driven Development with Vitest, strict red-green-refactor methodology, React component testing, and comprehensive coverage patterns. Use when implementing TypeScript features with TDD, writing Vitest tests, testing React components, developing with test-first approach, or when user mentions 'TypeScript TDD', 'Vitest', 'React testing', 'JavaScript TDD', 'red-green-refactor', 'TypeScript unit tests', or 'test-driven TypeScript'.
Iteratively fix test failures until all tests pass. Use when tests are failing and you want Claude to automatically plan and fix them in a loop.
Creates Robot Framework test cases for SnapLogic account creation. Use when the user wants to create accounts (Oracle, PostgreSQL, Snowflake, Kafka, S3, etc.), needs to know what environment variables to configure, or wants to see account test case examples.
Check and configure Sentry error tracking for project standards
Check and configure testing frameworks and infrastructure
Writing effective step definitions and organizing test code
Generates before/after verification pairs for loom plans. Proves a stage actually changed system behavior by capturing state before and after implementation. Use for delta-proof verification — proving new commands, endpoints, modules, or bug fixes work by comparing system state.
TDD/BDD testing principles, test patterns, and coverage strategies
Use when initializing Sentry in applications, configuring SDK options, or setting up integrations across different frameworks and platforms.
Testing procedures. Invoke with /tzurot-testing for test execution, coverage audits, and debugging test failures.
Replace the usage of `expect` and similar functions from `package:matcher` to `package:checks` equivalents.