Investment Plans workspace
Open raw ↗

Dispatch for test_writer_track_1

Mission

Design and implement the comprehensive E2E test suite in 05_Test/ following the 4-tier methodology (Tiers 1-4) plus programmatic verification script per ORIGINAL_REQUEST.md and PROJECT.md. When finished, publish TEST_INFRA.md and TEST_READY.md.

Exclusive Write Ownership

You own exclusively:

Do NOT edit any files in MVP/ or 04_Build/.

Mandatory Reading

Deliverables Required

  1. 05_Test/verify_mvp.py:
    • Self-contained CLI verification script using Python standard library (no external test dependencies).
    • Dual-mode: supports --source (launches MVP/app.py on ephemeral port) and --exe (launches standalone executable on ephemeral port).
    • Tests:

a. Launch application & health ping. b. Verify unauthenticated access rejection. c. Patient login (patient.durand / demo123). d. Submit patient toxicity report to SQLite. e. Direct SQLite persistence query verifying insertion in toxicity_reports. f. Clinician login (dr.martin / demo123). g. Clinician care timeline verification confirming patient's submitted report is visible. h. Clean process termination.

  • Returns exit code 0 on all tests pass, non-zero on failure.
    1. 05_Test/test_e2e_tier1.py:
      • Feature coverage tests (>=5 tests per feature for core features: auth, reporting, CTCAE grading, alerts, timeline).
    1. 05_Test/test_e2e_tier2.py:
      • Boundary value analysis (empty payloads, boundary CTCAE scores 0, 1, 5, 6, string values, account lockout 5 fails).
    1. 05_Test/test_e2e_tier3.py:
      • Cross-feature combinations (patient report -> alert generation -> nurse acknowledge -> oncologist grade confirmation -> timeline update).
    1. 05_Test/test_e2e_tier4.py:
      • Real-world clinical application scenarios (multi-patient home hospitalization cycle, clinician observation vs patient self-report).
    1. 05_Test/test_e2e_tier5_adversarial.py:
      • Security hardening & adversarial tests (path traversal attack, brute-force lockout, rapid concurrent requests).
    1. TEST_INFRA.md and TEST_READY.md:
      • Documenting test runner command, test breakdown, and feature coverage checklist.

    Verification

    Run tests using Python test tools (e.g. python 05_Test/verify_mvp.py --source or pytest 05_Test/). Record all outputs in your handoff report: c:\AI Projects\Kais Project\.agents\test_writer_track_1\handoff.md.

    2026-09-05T10:39:30Z

    You are test_writer_track_1. Your working directory is: c:\AI Projects\Kais Project\.agents\test_writer_track_1 Your dispatch instructions are at: c:\AI Projects\Kais Project\.agents\test_writer_track_1\DISPATCH.md Read c:\AI Projects\Kais Project\ORIGINAL_REQUEST.md first. MANDATORY: Read ORIGINAL_REQUEST.md, .agents/orchestrator_1/PROJECT.md, and the explorer handoff reports. Your task is to build the comprehensive E2E test suite in 05_Test/ (verify_mvp.py, test_e2e_tier1.py, test_e2e_tier2.py, test_e2e_tier3.py, test_e2e_tier4.py, test_e2e_tier5_adversarial.py) and generate TEST_INFRA.md and TEST_READY.md at project root. Execute and verify the tests against Python server. Write your completion handoff report to: c:\AI Projects\Kais Project\.agents\test_writer_track_1\handoff.md Send a completion message back when done.