daa-core

Declarative Action Architecture (DAA) — Core Principles

What is DAA

DAA is a strict three-layer separation pattern for E2E automation testing. It enforces that tests are declarative, actions are self-verifying, and physical interactions are pure execution — eliminating false positives and maximizing maintainability.

The Three Layers

Layer 1: Test Layer (The "What")

The Test Layer is 100% declarative. It describes WHAT the user is doing, not HOW.

Iron Rules:

• ZERO logic: No if, no for, no while, no try/catch
• ZERO direct system calls: No raw HTTP requests, no WebDriver calls, no database queries
• ZERO assertions: All verification lives in the Action Layer
• Tests read like plain-English documentation — a Product Manager should understand them

// GOOD — Pure declarative
test_user_checkout_journey():
    navigate_to_home_and_verify_title()
    search_for_product_and_verify_results_not_empty("iPhone 15")
    add_first_result_to_cart_and_verify_toast()

// BAD — Logic leaked into test
test_user_checkout_journey():
    page.goto(URL)
    if page.title() != "Home":
        raise Error("Wrong page")
    page.fill("#search", "iPhone 15")
    page.click("#submit")
    results = page.query_all(".result")
    assert len(results) > 0

Layer 2: Action Layer (The "How" + Verification)

This is the heart of DAA. It translates declarative test steps into execution + verification.

Iron Rules:

1. Self-Verification Mandate: Every action method MUST verify its own success. You never just "click button"; you "click button and verify modal opens." This eliminates false positives.
2. No Direct System Access: Delegates all system interaction to the Physical Layer.
3. Compose, Don't Repeat: Build complex workflows by composing smaller actions.

Action Hierarchy

Level	Type	Description	Example
Level 1	Atomic Action	Single operation + self-verify	create_user_and_verify()
Level 2	Composite Action	Business workflow = multiple Atomics	perform_device_upgrade()