argent-qa-flows

Creates repeatable QA regression E2E tests as Argent flows from test cases and acceptance criteria.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seyamalam/pstu_final --skill argent-qa-flows-seyamalam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: argent-qa-flows
Source: https://github.com/Seyamalam/pstu_final/tree/main/.agents/skills/argent-qa-flows
Command: npx skills add https://github.com/Seyamalam/pstu_final --skill argent-qa-flows-seyamalam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning tickets, test cases, and acceptance criteria into durable automated regression tests is slow and error-prone. This Skill converts them into deterministic Argent flows with stable selectors, executable evidence, and a two-pass completion gate so regressions are caught reliably. ## Core Features & Use Cases - Test Contract Definition: Maps every requirement to a hard await:, assert:, or reviewed snapshot: check with a compact contract table before recording. - Deterministic Setup and Teardown: Enforces a named data baseline, safe reset or seed flows, and end-state restoration so repeated runs stay independent. - Multi-Platform Coverage: Supports iOS, Android, Chromium, and Vega (Fire TV) with recorded tv-remote steps, while flagging Apple TV and Android TV as unsupported. - Two-Pass Proof Gate: Requires the unchanged YAML to pass twice consecutively with fresh mobile services before the flow is considered complete. - Use Case: Given a ticket stating "selecting Dark in Settings shows Dark selected and Light absent", produce a qa-settings-theme flow that proves the state change, verifies dark rendering via snapshot, restores the baseline, and passes twice. ## Quick Start Ask the agent to create a QA regression flow from your ticket or acceptance criteria, for example: "Create a QA flow verifying that enabling dark mode in Settings persists after restart."

Frequently Asked Questions about argent-qa-flows

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

FAQPage Schema
How do I create a QA regression test from a ticket or acceptance criteria?

Define a compact test contract mapping each requirement to a hard await, assert, or snapshot check, then record the scenario as an Argent flow. The flow must pass twice consecutively with the same runner before it is considered complete.

What platforms does Argent flow testing support?

Argent flows support iOS, Android, Chromium, and Vega (Fire TV). Vega uses recorded tv-remote steps instead of touch directives. Apple TV and Android TV are unsupported and require argent-tv-interact with the limitation reported.

When should I use argent-qa-flows instead of argent-create-flow?

Use argent-qa-flows when you have test cases, tickets, or acceptance criteria needing a preserved regression scenario with a two-pass proof gate. For one-off UI checks or replayable paths without acceptance criteria, use argent-test-ui-flow or argent-create-flow.

Why does a QA flow need two consecutive passes?

Two passes prove the flow is deterministic and independent of leftover state. Pass 1 starts with fresh mobile Argent services so a fixed timing margin cannot pass twice purely because environment speed was unchanged.

How do I verify an element is absent in an Argent flow?

First establish the same stable selector as visible on the containing screen, then perform the action, then assert it as hidden. Viewport absence in a collection is not global absence, so use seeded position, count, or empty-state evidence.

What are the limitations of Argent flows on TV platforms?

Vega supports launch, await, assert, snapshot, and idle but has no touch directives, so navigation uses recorded tv-remote steps gated by identity checks. Apple TV and Android TV fail at the gesture layer and are out of scope.