qa

Analyze git diffs to classify changes and run targeted browser or API tests.

22.7k|2.1k|Updated Feb 28, 2024
One-click install
npx skills add https://github.com/Skyvern-AI/skyvern --skill qa-skyvern-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Skyvern-AI/skyvern/tree/main/skyvern/cli/skills/qa
Command: npx skills add https://github.com/Skyvern-AI/skyvern --skill qa-skyvern-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of testing code changes by intelligently analyzing git diffs, selecting the appropriate validation methods (frontend, backend, or both), and reporting the results with clear evidence.

Core Features & Use Cases

  • Diff-driven Validation: Automatically determines the scope of changes (frontend, backend, or mixed) based on git diff.
  • Targeted Testing: Executes specific browser QA for frontend changes or API validation for backend changes.
  • Evidence Reporting: Generates a comprehensive report with pass/fail status and supporting evidence like screenshots or API response snippets.
  • Use Case: After making changes to a web application's user interface and an associated API endpoint, this Skill will first validate the API changes and then perform targeted browser tests on the updated UI elements, reporting any regressions.

Quick Start

Run the qa skill to automatically validate your current code changes.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate code validation for git diffs?

Automated code validation works by analyzing git diffs to classify changes as frontend, backend, or mixed, and then executing targeted automated testing strategies based on that classification.

What is diff-driven testing and how does it work?

Diff-driven testing is a mechanism that reads git diffs to determine the scope of code changes, enabling targeted execution of browser QA for frontend updates or API request validation for backend code.

How do I run targeted browser QA and API validation after UI changes?

You can run targeted browser QA and API validation by executing the skill on your current branch; it automatically detects mixed changes and validates API endpoints before testing updated UI elements.

Do I need the gh cli to run automated testing strategies?

Yes, the gh command line tool is a required dependency to support the continuous integration workflows and code validation processes executed by this automated testing skill.

How does evidence reporting work for failed tests?

Evidence reporting generates a comprehensive pass/fail status report that includes supporting visual and technical evidence like screenshots for browser QA and API response snippets.