Results for “mom-test”

Guides testing Megatron-LM: test layout, recipe YAML, adding and running unit/functional tests, golden values, marker filters, and CI parity.

妈妈唠叨模式 — 中国式妈妈提醒风格的生产力 coaching。底层行为仍是结构化排障、证据优先、完成质量检查。

妈妈唠叨模式 — 中国式妈妈提醒风格的生产力 coaching。底层行为仍是结构化排障、证据优先、完成质量检查。

Write, create, modernize, or fix comprehensive MSTest unit tests with MSTest 3.x/4.x APIs, covering assertions, data-driven tests, lifecycle, and async patterns.

Configures mewt or muton mutation testing campaigns — scopes targets, tunes timeouts, and optimizes long-running runs.

Run, filter, or troubleshoot .NET tests with `dotnet test`, detecting the test platform (VSTest vs Microsoft.Testing.Platform) and framework to apply the correct command syntax.

Analyzes production code to find gaps in existing tests by reasoning about hypothetical mutations and checking whether tests would catch them.

Write effective unit tests with best practices for any project. Use when writing tests, creating test cases, improving test coverage, increasing confidence before release, or when the user mentions testing. Mutation score / assertion theater → test-mutation.

Verifies that tests for already-implemented behavior are meaningful by temporarily breaking the production code and confirming the test fails for the expected reason.

Escribe tests de frontend centrados en el usuario con Vitest, Testing Library y Playwright, cubriendo unit, integración y E2E, y configura el runner de tests.

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.

Generates unit tests for multiple languages and frameworks, including coverage reports and boundary/exception cases.

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`

Executes Atomic Red Team tests mapped to MITRE ATT&CK techniques, performs coverage gap analysis, and runs detection validation loops to measure blue team visibility.

Test Python services with pytest, async coverage, monkeypatch, and boundary-focused fakes. Use when writing Python tests, fixtures, async tests, regression tests, or dependency-isolated verification.

Writes Jest unit tests for Lightning Web Components using @salesforce/sfdx-lwc-jest, covering wire adapter mocks, imperative Apex mocking, and async rerender handling.

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.

Determines when to test for germline KCNJ5 mutations indicating familial hyperaldosteronism type III in very young patients with primary aldosteronism. Triggered by severe early-onset hypertension with hypokalemia in infants or young children (<20 years) with confirmed PA.

Simulates man-in-the-middle attacks using Ettercap, mitmproxy, and Bettercap in authorized environments to intercept, analyze, and modify network traffic for testing encryption enforcement, certificate validation, and detection capabilities.

Generates comprehensive unit tests with edge cases, error paths, and boundary values. Auto-detects the test framework, scans for untested functions, adopts existing conventions, runs tests, and self-heals failures in up to 3 iterations while measuring coverage.

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

Use when writing or modifying tests in a Bun project

Verifies test effectiveness by introducing small bugs into production code and running the test suite to find weak or missing tests.

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines.

Run mutation testing against a project's test suite to verify the tests actually catch failures when source code is broken. Use after major test changes, before declaring a suite "good", or when coverage % looks healthy but you suspect tests aren't catching real bugs.