---
name: freewheel-test-automation
description: "Run FreeWheel sandbox, integration, tag, and pre-production tests."
version: 2.0.0
author: Hermes Agent (rebuild)
license: Proprietary site content
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [FreeWheel, Implementation, QA, Operations]
    related_skills: []
---

# FreeWheel Test Automation

Use for automating FreeWheel ad implementation testing — sandbox campaigns, tag testing, integration validation, and pre-production QA.

## Test Types

- **Sandbox campaigns** — test campaigns in sandbox environment
- **Tag testing** — VAST/VPAID tag testing
- **Integration validation** — ad server integration validation
- **Pre-production QA** — pre-production quality assurance
- **Ad delivery testing** — ad delivery path testing
- **Creative testing** — creative delivery and playback testing
- **Verification testing** — verification integration testing

## Sandbox Campaigns

- **Sandbox environment** — FreeWheel sandbox for testing
- **Sandbox campaign creation** — create test campaigns in sandbox
- **Sandbox inventory** — sandbox inventory for testing
- **Sandbox demand** — sandbox demand sources for testing
- **Sandbox configuration** — configure sandbox for test scenarios
- **Sandbox cleanup** — cleanup sandbox after testing
- **Sandbox reporting** — generate sandbox test reports

## Tag Testing

- **VAST tag testing** — test VAST tag responses
- **VPAID tag testing** — test VPAID tag execution
- **Tag wrapper testing** — test ad wrapper chains
- **Tag tracking testing** — test tracking event URLs
- **Tag error testing** — test tag error handling
- **Tag performance testing** — test tag response time
- **Tag validation** — validate tag before testing

## Integration Validation

- **Ad server integration** — validate ad server connectivity
- **Tracker integration** — validate tracking URL integration
- **Verification integration** — validate verification partner integration
- **Measurement integration** — validate measurement partner integration
- **SSP integration** — validate SSP inventory integration
- **Streaming Hub integration** — validate Streaming Hub integration
- **Integration error handling** — validate error handling

## Pre-Production QA

- **QA checklist** — pre-production QA checklist
- **QA validation** — validate all QA checklist items
- **QA testing** — run QA tests before launch
- **QA report** — generate QA report
- **QA approval** — approve QA results for launch
- **QA remediation** — remediate QA failures
- **QA frequency** — QA schedule before launch

## Workflow

### Run Test
1. Select test type (sandbox, tag, integration, QA)
2. Configure test parameters
3. Execute test in sandbox environment
4. Monitor test results
5. Flag test failures
6. Generate test report

### Manage Tests
- **Sandbox campaign management** — create/manage sandbox campaigns
- **Tag testing management** — manage tag tests
- **Integration validation management** — manage integration tests
- **QA management** — manage pre-production QA
- **Test cleanup** — cleanup sandbox after testing
- **Test scheduling** — schedule tests before launch
- **Test reporting** — generate test reports

## Key Metrics
- **Test success rate** — % of tests successful
- **Tag validation pass rate** — % of tags passing validation
- **Integration pass rate** — % of integration validations passing
- **QA pass rate** — % of QA checklist items passing
- **Test error rate** — % of test errors detected
- **Test coverage** — % of test scenarios covered
- **Test efficiency** — time saved vs. manual testing

## Notes
- Test automation should be run before campaign launch
- Tag testing should include all tag variants
- Integration validation should cover all partners
- QA checklist should be comprehensive before launch
- Sandbox cleanup should be completed after testing
- Test reports should be client-ready for review
- Test scheduling should align with launch timeline
- Test automation requires FreeWheel sandbox access
- QA approval required before go-live
- Test coverage should include error scenarios
- Test efficiency should be measured against manual baseline

## Inputs and Boundaries

- Require the account, environment, campaign or integration identifiers, requested operation, date range, and applicable platform specification.
- Default to read-only inspection or sandbox execution. Require explicit approval before production changes, automation writes, DNS changes, inventory changes, or launch actions.
- Validate user-provided URLs, XML, files, identifiers, and configuration before processing.
- Never expose credentials, tokens, client secrets, or unnecessary PII in logs, reports, test fixtures, or generated artifacts.

## Failure Handling

- Record the exact input, environment, operation, timestamp, response, and correlation ID when available.
- Classify failures as malformed input, unsupported format, authentication, permission, dependency, timeout, platform, or verification failure.
- Do not repeat mutations blindly. Check for partial completion and current state before retrying.
- Stop and escalate when a production, security, compliance, delivery, or rollback gate fails.

## Verification

- Confirm every requested item was checked and report pass, fail, or warning per item.
- Read back the authoritative configuration after approved changes.
- Run the relevant sandbox, integration, delivery, playback, routing, or health check.
- Preserve evidence and report assumptions, approvals, unresolved risks, rollback status, and next actions.