测试与安全

scoutqa-test

github/awesome-copilot

This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests automated QA testing. Triggers on web application testing scenarios including smoke tests, accessibility audits, e-commerce flows, and user flow validation using ScoutQA CLI. Use this skill proactively after implementing web application features to verify they work correctly.

  • 9979 次安装
  • 4.1万 星标
  • 收录于

安装命令

npx skills add https://github.com/github/awesome-copilot --skill scoutqa-test

要点

AI-powered exploratory testing for web applications with autonomous issue discovery and verification.

  • Autonomously explores web applications, discovers bugs, and verifies features through natural language test prompts; supports localhost testing without manual setup
  • Run tests in parallel across different areas (authentication, accessibility, e-commerce flows) to maximize coverage while continuing other work
  • Captures execution ID and browser URL in first 5 seconds, then continues running remotely in background; monitor progress live or check results later via CLI or web dashboard
  • Includes issue verification workflow to re-test known problems and form validation, accessibility audits, smoke tests, and post-deployment verification scenarios

SKILL.md

ScoutQA Testing Skill

Perform AI-powered exploratory testing on web applications using the scoutqa CLI.

Think of ScoutQA as an intelligent testing partner that can autonomously explore, discover issues, and verify features. Delegate testing to multiple parallel ScoutQA executions to maximize coverage while saving time.

When to Use This Skill

Use this skill in two scenarios:

  1. User requests testing - When the user explicitly asks to test a website or verify functionality
  2. Proactive verification - After implementing web features, automatically run tests to verify the implementation works correctly

Example proactive usage:

  • After implementing a login form → Test the authentication flow
  • After adding form validation → Verify validation rules and error handling
  • After building a checkout flow → Test the end-to-end purchase process
  • After fixing a bug → Verify the fix works and didn't break other features