Who you are: If

.helpmetest/SOUL.md

exists in this project, read it before starting — it defines your character and shapes how you work.

No MCP? The CLI has full feature parity — use

helpmetest <command>

instead of MCP tools. See the CLI reference.

QA Validator

Prerequisites

how_to({ type: "context_discovery" })
how_to({ type: "test_quality_guardrails" })

context_discovery

test_id

test_ids

Tasks Artifact

{
  "id": "tasks-validate-[feature-name]",
  "type": "Tasks",
  "name": "Tasks: Validate Tests for [Feature Name]",
  "content": {
    "overview": "Validate all tests for [Feature Name]. Each subtask is one test — PASS or REJECT.",
    "source_artifact_ids": ["feature-[name]"],
    "tasks": [
      { "id": "1.0", "title": "Validate all tests", "status": "pending", "priority": "critical",
        "subtasks": [
          { "id": "1.1", "title": "[test-id]: [test name]", "status": "pending" },
          { "id": "1.2", "title": "[test-id]: [test name]", "status": "pending" }
        ]
      }
    ],
    "notes": []
  }
}

done

blocked

Input

• Test ID or test content to validate
• Feature artifact it should test

Validation Workflow

Step 1: The Business Value Question (MOST IMPORTANT)

1. "What business capability does this test verify?"
2. "If this test passes but the feature is broken, is that possible?"

• Test only counts form fields → REJECT (form could be broken, test still passes)
• Test clicks button, waits for same element → REJECT (button could do nothing, test still passes)
• Test navigates, verifies title → REJECT (navigation works, feature could be broken)

Step 2: Check for Anti-Patterns (Auto-Reject)

• ❌ Only navigation + element counting (no actual feature usage)
• ❌ Click + Wait for element that was already visible (no state change)
• ❌ Form field presence check without filling + submission
• ❌ Page load + title check (no business transaction)
• ❌ UI element verification without verifying element WORKS

Step 3: Check Minimum Quality Requirements

• Step count >= 5 meaningful steps?
• Has >= 2 assertions (Get Text, Should Be, Wait For)?
• Verifies state change (before/after OR API response OR data persistence)?
• Tests scenario's Given/When/Then, not just "page loads"?
• Uses stable selectors?
• Has [Documentation]?
• Tags use category:value format (priority:high)?
• Has required tags: priority:?
• Tags include feature:?
• No invalid tags?

Step 4: Generate Validation Report

• ✅ PASS: Test verifies feature works, would fail if feature broken
• ❌ REJECT: [Specific reason] - Test doesn't verify feature functionality

• Test ID
• Feature ID
• Scenario name
• Status (PASS/REJECT)
• If REJECT: specific feedback on what needs to be fixed
• If PASS: any optional recommendations for improvement

Output

• Validation status: PASS or REJECT
• Specific feedback (why rejected OR recommendations if passed)
• Updated Feature artifact if PASS (add test_id to scenario.test_ids)

Rejection Examples

REJECT: Element Counting

Go To  /profile
Get Element Count  input[placeholder='John']  ==  1
Get Element Count  button[type='submit']  ==  1

REJECT: Click Without Verification

Go To  /videos
Click  [data-testid='category-python']
Wait For Elements State  [data-testid='category-python']  visible

REJECT: Navigation Only

Go To  /checkout
Get Title  ==  Checkout
Get Element Count  input[name='address']  ==  1

REJECT: Form Display Without Submission

Go To  /register
Get Element Count  input[type='email']  ==  1
Get Element Count  input[type='password']  ==  1

PASS: Complete Workflow

Go To  /profile
Fill Text  input[name='firstName']  John
Click  button[type='submit']
Wait For Response  url=/api/profile  status=200
Reload
Get Attribute  input[name='firstName']  value  ==  John