automating-computer-use-testing

# Automating Computer-Use Testing

A comprehensive skill for creating Gemini 2.5 Computer Use automation scripts, natural-language goal files, and Playwright-based test harnesses for QA testing of web applications.

## When to Use This Skill

Trigger this skill when the user requests:
- Automating UI testing for web applications
- Creating QA automation scripts
- Writing goal files for Gemini computer use
- Generating Playwright-based test harnesses
- Automating browser interactions (clicking, typing, scrolling)
- Creating test scenarios for regression testing
- Building computer-use automation workflows
- Testing React/Vue/Angular/web applications
- Form automation and validation testing
- Visual regression testing

**Complete overview**: See [README.md](README.md)

## Core Workflow

### Phase 1: Requirements Analysis

1. **Understand the Application**
   - What application are you testing? (URL, tech stack)
   - What are the key UI patterns? (panels, forms, modals, navigation)
   - What user flows need automation? (login, checkout, data entry)
   - Are there existing test scenarios or manual test plans?

2. **Define Automation Objectives**
   - What is the primary goal? (regression testing, UI validation, workflow automation)
   - What constitutes "passing"? (success criteria)
   - What should be verified? (UI elements, data validation, visual appearance)
   - What edge cases or error scenarios should be tested?

3. **Scope the Automation**
   - Which features to include?
   - Which features to exclude or defer?
   - How many test scenarios? (recommend 5-10 per goal file)
   - Expected runtime? (recommend <10 minutes per automation)

### Phase 2: Goal File Generation

The goal file is a natural-language document that Gemini 2.5 Computer Use reads to understand what to test.

**Goal File Structure** (Use template from `templates/goal_template.txt`):
```
[Role Description]
You are a QA engineer testing the [Application Name].

Your goal is to [primary objective].

#