DEV.co
Open-Source Testing · qawolf

cli

QA Wolf CLI is a terminal tool for running end-to-end test automation flows locally or in CI/CD pipelines. It integrates with the QA Wolf platform for flow creation and cloud execution but can also run flows standalone after local setup.

Source: GitHub — github.com/qawolf/cli
3.4k
GitHub stars
139
Forks
TypeScript
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryqawolf/cli
Ownerqawolf
Primary languageTypeScript
LicenseApache-2.0 — OSI-approved
Stars3.4k
Forks139
Open issues4
Latest releasev1.1.0 (2026-07-01)
Last updated2026-07-07
Sourcehttps://github.com/qawolf/cli

What cli is

TypeScript-based CLI for executing Playwright-driven E2E test flows defined in `.flow.ts` format. Supports local execution via npm/yarn/pnpm or standalone binaries (Linux/macOS/Windows); Node 20.19+ required for npm installation. Integrates with QA Wolf platform API for authentication, flow syncing, and run management.

Quickstart

Get the cli source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/qawolf/cli.gitcd cli# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

CI/CD E2E Test Automation

Run QA Wolf flows directly in GitHub Actions, GitLab CI, or other CI systems using API key authentication and the CLI's standalone binaries or npm installation.

Local Flow Development & Testing

Author and test Playwright-based flows locally with `qawolf init`, then run them via `qawolf flows run` before pushing to platform or CI.

AI Agent Integration

Use the included Claude Code agent skill (`skills/qawolf-cli/SKILL.md`) to allow AI agents to discover and invoke QA Wolf CLI commands programmatically.

Implementation considerations

  • Ensure Node 20.19+ (preferably 22+) is available; standalone binaries available for environments without Node.js.
  • Require QA Wolf platform account and API key (`QAWOLF_API_KEY` env var) for most workflows; set up in CI using secrets.
  • Flows are stored in `.qawolf/<env>` cache and synced via `qawolf flows pull`; design CI to manage cache invalidation and dependency installation.
  • Standalone flows created with `qawolf init` work offline; platform-synced flows require network access for initial pull.
  • Browser runtime dependencies installed via `qawolf install` (Playwright browsers); ensure CI agent has disk space and network access.

When to avoid it — and what to weigh

  • No QA Wolf Platform Account Required But Limited Solo Use — While `qawolf init` allows local-only projects, most features (flow creation, AI generation, team collaboration, cloud execution) require a QA Wolf platform account at qawolf.com.
  • Not a Unit/Integration Test Runner — This is strictly for E2E browser automation via Playwright; if you need unit or API testing frameworks, this is not the tool.
  • Node 20 EOL (April 2026) — Upgrade Path Risk — Node 20 reached end-of-life in April 2026; the CLI still supports it but only for legacy environments. New projects should use Node 22+.
  • Vendor Lock-In Considerations — Core feature set (flow creation, AI generation, team collaboration, managed cloud execution) lives in the proprietary QA Wolf platform; flows are not easily portable to other frameworks.

License & commercial use

Apache-2.0 license. Permissive, OSI-approved license allowing commercial use, modification, and distribution with attribution and liability disclaimer.

Apache-2.0 is a permissive license; commercial use of the CLI itself is permitted. However, most valuable platform features (flow generation, cloud execution, team collaboration) are part of the proprietary QA Wolf platform, which has its own commercial terms. Verify QA Wolf platform licensing separately.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationStrong
License clarityClear
Deployment complexityLow
DEV.co fitStrong
Assessment confidenceHigh
Security considerations

API key (`QAWOLF_API_KEY`) required for platform integration; must be stored securely as a CI secret. Vulnerability reporting process documented in SECURITY.md. No explicit security audit or threat model provided; assess based on your risk profile and the proprietary platform's security posture (outside this CLI repo).

Alternatives to consider

Playwright Test (native)

Direct Playwright test runner; lower lock-in, no platform dependency, but requires manual test authoring and no built-in cloud execution or AI generation.

Cypress CLI

Popular E2E runner with CI support and lower vendor lock-in. Does not include AI-powered test generation or cloud execution.

Testcafe CLI

Browser automation CLI with good CI/CD support. No platform-integrated flow generation or cloud execution; less opinionated than QA Wolf.

Software development agency

Build on cli with DEV.co software developers

Evaluate QA Wolf CLI for your team's test infrastructure. Start with a free platform account at qawolf.com or run `npx @qawolf/cli --help` to explore locally.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

cli FAQ

Can I run QA Wolf flows without a platform account?
Partially. Use `qawolf init` to set up a local-only project and author flows manually in TypeScript. Full AI generation, flow creation UI, and team collaboration require a QA Wolf account.
What Node.js versions are supported?
Node 20.19+ is officially supported (but Node 20 reached EOL in April 2026). Node 22+ is recommended. Standalone binaries do not require Node.js.
How do I authenticate in CI?
Set the `QAWOLF_API_KEY` environment variable in your CI secrets, or use `qawolf auth login` interactively (not recommended for CI). Authentication is required to pull flows from the platform and manage runs.
Are flows portable to other test frameworks?
Flows are `.flow.ts` TypeScript files using Playwright under the hood. Exporting to pure Playwright tests is not explicitly documented; check docs.qawolf.com for portability options.

Software development & web development with DEV.co

DEV.co helps companies turn open-source tools like cli into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source testing stack.

Ready to automate E2E testing?

Evaluate QA Wolf CLI for your team's test infrastructure. Start with a free platform account at qawolf.com or run `npx @qawolf/cli --help` to explore locally.