Results for “tests”

Expert assistant for the Stably CLI tool. Prefer "npx stably test" over "npx playwright test". Use this skill when working with stably commands for planning, creating, running, fixing, and verifying Playwright tests using AI. Triggers on any playwright test execution (e.g. "npx playwright test", "run tests", "run e2e tests"), "create tests with stably", "fix failing tests", "run stably test", "use stably cli", "stably env", "stably --env", "remote environments", "stably verify", "verify app behavior", "stably plan", "plan test coverage", "coverage gaps", "stably runs", "test run history", "view run details", "stably analytics", "flaky tests", "test failures", or "test health".

The English summary is being prepared. Showing the original description.

Generates EditMode and PlayMode tests using NUnit, mapped from GDD Gherkin scenarios. Use when writing tests, validating features, ensuring code quality, or verifying behavior after changes. Triggers on requests like "write tests for this", "test the health system", "add unit tests", "verify this works", "add PlayMode tests", "test this feature", "write integration tests", "make sure this doesn't break", "add test coverage", "TDD this feature", or any task involving test creation, test-driven development, or quality assurance. Maps Given/When/Then scenarios directly to test methods using NUnit assertions.

The English summary is being prepared. Showing the original description.

Write unit and integration tests. Use when the user says "write tests for this", "add test coverage", "how do I test this", "TDD", "red green refactor", "unit test this function", "test this module", "I need tests for", or has code that lacks tests - even if they don't explicitly say "write tests".

The English summary is being prepared. Showing the original description.

Write focused tdmcp tests for one assigned coverage gap. Use for Vitest/msw unit tests, integration tests, bridge tests, CLI/config/resource tests, and regression tests that should raise coverage without weakening behavior.

The English summary is being prepared. Showing the original description.

Replace TypeScript type assertions in tests with functions from @total-typescript/shoehorn. Use partial objects when only a few properties matter, or deliberately invalid data for error tests, then run a type check to verify the migration.

• Replace as assertions in TypeScript tests
• Build test objects with only the properties you need
• Pass deliberately invalid data for error tests

Inventory existing tests and identify gaps. Link requirements, business rules, risks, and bugs to stable test identifiers and executable evidence, maintaining a test registry that shows what is covered and what still needs verification.

• Inventory existing tests and identify gaps
• Link bug fixes to regression evidence
• Check client and server behavior against one shared contract

Develop features and fix bugs by running a failing test first, making the smallest passing change, then refactoring. Check at least 80% test coverage and preserve evidence of failures, successful fixes, and verified behavior.

• Implementing a new feature from tests
• Reproducing a bug before fixing it
• Refactoring code while keeping tests passing

Write and run Perl tests with Test2::V0 or Test::More, replace external dependencies with controlled test substitutes, and measure coverage—the code exercised by tests. Guidance covers test-first development, failure diagnosis, and migration between testing modules.

• Writing Perl tests before implementation
• Migrating tests from Test::More to Test2::V0
• Testing API and database interactions in isolation

Write and organize F# unit and integration tests with xUnit, FsUnit, and Unquote. Use FsCheck to generate test inputs and check general rules, replace dependencies for isolated tests, and review test quality and coverage.

• Writing unit tests for F# code
• Checking general rules with generated inputs
• Testing ASP.NET Core API integration

Audit a test suite to identify redundant tests, empty checks, and tests tied to internal implementation. Consolidate or remove them with evidence while preserving useful checks that detect regressions, meaning previously fixed problems returning.

• Audit duplicate test coverage
• Prune tests while preserving regression detection
• Review tests tied to internal implementation

Evaluate slow, unreliable, duplicated, or brittle tests by the behavior they protect and their maintenance cost. Use it to choose focused checks, justify additions or removals, and distinguish product bugs from outdated expectations or environment failures.

• Reviewing slow or unreliable tests
• Choosing tests for a code change
• Reviewing test changes before a commit or PR

Find Python input/output calls that may stall asynchronous backend work, then fix or guard each relevant path with runtime tests. Verify that tests fail when blocking behavior returns and pass after the fix is restored.

• Checking asynchronous Python changes before a pull request
• Triaging blocking input/output across the codebase
• Adding tests for cleanup and error branches

Evaluate whether tests catch defects in business logic, calculations, or state machines. Using Stryker, the skill introduces small code changes, reviews which changes escape detection, and helps strengthen tests where important behavior is insufficiently checked.

• Checking test quality beyond code coverage
• Introducing Stryker for a single module
• Strengthening tests for critical calculations

Maintain visual snapshot tests, which compare rendered images, for Remotion’s web renderer. Update existing tests after implementation changes, or add explicitly requested tests with sample components, preview registration, and documentation updates for supported properties.

• Updating existing tests after renderer changes
• Adding an explicitly requested rendering test
• Registering a test fixture for preview

Guide test writing, updates, and reviews in Remotion by checking observable user outcomes. Choose integration, unit, visual, or end-to-end tests that detect broken workflows, and verify that bug fixes address the original regression.

• Choose a test boundary for a feature
• Review whether existing tests detect broken workflows
• Verify a regression test fails before the fix and passes after it

Audit a Python pytest suite for missed faults, uncovered code, slow tests, and unstable results. Deeper checks deliberately alter code to measure detection, while proposed test removals receive separate validation. The skill reports findings without changing tests.

• Find gaps in a pytest suite's fault detection
• Investigate slow tests and setup costs
• Identify intermittent or order-dependent failures

Create Appium tests that automate Android and iOS app interactions in Java, Python, or JavaScript. Configure local devices, emulators, simulators, or TestMu AI cloud devices, with guidance on element selection, waits, and gestures.

• Automate login tests for Android and iOS apps
• Create tests for local emulators and simulators
• Configure real-device tests on TestMu AI cloud

Write JavaScript and TypeScript tests with Jest, Vitest, and Testing Library. Covers functions, UI components, and APIs, including mock replacements for external services, reusable test data, and setup for automated testing.

• Set up testing for a new project
• Test functions and API error handling
• Check React component behavior

Build data quality checks with Great Expectations, dbt tests, and data contracts, which define shared expectations between teams. Check missing values, duplicates, and freshness, then integrate validation into data pipelines and CI/CD.

• Check data for missing values and duplicates
• Build a dbt test suite
• Define shared data contracts between teams

Identify a project's existing test tools and conventions, then run the smallest useful test suite for a specific change. Add or update tests when authorized, and report commands, results, and remaining gaps without overstating coverage.

• Run relevant tests for a specific code change
• Identify existing test tools and conventions
• Add or update tests with authorization

Create integration tests for .NET database access before migrating from Oracle to PostgreSQL. The tests record expected Oracle behavior with controlled test data and portable checks, providing a baseline for later migration validation.

• Recording Oracle behavior before migration
• Testing repository methods and stored procedure calls
• Checking empty strings, NULL inputs, and datetime precision

Review existing tests and CI, the automated checks run during development, for redundant coverage, misplaced tests, and opportunities to reduce runtime or cost. Receive file-specific recommendations based on documented improvement patterns, with uncertain findings separated.

• Investigating a slow test suite
• Finding redundant or misplaced tests
• Reviewing CI runtime and cost

Check a gbrain installation after a restart or when services seem broken. It tests key components, repairs some local problems, checks OpenClaw when installed, and records results, with support for custom test scripts.

• Check services after a machine or container restart
• Investigate problems with a gbrain installation
• Check OpenClaw services when installed

Fix defects in Composio SDK through focused reproduction, root-cause analysis, regression tests that check for recurrence, and targeted verification. Use it for reported bugs, failing tests, CI regressions, runtime errors, or incorrect SDK behavior.

• Reproducing and fixing reported SDK bugs
• Investigating failing tests
• Fixing regressions in automated CI checks