runtime-qa-validation

Run acceptance journeys in a live browser and produce a runtime QA verdict package.

Updated Jan 30, 2019
One-click install
npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill runtime-qa-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-qa-validation
Source: https://github.com/nishantnaagnihotri/tark-vitark/tree/main/.github/skills/runtime-qa-validation
Command: npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill runtime-qa-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runtime QA workflow enables validating acceptance-criterion user journeys in a real browser session, generating a formal verdict package to gate UI-impacting changes.

Core Features & Use Cases

  • End-to-end runtime UI verification across multiple viewports and themes in a live app session.
  • Produce a Runtime QA Verdict Package to inform orchestrator decisions and gate merge progression.
  • Support loop-back on runtime failures and post-handoff validation with deterministic dev-server orchestration.

Quick Start

Initiate a live browser QA session to validate acceptance journeys across required viewports and themes and generate the Runtime QA Verdict Package.

Frequently Asked Questions about runtime-qa-validation

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

FAQPage Schema
How do I automate runtime UI validation in a live browser session?

Runtime UI validation works by executing acceptance journeys in a live browser session across multiple viewports and themes, then collecting evidence and AC-DELTA conflicts to produce a formal verdict package for orchestration review.

What is a runtime QA verdict package and when do I need one?

A runtime QA verdict package is a formal output generated by validating acceptance-criterion user journeys in a real browser session. You need one to gate UI-impacting changes, support post-handoff UI verification, and loop-back on runtime failures.

How do I validate UI readiness across multiple viewports and themes?

Validate UI readiness across viewports and themes by starting a deterministic dev server, checking its readiness, and executing acceptance journeys in a live browser session. This captures runtime UI behavior and potential AC-DELTA conflicts for orchestration review.

Do I need a deterministic dev server to run end-to-end UI verification?

Yes, end-to-end UI verification requires starting a deterministic dev server and validating its readiness before running acceptance journeys. This ensures the live browser session captures consistent runtime UI behavior across required viewports and themes.

How do I handle runtime failures during post-handoff UI verification?

Handle runtime failures during post-handoff UI verification by using loop-back on runtime failures within the live browser session. This process collects evidence and potential AC-DELTA conflicts to generate a verdict package for orchestration review.