qa

Automate smoke testing of live deployments against production URLs.

2|7|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/chidekina/aria-superpowers --skill qa-chidekina
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/chidekina/aria-superpowers/tree/main/skills/qa
Command: npx skills add https://github.com/chidekina/aria-superpowers --skill qa-chidekina

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validates production deployments by quickly surfacing health, authentication, and route-access issues before customers are affected.

Core Features & Use Cases

  • Playwright-based smoke tests that check health endpoints, login flows, and access to protected routes.
  • Supports quick validation of new deployments across multiple projects and environments.
  • Generates a concise test result report with pass/fail status and screenshots.

Quick Start

Run the smoke test against your target URL to verify health and auth flows.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run automated smoke tests against live production deployments?▼

Automated smoke tests validate live production deployments using Playwright-based scripts to check health endpoints, login flows, and protected routes. You configure the target deployment using parameters like --url, --project, and --auth to verify stability.

What is smoke testing for production URLs and when do I need it?▼

Smoke testing for production URLs is the process of rapidly validating health and authentication on live apps after a release. You need it to surface route-access and login issues immediately following new deployments across multiple projects and environments.

Can I verify protected routes and login flows using Playwright smoke tests?▼

Yes, you can verify protected routes and login flows using Playwright smoke tests. The scripts perform health checks and authentication verification against your specified production URL, generating a concise pass/fail report with screenshots.

Does this smoke testing approach work for validating multiple projects and environments?▼

Yes, this smoke testing approach works for validating multiple projects and environments. You can apply the bundled scripts across different deployment targets by passing the appropriate --url and --project parameters for each configuration.

What's the best way to perform health checks after a new app deployment?▼

The best way to perform health checks after a new app deployment is to run automated smoke tests against the production URL. This quickly validates health endpoints and authentication, surfacing route-access issues before customers are affected.

Do I need to provide authentication credentials to test protected routes?▼

Yes, you need to provide authentication credentials to test protected routes. The smoke test scripts support an --auth parameter, allowing the automated tests to successfully navigate through login flows and verify access controls on live deployments.