Results for “a-b-testing”

Comprehensive web application testing patterns with Playwright selectors, wait strategies, and best practices

Performs load testing with Locust, Python-based distributed testing, and real-time web UI.

Prevents AI-introduced regressions with sandbox-mode API testing, automated bug-check workflows, and patterns that catch blind spots where the same model writes and reviews code.

Runs a disciplined debugging loop for hard bugs and performance regressions, covering reproduction, hypothesis testing, instrumentation, fixing, and regression testing.

Provides C# and .NET testing patterns using xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.

Generate and run Jest tests for Adobe App Builder actions and React Spectrum UI components, including unit, integration, contract, and component tests with mock helpers for Adobe SDKs.

Guides writing behavior-focused React component and hook tests with React Testing Library, Vitest/Jest, MSW network mocking, and axe accessibility assertions, including when to use component vs end-to-end tests.

When the user wants to perform load testing, stress testing, or performance testing of APIs and websites using k6. Also use when the user mentions "k6," "load test," "performance test," "stress test," "spike test," "soak test," "thresholds," "virtual users," or "VUs." For browser-based testing, see selenium.

Runs adversarial UI tests in a real browser using the browse CLI, analyzing git diffs to test only changed areas or exploring the full app to find bugs in functionality, accessibility, responsive layout, and UX.

Applies practical test-first and regression testing to behavior changes, bug fixes, state transitions, and public contracts.

Drive development with tests by writing a failing test before implementing code, and reproduce bugs with tests before fixing them.

Runs load, stress, and performance tests using k6, JMeter, and profiling tools, with capacity planning and benchmarking for APIs and backend services.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, or refactoring.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, and refactoring.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests when writing features, fixing bugs, or refactoring code.

Stops fantasy approvals, evidence-based certification - Default to "NEEDS WORK", requires overwhelming proof for production readiness

Kotest — flexible, idiomatic Kotlin testing framework. Multiple specification styles (StringSpec, FunSpec, BehaviorSpec, DescribeSpec, FeatureSpec, FreeSpec), rich matcher library, property-based testing, data-driven tests, coroutine support, KMP-friendly. Drop-in alternative or complement to JUnit. USE WHEN: user mentions "Kotest", "io.kotest", "shouldBe", "StringSpec", "BehaviorSpec", "DescribeSpec", "kotest property testing", "Arb.list", "forAll", "kotest matchers", "kotlin tests" DO NOT USE FOR: JUnit-specific patterns - use junit skill (or framework-specific test skills) DO NOT USE FOR: Flow testing - use `testing/turbine` DO NOT USE FOR: Compose snapshot tests - use `testing/compose-snapshot` DO NOT USE FOR: Mobile E2E - use `testing/maestro`

Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions, including A/B testing, sample size estimation, and statistical interpretation.

A/B and multivariate testing methodology. Design experiments, calculate sample sizes, determine statistical significance, avoid common pitfalls, and interpret results. Platform-agnostic framework applicable to landing pages, emails, ads, pricing, and product features. Use when the user asks about A/B testing, split testing, experiment design, statistical significance, or conversion experiments.

Recommends against performing dynamic GnRH stimulation testing in the evaluation of hypogonadism, as it provides no additional diagnostic information beyond baseline gonadotropins and sex steroids. Consider this recommendation when evaluating hypogonadism and contemplating GnRH testing.

Provides Playwright patterns for building stable E2E test suites, including Page Object Model, configuration, flaky test strategies, artifact management, and CI/CD integration.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

Sets up a reliable end-to-end test suite as a per-PR gate, with real flows, layered assertions, reusable auth helpers, and video evidence.

Auto-detects the project's tech stack, then generates and runs exhaustive end-to-end tests for backend APIs and frontend UI flows, self-healing failures without user input.

Automates browser interactions for web testing, form filling, screenshots, and data extraction.

Provides Playwright patterns for building stable, fast, and maintainable E2E test suites, including Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

WelineFramework local testing adapter. Use when working in this repo on how to write module tests, choose validation layers, or run PHPUnit, Pest, Vitest, Playwright, HTTP smoke, Browser smoke, or WLS-backed test flows. Read dev/ai/skills/testing/SKILL.md before acting.

Guides the creation, iterative improvement, and evaluation of agent skills, including drafting, testing, benchmarking, and optimizing descriptions.

Enforces a mandatory pre-commit/pre-PR testing gate: detects the test stack, runs the full suite, fixes failures, creates minimal tests when none exist, and verifies coverage before allowing commits.

Tests local web applications with Playwright, including server lifecycle management, DOM inspection, and screenshot capture.

Write behavior-focused React component tests with React Testing Library, Vitest/Jest, MSW for network mocking, and accessibility assertions using axe, while deciding when to use component tests versus Playwright/Cypress end-to-end tests.

Runs a QA validation cycle followed by bugfix until all criteria pass clean, with automated verification and re-validation.

Control browsers via a CLI tool that runs sandboxed JavaScript scripts for automation, testing, and data extraction.

Write defensive, production-grade Bash scripts with strict error handling, safe patterns, and comprehensive testing.