skills.rest
leadmind-ai
leadmind-aiOFFICIAL
Explore all skills by this author →
GitHub

testeur-qa

Orchestrate parallel QA testing pipelines for web applications with browser-based agents.

Updated Mar 25, 2026
Search Tags:#automation#testing#qa#playwright#parallel-execution#agent-teams#yaml-tests
One-click install
npx skills add https://github.com/leadmind-ai/leadmind-ai-website --skill testeur-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testeur-qa
Source: https://github.com/leadmind-ai/leadmind-ai-website/tree/main/.claude/skills/testeur/orchestrateur
Command: npx skills add https://github.com/leadmind-ai/leadmind-ai-website --skill testeur-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill orchestrates the QA testing phase by coordinating a team of browser-based QA agents to execute user stories in parallel and deliver an aggregated report.

Core Features & Use Cases

  • Orchestrates five-phase QA pipelines: analysis, transformation to executable YAML tests, reverse-prompt audit, parallel execution, and consolidated reporting.
  • Scales across multiple user stories with one agent per story, enabling rapid validation of complex flows.
  • Produces screenshots and a pass/fail report for traceability and pre-deployment auditing.

Quick Start

Start the QA pipeline by providing your user stories and running the orchestrator to commence the five-phase process.

Frequently Asked Questions about testeur-qa

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

FAQPage Schema
How do I run parallel QA tests for multiple user stories?▼

Parallel QA testing assigns one browser-based agent per user story to execute scenarios simultaneously. This scales validation across complex web application flows without manual execution.

How do I convert user stories into executable YAML tests?▼

User stories are transformed into executable YAML tests during an analysis phase that maps story requirements into structured YAML templates. This generates automated scripts ready for browser agent execution.

What inputs do I need to start automated browser QA testing?▼

Automated browser QA requires structured inputs: user story documents, a features configuration file, and an architecture API reference. These provide the context for agents to execute the testing pipeline.

Does parallel test execution work with Playwright for web applications?▼

Yes, parallel test execution orchestrates browser-based agents to run tests across web applications. The pipeline validates multiple user stories concurrently and generates screenshots for traceability.

How do I generate a pre-deployment QA audit report?▼

A pre-deployment audit report is generated through a reverse-prompt audit phase followed by parallel test execution. The system aggregates pass/fail results and screenshots for each user story.

Related Skills

Explore More Software Engineering Skills→
jsaliojsalio

sdd

Create SDD contracts with data models, API contracts, and documentation from feature ideas.

Community
Advanced
jnlanahanjnlanahan

uat

Generates UAT checklists from commits and planned crop and saves PASS/FAIL/CONDITIONAL PASS reports.

Community
Advanced
Ouro-labsOuro-labs
14

ce-demo-reel

Automate capture of GIFs, terminal recordings, and screenshots for PR evidence.

Official
Advanced
partme-aipartme-ai
610

playwright

Automate browsers and write end-to-end tests with Playwright.

Official
Intermediate