tatari-qa

tatari-qa

Tatari-specific QA automation plugin for Claude Code. Playwright-powered browser testing for Tatari2 workflows.

Why a Separate Plugin?

This plugin lives outside Conductor because:

• Tatari-specific: Hardcoded to Tatari2 URLs, Okta auth, and internal form structures
• Cross-repo: QA workflows span philo and philo-fe — a single-repo .claude/commands/ file can't reach both
• Conductor stays general: Conductor provides engineering workflow tools usable by any team

Installation

/plugin marketplace add tatari-tv/tatari-qa
/plugin install tatari-qa@tatari-qa

Available Commands

Command	Description
/tatari-qa:campaign-qa <scenario>	Execute YAML-driven campaign creation QA scenarios

Prerequisites

• Claude Code with Playwright MCP server configured
• Local Tatari2 dev environment running
• philo-fe at http://local.tatari.tools:3000

Campaign QA

Run pre-defined campaign creation scenarios against the local Tatari2 campaign form:

/tatari-qa:campaign-qa awareness_cpm_daily_prospecting

Scenario YAML files live in the philo repo at script/qa/campaign_creation/scenarios/. See the setup guide in philo for details.

Supported Scenarios

13 pre-built scenarios across 3 tiers:

• Tier 1 (no extra setup): Awareness + CPM combinations
• Tier 2 (needs conversion events): CPA, CPV, ROAS scenarios
• Tier 3 (needs segment data): Retargeting scenarios

License

MIT