「test」の検索結果

Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (OUSD R&E, August 2022). Use for DoD test and evaluation (T&E) across the Adaptive Acquisition Framework — the four test communities (contractor testing, developmental DT&E, operational OT&E, live-fire LFT&E); the five operational events (Operational Demonstration, EOA, OA, IOT&E, FOT&E) and the OTRR gate; the T&E Strategy / TEMP and its IDSK, with the upstream documents that feed it and the test plans that decompose it; the T&E organizations and oversight roles (USD(R&E), DOT&E, TRMC, the Service Executives and OTAs, the T&E WIPT, CDT); and pathway-specific T&E for all six acquisition pathways (Urgent Capability, Middle Tier, Major Capability, Software, Defense Business Systems). Statutory anchors include 10 U.S.C. §4171 (IOT&E) and §4172 (LFT&E/FUSL). This is guidance, not policy: it points outward to DoDI 5000.89 and the DoDI 5000-series for binding detail, and is thin on detailed test statistics/design-of-experiments methodology, cost estimating, the Acquisition of Services pathway, and any CUI/CAC-gated companion guides.

日本語の概要は準備中です。原文の説明を表示しています。

Repair and triage guide for the NV oOS PHPUnit test suite — Docker test environment (incl. cross-worktree one-off runners), CI log triage, and 71 recurring root-cause patterns (hook resets, singleton interference, WP_Error envelope drift, coverage-manifest drift, preset-accounting gaps, and more — see the patterns section). Covers the cluster-by-cluster PR workflow against alpha-working and validation gates. Use when fixing failing PHPUnit tests, triaging CI logs, repairing test drift, deciding between a production fix and a test fix, or starting a new fix cluster.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "test our messaging before we scale it", "design a message-market-fit panel", or "run a 5-second comprehension test on our new tagline"; produces a message-test design spec — hypothesis, panel and recruit criteria, comprehension / 5-second / message-market-fit (Wynter-style) protocols, stimulus set drawn from the canon, success thresholds, and a stop/revise decision rule — for the TALE Evaluate phase so the message is validated before any paid scale. It designs the test; it never runs the experiment or adjudicates a claim. Not for running the panel or A/B experiment — use send-experiment-designer or ad-test-designer; not for analyzing the results — use performance-analyzer; not for authoring the message itself — use message-system-architect. 消息测试/理解度测试/面板设计/五秒测试/消息市场契合

日本語の概要は準備中です。原文の説明を表示しています。

Generate Vue.js component test skeletons (Vue Test Utils) from specifications.

日本語の概要は準備中です。原文の説明を表示しています。

Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate any tdmcp test-coverage work: run the coverage harness, inspect coverage gaps, plan focused Vitest/msw or bridge tests, delegate coverage writers, verify coverage deltas, and re-run gates. Use whenever the user asks to raise coverage, add broad regression coverage, create a test harness, improve tests, re-run a coverage wave, or fix a coverage gate.

日本語の概要は準備中です。原文の説明を表示しています。

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

日本語の概要は準備中です。原文の説明を表示しています。

Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Cypress Deep — cypress end-to-end testing management and analysis. Covers test execution monitoring, dashboard integration, screenshot and video analysis, test report parsing, flaky test detection, and configuration auditing. Use when investigating test failures, reviewing Cypress Cloud results, or managing Cypress test suites.

日本語の概要は準備中です。原文の説明を表示しています。

Expert en tests d'agents IA (tests unitaires, intégration, régression, guardrails, red teaming agents)

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.

日本語の概要は準備中です。原文の説明を表示しています。

Automated WCAG 2.1 AA accessibility testing with axe-core and Lighthouse CI. Auto-detects frontend framework (React, Next.js, Vue, Angular, Svelte, Astro, Flutter, React Native), discovers all routes and interactive components, installs Playwright + axe-core for page-level scanning and jest-axe/vitest-axe for component-level testing. Generates tests for color contrast (4.5:1), alt text, form labels, ARIA attributes, heading order, landmark regions, focus visibility, keyboard navigation (tab order, focus traps, modal focus management, skip-to-content), screen reader compatibility (aria-live regions, error announcements, toast notifications), and Flutter Semantics validation (48dp touch targets, semanticLabel). Reports violations by severity (critical, serious, moderate, minor) with WCAG criterion references. Use when adding a11y testing, auditing accessibility compliance, fixing contrast issues, or validating keyboard and screen reader support.

日本語の概要は準備中です。原文の説明を表示しています。

Build, maintain, and run conformance tests for canonical App-in-Skill projects created by kelly-app-skill-creator. Use when a Kelly app skill needs contract checks, local server smoke tests, responsive browser acceptance, temporary open-source Busabase integration, environment-gated Busabase Cloud OAuth verification, lazy provisioning checks, persistence tests, AirApp parity tests, or CI coverage. Keep app creation in kelly-app-skill-creator and own only the reusable test harness, per-skill fixtures, execution gates, diagnostics, and truthful pass/fail/skip reporting.

日本語の概要は準備中です。原文の説明を表示しています。

Stryker-driven test cull: delete slop, consolidate redundants, fill mutation-coverage gaps. Score up, test count and lines down. Use when the user says 'trim tests', '/trim-tests', or wants to clean up LLM-generated test bloat. No args picks the worst-scored file; argument scopes to a section, service, or file.

日本語の概要は準備中です。原文の説明を表示しています。

Storybook (UI カタログ) リファレンス。story, CSF (Component Story Format), CSF Next (CSF Factories), args, argTypes, decorators, play function, interaction tests, autodocs, main.ts / preview.ts, アドオン (a11y, controls, viewport, themes), Vitest addon, test-runner, Storybook MCP server, components manifest, アドオン作成, upgrade / migration。

Playwright v1.64 (E2E / コンポーネントテストフレームワーク) リファレンス。 test, expect, page, locator, getByRole / getByText / getByLabel / getByTestId / getByRef、 toBeVisible, click, fill, route, mock, fixtures、playwright.config.ts、 auth 永続化、Credentials (passkeys / WebAuthn)、WebStorage、WebMCP、 Playwright MCP / playwright-cli、trace viewer、screencast、test locks、codegen、UI モード。

App Store Connect API 4.5.1 (REST) アプリ配布リファレンス。JWT 認証、API キー作成・失効、 Apps, Builds, Bundle IDs, Bundle ID Capabilities, Certificates, Devices, Provisioning Profiles, Users, User Invitations, Merchant IDs, Pass Type IDs、TestFlight (Beta Groups / Testers)、 Sandbox Testers、App Review, Review Submissions, Customer Reviews, Custom Product Pages, Phased Release、In-App Purchases, Subscriptions, Subscription Groups, App Price Points, Promotional Offers, Win-back Offers, Sales Reports、App Asset Library (screenshots / app previews)、 Webhooks / Webhook Events / Deliveries、Xcode Cloud (Workflows, Build Runs, Artifacts)、 Alternative Distribution (EU マーケットプレイス / Web Distribution)、 Game Center (Achievements, Leaderboards, Challenges)、Analytics / 診断レポート。

Use when writing tests of any kind — unit, slice, or integration. Covers test structure, naming conventions, Mockito patterns, @WebMvcTest, @DataJpaTest, and Testcontainers setup.

日本語の概要は準備中です。原文の説明を表示しています。

Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR. Keep ordinary implementation and pre-commit use scoped to the affected behavior, not a repository-wide audit.

日本語の概要は準備中です。原文の説明を表示しています。

Write comprehensive end-to-end tests that verify complete user workflows, integration between components, and system behavior from user perspective using Playwright, Cypress, or similar frameworks. Use when testing user flows, verifying feature integration, testing across real browsers, ensuring UI interactions work correctly, validating form submissions end-to-end, testing authentication flows, catching regressions, automating QA processes, testing API integrations, or building confidence in production deployments.

日本語の概要は準備中です。原文の説明を表示しています。

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

日本語の概要は準備中です。原文の説明を表示しています。

Turn a large dataset (an existing oversized Coval test set, an export of past conversations, or a CSV/JSON of cases) into a small, high-signal Coval test set by removing duplicates, identifying unique scenarios, and selecting a representative, failure-weighted subset — then bulk-loading it with no row cap. Use when the user says "I have thousands of cases", "dedupe my test set", "my test set is too big", "turn this dataset into a test set", "pick representative scenarios", or "my CSV import only kept 10 / uploaded everything".

日本語の概要は準備中です。原文の説明を表示しています。

Detects test antipatterns and code smells in PHP test suites. Identifies 15 smells (Logic in Test, Mock Overuse, Fragile Tests, Mystery Guest, etc.) with fix recommendations and refactoring patterns for testability.

日本語の概要は準備中です。原文の説明を表示しています。

Create test versions to verify app auto-update functionality. Use when testing update flows, version migration, or validating app upgrade mechanisms. Automates version number and build number configuration for testing the auto-update system. Triggers on auto update, app upgrade, update testing, upgrade flow, version migration, test build, 9XXX version.

日本語の概要は準備中です。原文の説明を表示しています。