'performance-testing' 검색 결과

Test native, React Native, hybrid, and Flutter mobile apps with Appium 3.x, Detox, Maestro, and Patrol. Covers device farm setup (BrowserStack, Sauce Labs), gesture simulation, deep link and cold-start testing, push notifications, biometric (Face ID) auth, offline/poor-network simulation, and iOS/Android permission dialog handling. Use when: "mobile test," "Appium," "Detox," "Maestro," "Patrol," "Flutter test," "iOS test," "Android test," "device farm," "deep link," "biometric," "Face ID," "permission dialog," "React Native test." Not for: device/browser matrix strategy in the abstract — use cross-browser-testing; app startup/memory/battery profiling depth — use performance-testing; mobile screenshot diffing — use visual-testing. Related: ci-cd-integration, cross-browser-testing, performance-testing, test-data-management, test-reliability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Add or update Handsontable performance tests for rendering and user interactions. The skill guides trace recording, measurement boundaries, baseline comparisons, and reports that help reviewers identify performance changes in pull requests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a performance test for a Handsontable feature
• Investigate filtering or sorting performance
• Compare performance changes in a pull request

Measure indicator calculation speed with BenchmarkDotNet, a benchmarking tool for .NET. Compare batch, incremental, and streaming implementations, detect slowdowns against saved results, and evaluate changes intended to reduce processing time and memory allocations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing batch, incremental, and streaming performance
• Detecting performance regressions after code changes
• Adding benchmarks for a new indicator

Coordinate specialized code, security, architecture, and performance reviewers and consolidate their results. Use when a codebase needs parallel review across multiple disciplines.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Combine static analysis with model-assisted code review to assess security, performance, correctness, and architecture. Use when designing review automation or reviewing complex changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Testing for React/Next.js with Jest, React Testing Library, and Playwright. Use when generating tests, writing unit tests, analyzing coverage, scaffolding E2E tests, configuring Jest, or improving test quality.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Load testing with k6/Artillery, response time thresholds, memory leak detection, N+1 query detection, and CI integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test application performance with k6 load/stress/soak/spike scripts and k6 scenarios, Lighthouse CI for Web Vitals, and performance budgets as CI gates. Covers load profiles, custom metrics, bottleneck identification, and Core Web Vitals (LCP, INP, CLS). Use when: "performance test," "load test," "stress test," "soak test," "spike test," "k6," "k6 scenarios," "Lighthouse," "Web Vitals," "Core Web Vitals," "performance budget." Not for: scheduled production probes — use synthetic-monitoring; pixel-diff regressions — use visual-testing; designing tests from prod telemetry — use observability-driven-testing. Related: ci-cd-integration, qa-metrics, release-readiness.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scheduled probes that run CONTINUOUSLY after release. Covers probe design for critical user journeys, alerting integration, SLA validation, multi-region monitoring, and the boundary between QA and SRE. Use when: "synthetic monitoring," "uptime testing," "scheduled probes," "SLA validation," "availability monitoring," "post-deploy checks." Not for: safe-release techniques during rollout — use testing-in-production. Not for: designing tests from prod telemetry — use observability-driven-testing. Not for: a one-shot post-deploy smoke gate tied to a release — use release-readiness. Related: testing-in-production, release-readiness, performance-testing, qa-metrics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate system resilience through controlled fault injection. Covers hypothesis-driven chaos experiments, failure injection types (network, service, infrastructure, dependency), LitmusChaos/Chaos Mesh/AWS FIS/Gremlin/toxiproxy tooling, automated abort gating, game day planning, and progressive chaos adoption. Use when: "chaos engineering," "fault injection," "resilience test," "game day," "failure recovery," "system reliability," "blast radius." Not for: safe rollout flags/canary/dark launch during a release — use testing-in-production; designing new tests from production telemetry — use observability-driven-testing. Related: testing-in-production, observability-driven-testing, performance-testing, release-readiness, test-environments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

评估系统性能 / 容量 / 压测时使用。适用于上线前性能基线、SLA 验证、容量规划、性能退化排查。融合 Google SRE Workbook、Brendan Gregg USE Method、k6/JMeter 实践。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.