daa-generate

DAA Code Generator

REQUIRED BACKGROUND: You MUST understand daa:daa-core before using this skill.

Overview

When generating E2E test automation code, follow the Declarative Action Architecture strictly. Every piece of code you write belongs to exactly ONE of the three layers, and must follow that layer's rules.

Generation Process

digraph generation {
    rankdir=TB;
    "Identify target layer" [shape=box];
    "Read layer-specific rules" [shape=box];
    "Generate code" [shape=box];
    "Run pre-output checklist" [shape=diamond];
    "Output code" [shape=doublecircle];
    "Fix violations" [shape=box];

    "Identify target layer" -> "Read layer-specific rules";
    "Read layer-specific rules" -> "Generate code";
    "Generate code" -> "Run pre-output checklist";
    "Run pre-output checklist" -> "Output code" [label="all pass"];
    "Run pre-output checklist" -> "Fix violations" [label="violation found"];
    "Fix violations" -> "Run pre-output checklist";
}

Quick Rules Per Layer

Test Layer

• ZERO logic: No if, for, while, try/catch
• ZERO assertions: All verification is inside Action methods
• ZERO direct calls: No HTTP requests, no WebDriver, no database
• Test methods call ONLY Action Layer methods
• Test class inherits from or composes the Action Layer

// Test Layer — pure declarative
test_guest_checkout_journey():
    navigate_to_home_and_verify_title()
    search_for_product_and_verify_results_not_empty("MacBook Air")
    add_first_result_to_cart_and_verify_toast()
    navigate_to_cart_and_verify_page()
    click_checkout_and_verify_login_prompt()

→ Full generation rules: test-layer.md

Action Layer

• Every method MUST self-verify (built-in assertion)
• Delegates system interaction to Physical Layer — no direct calls
• Atomic Actions (Level 1): single operation + verify
• Composite Actions (Level 2): orchestrate multiple Atomics
• Use semantic long names: verb_object_and_verify_outcome