Search: "testing"
Showing 24 of 24 results
prompt-engineer-pro
Prompt Engineer Pro is a production-grade system for teams shipping AI workflows into business-critical environments. Unlike basic prompting assistants, this skill treats prompts as software assets that require governance, audit trails, and regression testing. It helps you build, audit, and harden prompt stacks for complex tasks involving multiple models, tool-use agents, and structured data extraction.
PR Description Generator
Generates comprehensive, structured PR descriptions from git diff or branch comparison. Includes summary, changelog, testing notes, and deployment considerations.
testing
# Grafana Cloud Testing > **Docs**: https://grafana.com/docs/grafana-cloud/testing/ Three pillars: external probing (Synthetic Monitoring), load testing (k6 Cloud), real-user monitoring (Faro). ## Prerequisites - Grafana Cloud stack - Synthetic Monitoring: SM access token (`sm:write`) - k6 Cloud: a Grafana Cloud k6 token + projectID - Faro: a Faro app + write-token from **Frontend Observability → Apps** ## Common Workflows ### 1. Create + verify a Synthetic HTTP check ```bash # 1. Create the check (full pay
E2E Testing Patterns
Build reliable, fast E2E test suites with Playwright and Cypress. Critical user journey coverage, flaky test elimination, CI/CD integration.
Testing Patterns
Unit, integration, and E2E testing patterns with framework-specific guidance. Use when asked to "write tests", "add test coverage", "testing strategy", "test this function", "create test suite", "fix flaky tests", or "improve test quality".
Quant Testing
量化测试流程技能。当用户说"回归测试"、"策略测试"、"回测验证"、"实盘验证"、"测试"、"上线"、"发布"时自动触发。提供回归测试流程、测试用例模板、测试报告模板。适用于量化项目的测试和上线阶段。
browser-testing-toolkit
浏览器测试与自动化工具包。三层架构：L1快速验证（playwright-cli）、L2深度调试（DevTools）、L3复杂测试（Python+E2E）。v1.1 新增智能点击（自动处理遮挡）。
E2E Testing
Use when creating, maintaining, debugging, or reviewing real-browser end-to-end tests with Playwright or Cypress, including Page Object models, CI artifacts,...
Testing Workflow
Meta-skill that orchestrates comprehensive testing across a project by coordinating testing-patterns, e2e-testing, and testing agents. Use when setting up testing for a new project, improving coverage for an existing project, establishing a testing strategy, or verifying quality before a release.
Frontend Testing
Designs and writes frontend unit, component, integration, and E2E tests using Jest, Vitest, Testing Library, MSW, and Playwright with mocks and coverage cons...
回归测试
根据变更范围、风险等级和时间约束制定分级精准回归方案。当版本迭代了、代码改动了、你需要确定"到底哪些功能要重新测一遍"的时候使用此技能。回归的时间永远不够——此技能帮你做出取舍决策：冒烟回归（P0核心流程）、核心回归（高影响区域）、全量回归（有余力时）。基于变更分析和风险评估选择最省时的回归策略，而不是盲目全量回归。 本技能属于 QA Test Skills 技能集（49 个技能之一），完整工作流体验需安装全套：npx skills add Kokxi/qa-test-skills
移动端测试
当需要测试 iOS/Android 原生 App、H5 页面或小程序的移动端专项场景时使用此技能。移动端的坑主要不在功能逻辑上——中断（电话/通知/低电量）、弱网/断网/网络切换、前后台切换、系统权限管理、多机型适配和各种系统版本兼容才是重灾区。不要只测功能流程，移动端的 Bug 有一半以上是中断和兼容性相关的。输出按中断/网络/权限/兼容/性能分类的测试要点清单。 本技能属于 QA Test Skills 技能集（49 个技能之一），完整工作流体验需安装全套：npx skills add Kokxi/qa-test-skills
python-testing
Python testing patterns with pytest, fixtures, TDD, mocking, async and integration tests
testing-with-sandbox
Use when capturing outbound email in development or staging without delivering to real recipients, inspecting HTML or headers, running spam or structure checks, or automating tests against a fake inbox. Use when testing outgoing mail from an app without committing to a production ESP yet. Use when u
统计假设检验技能
统计假设检验工具；支持正态性检验(Shapiro-Wilk/K-S)、t检验(单样本/独立/配对)、卡方检验(拟合优度/独立性)、ANOVA、Levene检验、Mann-Whitney U检验；自动计算统计量、p值、置信区间与效应量；提供结果解释指南
browser-testing
VERIFY your changes work. Measure CLS, detect theme flicker, test visual stability, check performance. Use BEFORE and AFTER making changes to confirm fixes....
Testing Strategy
Deep testing strategy workflow—risk mapping, test pyramid, levels of isolation, flakiness, data, CI gates, and quality signals beyond coverage %. Use when de...
APITester Agent-Driven API Testing
Test API endpoints and document responses. Define tests in plain English, run them, get formatted results. Agent-driven Postman alternative.
mcore-testing
# Testing Guide --- ## Answer-First Testing Facts For questions about disabling tests without deleting them: - Functional recipe entries stay in YAML; disable by suffixing scope with `-broken`, for example `scope: [mr-github]` -> `scope: [mr-github-broken]`. - Unit-test skips use pytest markers instead: `@pytest.mark.flaky_in_dev` skips in the default dev environment, and `@pytest.mark.flaky` skips in LTS. - Do not delete the test case or recipe entry when the goal is discoverability and easy re-enable. ---
frontend-testing-best-practices
# Testing Best Practices Guidelines for writing effective, maintainable tests that provide real confidence. Contains 6 rules focused on preferring E2E tests, minimizing mocking, and testing behavior over implementation. ## Core Philosophy 1. **Prefer E2E tests over unit tests** - Test the whole system, not isolated pieces 2. **Minimize mocking** - If you need complex mocks, write an E2E test instead 3. **Test behavior, not implementation** - Test what users see and do 4. **Avoid testing React components dir
typescript-e2e-testing
# E2E Testing Skill E2E testing validates complete workflows from user perspective, using real infrastructure via Docker. --- ## Workflows For comprehensive step-by-step guidance, use the appropriate workflow: | Workflow | When to Use | |----------|-------------| | [Setup E2E Test](workflows/setup/workflow.md) | Setting up E2E infrastructure for a new or existing project | | [Writing E2E Test](workflows/writing/workflow.md) | Creating new E2E test cases with proper GWT pattern | | [Review E2E Test](workflow
application-security-testing
# Application security testing Entry point for "make my application secure" requests, where the target is not yet a single URL or repo. The job here is to pick the right test per asset, run it, and produce one ranked plan — not to run everything at maximum depth. Install, LLM setup, all CLI flags, and the managed-cloud path live in the **penetration-testing-with-strix** skill. Read it first if `strix --version` fails. Only test assets the user owns or is authorized to test. Confirm authorization before the