How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

TFK-06-Establish_E2E_Infrastructure - Prompt

Name: TFK-06-Establish_E2E_Infrastructure
Author: FeatureFactory-io

Prompt file imported from FeatureFactory-io/mimir (.windsurf/workflows/Edda/TFK/TFK-06-Establish_E2E_Infrastructure.md). Copyright stays with the author.

Activity: Establish E2E Infrastructure

Activity ID: 192 Order: 6 Phase: Elaboration Dependencies: Predecessor: Activity 191 (Wire CICD Integration) Successor: Activity 193 (Add Step and/or Fixture to Library)

Description

Establish E2E Infrastructure

Guidance

Establish E2E Infrastructure

Objective

Set up the end-to-end test infrastructure that enables "day in life" user journey testing via Playwright-driven browser automation.

Location: tests/e2e/ — standalone suite with its own environment.py, steps/, and *.feature files. Not nested under AT. AT remains in docs/features/ with Django test client steps.

Sequencing contract (why order 6 after #189–#191 is correct)

Chosen resolution (Galdr option c): Activities #189–#191 cover AT concerns only. Activity #192 stands up independent E2E infrastructure. No resequence.

Activity	TFK label	Scope	Needs Playwright / `tests/e2e/` harness?
#188	TFK-02 Bootstrap Test Harness	Creates directory layout for both `docs/features/` (AT) and `tests/e2e/` (E2E placeholders), pytest, `behave.ini`	No — only scaffolds paths
#189	TFK-03 Build Step Library	AT step implementations in `docs/features/steps/` + Step Library Catalog (phrases)	No
#190	TFK-04 Build Fixture Library	Shared fixture data / presets used by AT (and later by E2E data load)	No
#191	TFK-05 Wire CICD Integration	CI gates for unit/integration/`make test-at`	No (E2E stays staging/release-only)
#192	TFK-06 Establish E2E Infrastructure	Playwright + LiveServer + `tests/e2e/environment.py` + journey features	Yes — this activity
#193	TFK-07 Add Step and/or Fixture	Extends catalog; may add AT and/or E2E implementations	As needed

How #189–#191 exist without E2E infrastructure: AT runs via Django test client against docs/features/ (manage.py behave --simple). That path never starts a browser. Fixtures and CI wiring for AT do not call Playwright. Therefore predecessors #189–#191 are valid without #192 being complete.

What #188 already did vs what #192 does: #188 may create empty tests/e2e/ directories and Makefile stubs. #192 makes that suite runnable (browser lifecycle, LiveServer, screenshots, --base-url / --db-uri). Empty dirs ≠ working E2E harness.

Dual-path step maintenance: Catalog phrases are owned by #189 (TFK-03). AT Python lives in docs/features/steps/. E2E Playwright counterparts live in tests/e2e/steps/ and are added when journeys need them (#192 seeds the harness; #193 adds missing phrase implementations). Not one merged module.

Naming: Prefer Activity numeric IDs (#188–#195) in cross-references; TFK-0N labels are workflow abbreviations only.

Clarifications (architecture contract)

Shared catalog, separate implementations. The Step Library Catalog (phrases/vocabulary) is shared between AT and E2E. Python step modules are not shared: AT in docs/features/steps/ (Django test client); E2E in tests/e2e/steps/ (Playwright).
"Same Gherkin phrases" means catalog alignment, not one code tree. Missing phrases → Activity #193 (TFK-07).
No activity reorder. Placement after #191 is intentional: AT stack first, E2E harness second. #192 does not unblock #189–#191.

Key Concepts

E2E vs Acceptance Tests

Aspect	Acceptance Test (AT)	E2E Test
Focus	Proving ONE feature works	Fulfilling a GOAL using system means
Path	`docs/features/`	`tests/e2e/`
Engine	Django test client (`behave --simple`)	Playwright + LiveServer
Scope	Single .feature, single scenario	Multi-phase .feature, sequential
Speed	Fast (no browser)	Slow (real browser, screenshots)
When	Every CI run	Staging before release

Big Idea: Certify Any Environment

Using --base-url=... we can point Playwright at any place where the application runs:

--base-url=http://localhost:8000 — local development
--base-url=https://staging.example.com — staging
--base-url=https://app.example.com — production smoke test

Similarly --db-uri=... points where initial setup has to be loaded.

Process

1. E2E Configuration

make test-e2e BASE_URL=https://staging.example.com DB_URI=postgres://...
# → manage.py behave tests/e2e/

2. E2E Feature Structure

Each E2E test is written as one long multi-phase .feature file under tests/e2e/ running sequentially.

3. Screenshot on Every Step

tests/e2e/environment.py captures a screenshot after every step for visual verification and debugging.

Agent

None

Skill

None

Rules

None

Artifacts Produced

E2E Test Configuration (Code) - Required

Artifacts Consumed

SAO.md § Test Strategy (Document) - Required
Step Library Catalog (Document) - Required
Fixture Library Catalog (Document) - Required

Notes

No additional notes.

Install TFK-06-Establish_E2E_Infrastructure and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Activity: Establish E2E Infrastructure **Activity ID**: 192 **Order**: 6 **Phase**: Elaboration **Dependencies**: Predecessor: Activity 191 (Wire CICD Integration) Successor: Activity 193 (Add Step and/or Fixture to Library) ## Description Establish E2E Infrastructure ## Guidance # Establish E2E Infrastructure ## Objective Set up the end-to-end test infrastructure that enables "day in life" user journey testing via Playwright-driven browser automation. **Location:** `tests/e2e/` — standalone suite with its own `environment.py`, `steps/`, and `*.feature` files. Not nested under AT. AT remains in `docs/features/` with Django test client steps. --- ## Sequencing contract (why order 6 after #189–#191 is correct) **Chosen resolution (Galdr option c):** Activities #189–#191 cover **AT concerns only**. Activity #192 stands up **independent E2E** infrastructure. No resequence. | Activity | TFK label | Scope | Needs Playwright / `tests/e2e/` harness? | |----------|-----------|-------|------------------------------------------| | #188 | TFK-02 Bootstrap Test Harness | Creates **directory layout** for both `docs/features/` (AT) and `tests/e2e/` (E2E placeholders), pytest, `behave.ini` | No — only scaffolds paths | | #189 | TFK-03 Build Step Library | **AT** step implementations in `docs/features/steps/` + Step Library Catalog (phrases) | **No** | | #190 | TFK-04 Build Fixture Library | Shared fixture data / presets used by AT (and later by E2E data load) | **No** | | #191 | TFK-05 Wire CICD Integration | CI gates for unit/integration/`make test-at` | **No** (E2E stays staging/release-only) | | #192 | TFK-06 Establish E2E Infrastructure | Playwright + LiveServer + `tests/e2e/environment.py` + journey features | **Yes — this activity** | | #193 | TFK-07 Add Step and/or Fixture | Extends catalog; may add AT and/or E2E implementations | As needed | **How #189–#191 exist without E2E infrastructure:** AT runs via Django test client against `docs/features/` (`manage.py behave --simple`). That path never starts a browser. Fixtures and CI wiring for AT do not call Playwright. Therefore predecessors #189–#191 are valid without #192 being complete. **What #188 already did vs what #192 does:** #188 may create empty `tests/e2e/` directories and Makefile stubs. #192 makes that suite **runnable** (browser lifecycle, LiveServer, screenshots, `--base-url` / `--db-uri`). Empty dirs ≠ working E2E harness. **Dual-path step maintenance:** Catalog phrases are owned by #189 (TFK-03). AT Python lives in `docs/features/steps/`. E2E Playwright counterparts live in `tests/e2e/steps/` and are added when journeys need them (#192 seeds the harness; #193 adds missing phrase implementations). Not one merged module. **Naming:** Prefer Activity numeric IDs (#188–#195) in cross-references; TFK-0N labels are workflow abbreviations only. --- ## Clarifications (architecture contract) 1. **Shared catalog, separate implementations.** The Step Library Catalog (phrases/vocabulary) is shared between AT and E2E. Python step modules are **not** shared: AT in `docs/features/steps/` (Django test client); E2E in `tests/e2e/steps/` (Playwright). 2. **"Same Gherkin phrases" means catalog alignment, not one code tree.** Missing phrases → Activity #193 (TFK-07). 3. **No activity reorder.** Placement after #191 is intentional: AT stack first, E2E harness second. #192 does not unblock #189–#191. --- ## Key Concepts ### E2E vs Acceptance Tests | Aspect | Acceptance Test (AT) | E2E Test | |--------|---------------------|----------| | Focus | Proving ONE feature works | Fulfilling a GOAL using system means | | Path | `docs/features/` | `tests/e2e/` | | Engine | Django test client (`behave --simple`) | Playwright + LiveServer | | Scope | Single .feature, single scenario | Multi-phase .feature, sequential | | Speed | Fast (no browser) | Slow (real browser, screenshots) | | When | Every CI run | Staging before release | ### Big Idea: Certify Any Environment Using `--base-url=...` we can point Playwright at any place where the application runs: - `--base-url=http://localhost:8000` — local development - `--base-url=https://staging.example.com` — staging - `--base-url=https://app.example.com` — production smoke test Similarly `--db-uri=...` points where initial setup has to be loaded. --- ## Process ### 1. E2E Configuration ```bash make test-e2e BASE_URL=https://staging.example.com DB_URI=postgres://... # → manage.py behave tests/e2e/ ``` ### 2. E2E Feature Structure Each E2E test is written as one long multi-phase `.feature` file under `tests/e2e/` running sequentially. ### 3. Screenshot on Every Step `tests/e2e/environment.py` captures a screenshot after every step for visual verification and debugging. ## Agent None ## Skill None ## Rules None ## Artifacts Produced - **E2E Test Configuration** (Code) - Required ## Artifacts Consumed - **SAO.md § Test Strategy** (Document) - Required - **Step Library Catalog** (Document) - Required - **Fixture Library Catalog** (Document) - Required ## Notes No additional notes.

{ "prompt": "# Activity: Establish E2E Infrastructure\n\n**Activity ID**: 192\n**Order**: 6\n**Phase**: Elaboration\n**Dependencies**: Predecessor: Activity 191 (Wire CICD Integration)\nSuccessor: Activity 193 (Add Step and/or Fixture to Library)\n\n## Description\n\nEstablish E2E Infrastructure\n\n## Guidance\n\n# Establish E2E Infrastructure\n\n## Objective\n\nSet up the end-to-end test infrastructure that enables \"day in life\" user journey testing via Playwright-driven browser automation.\n\n**Location:** `tests/e2e/` — standalone suite with its own `environment.py`, `steps/`, and `*.feature` files. Not nested under AT. AT remains in `docs/features/` with Django test client steps.\n\n---\n\n## Sequencing contract (why order 6 after #189–#191 is correct)\n\n**Chosen resolution (Galdr option c):** Activities #189–#191 cover **AT concerns only**. Activity #192 stands up **independent E2E** infrastructure. No resequence.\n\n| Activity | TFK label | Scope | Needs Playwright / `tests/e2e/` harness? |\n|----------|-----------|-------|------------------------------------------|\n| #188 | TFK-02 Bootstrap Test Harness | Creates **directory layout** for both `docs/features/` (AT) and `tests/e2e/` (E2E placeholders), pytest, `behave.ini` | No — only scaffolds paths |\n| #189 | TFK-03 Build Step Library | **AT** step implementations in `docs/features/steps/` + Step Library Catalog (phrases) | **No** |\n| #190 | TFK-04 Build Fixture Library | Shared fixture data / presets used by AT (and later by E2E data load) | **No** |\n| #191 | TFK-05 Wire CICD Integration | CI gates for unit/integration/`make test-at` | **No** (E2E stays staging/release-only) |\n| #192 | TFK-06 Establish E2E Infrastructure | Playwright + LiveServer + `tests/e2e/environment.py` + journey features | **Yes — this activity** |\n| #193 | TFK-07 Add Step and/or Fixture | Extends catalog; may add AT and/or E2E implementations | As needed |\n\n**How #189–#191 exist without E2E infrastructure:** AT runs via Django test client against `docs/features/` (`manage.py behave --simple`). That path never starts a browser. Fixtures and CI wiring for AT do not call Playwright. Therefore predecessors #189–#191 are valid without #192 being complete.\n\n**What #188 already did vs what #192 does:** #188 may create empty `tests/e2e/` directories and Makefile stubs. #192 makes that suite **runnable** (browser lifecycle, LiveServer, screenshots, `--base-url` / `--db-uri`). Empty dirs ≠ working E2E harness.\n\n**Dual-path step maintenance:** Catalog phrases are owned by #189 (TFK-03). AT Python lives in `docs/features/steps/`. E2E Playwright counterparts live in `tests/e2e/steps/` and are added when journeys need them (#192 seeds the harness; #193 adds missing phrase implementations). Not one merged module.\n\n**Naming:** Prefer Activity numeric IDs (#188–#195) in cross-references; TFK-0N labels are workflow abbreviations only.\n\n---\n\n## Clarifications (architecture contract)\n\n1. **Shared catalog, separate implementations.** The Step Library Catalog (phrases/vocabulary) is shared between AT and E2E. Python step modules are **not** shared: AT in `docs/features/steps/` (Django test client); E2E in `tests/e2e/steps/` (Playwright).\n\n2. **\"Same Gherkin phrases\" means catalog alignment, not one code tree.** Missing phrases → Activity #193 (TFK-07).\n\n3. **No activity reorder.** Placement after #191 is intentional: AT stack first, E2E harness second. #192 does not unblock #189–#191.\n\n---\n\n## Key Concepts\n\n### E2E vs Acceptance Tests\n\n| Aspect | Acceptance Test (AT) | E2E Test |\n|--------|---------------------|----------|\n| Focus | Proving ONE feature works | Fulfilling a GOAL using system means |\n| Path | `docs/features/` | `tests/e2e/` |\n| Engine | Django test client (`behave --simple`) | Playwright + LiveServer |\n| Scope | Single .feature, single scenario | Multi-phase .feature, sequential |\n| Speed | Fast (no browser) | Slow (real browser, screenshots) |\n| When | Every CI run | Staging before release |\n\n### Big Idea: Certify Any Environment\n\nUsing `--base-url=...` we can point Playwright at any place where the application runs:\n- `--base-url=http://localhost:8000` — local development\n- `--base-url=https://staging.example.com` — staging\n- `--base-url=https://app.example.com` — production smoke test\n\nSimilarly `--db-uri=...` points where initial setup has to be loaded.\n\n---\n\n## Process\n\n### 1. E2E Configuration\n\n```bash\nmake test-e2e BASE_URL=https://staging.example.com DB_URI=postgres://...\n# → manage.py behave tests/e2e/\n```\n\n### 2. E2E Feature Structure\n\nEach E2E test is written as one long multi-phase `.feature` file under `tests/e2e/` running sequentially.\n\n### 3. Screenshot on Every Step\n\n`tests/e2e/environment.py` captures a screenshot after every step for visual verification and debugging.\n\n## Agent\n\nNone\n\n## Skill\n\nNone\n\n## Rules\n\nNone\n\n## Artifacts Produced\n\n- **E2E Test Configuration** (Code) - Required\n\n## Artifacts Consumed\n\n- **SAO.md § Test Strategy** (Document) - Required\n- **Step Library Catalog** (Document) - Required\n- **Fixture Library Catalog** (Document) - Required\n\n## Notes\n\nNo additional notes.", "variables": [], "notes": "Establish E2E Infrastructure", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/FeatureFactory-io/mimir", "path": ".windsurf/workflows/Edda/TFK/TFK-06-Establish_E2E_Infrastructure.md", "ref": "d222acb5b4d8ab7b8f48940f8db587e93f425b41", "url": "https://github.com/FeatureFactory-io/mimir/blob/d222acb5b4d8ab7b8f48940f8db587e93f425b41/.windsurf/workflows/Edda/TFK/TFK-06-Establish_E2E_Infrastructure.md", "key": "FeatureFactory-io/mimir/.windsurf/workflows/Edda/TFK/TFK-06-Establish_E2E_Infrastructure.md" } } }

TFK-06-Establish_E2E_Infrastructure

About

Activity: Establish E2E Infrastructure

Description

Guidance

Establish E2E Infrastructure

Objective

Sequencing contract (why order 6 after #189–#191 is correct)

Clarifications (architecture contract)

Key Concepts

E2E vs Acceptance Tests

Big Idea: Certify Any Environment

Process

1. E2E Configuration

2. E2E Feature Structure

3. Screenshot on Every Step

Agent

Skill

Rules

Artifacts Produced

Artifacts Consumed

Notes

Install TFK-06-Establish_E2E_Infrastructure and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews