# Self-Healing-Test-Pipelines

Traditionelle Test-Suiten brechen, wenn sich die UI ändert. Self-Healing-Tests
nutzen Synapse-Memory, um aus vergangenen Fehlern zu lernen und sich anzupassen —
das reduziert flaky Tests und Wartungsaufwand.

## Konzept

```
┌─────────┐  fails   ┌──────────┐  store   ┌──────────┐
│  Test   │ ───────▶ │  Synapse │ ───────▶ │ Memories │
│  Run    │          │  Memory  │          │ (failures)│
└─────────┘          └──────────┘          └──────────┘
                           ▲                     │
                           │   recall            │
                           │  before next run    │
                           └─────────────────────┘
```

1. Test läuft
2. Bei Fehlschlag: Failure speichern (was schiefging, warum, wie zu beheben)
3. Nächster Lauf: relevante Failures vor der Ausführung abrufen
4. Bekannte Fixes automatisch anwenden

## Implementierung

### Schritt 1: Test-Wrapper

Jeden Test mit Memory-Recall/Store wrappen:

```python
import requests
from datetime import datetime

URL = "https://synapse.schaefer.zone"
MIND_KEY = "mk_..."

def self_healing_test(test_name, test_fn):
    """Decorator: wrap a test with self-healing memory."""
    def wrapper():
        # 1. Recall past failures for this test
        past_failures = requests.get(
            f"{URL}/memory/search?q={test_name}+failure",
            headers={"Authorization": f"Bearer {MIND_KEY}"}
        ).json()
        
        # 2. Run test with failure context
        try:
            test_fn(known_failures=past_failures)
        except Exception as e:
            # 3. Store the failure
            store_failure(test_name, e, traceback.format_exc())
            raise
    
    return wrapper

def store_failure(test_name, error, traceback_str):
    requests.post(f"{URL}/memory",
        headers={"Authorization": f"Bearer {MIND_KEY}",
                 "Content-Type": "application/json"},
        json={
            "category": "mistake",
            "key": f"test_failure_{test_name}_{datetime.now().isoformat()}",
            "content": f"Test: {test_name}\nError: {error}\nTrace:\n{traceback_str}",
            "tags": ["test", "failure", test_name],
            "priority": "high"
        })
```

### Schritt 2: Adaptive Test-Logik

Im Test auf bekannte Failures prüfen und Fixes anwenden:

```python
@self_healing_test
def test_login_page(browser, known_failures=None):
    browser.goto("https://app.com/login")
    
    # Check if we've seen this page change before
    if known_failures and known_failures.get("results"):
        for failure in known_failures["results"]:
            if "button moved" in failure["content"].lower():
                # Use accessibility label instead of coordinates
                browser.click(by_label="Login button")
                return
    
    # Default: use coordinates
    browser.click(x=150, y=400)
```

### Schritt 3: Recovery-Strategien

Recovery-Strategien als Memories speichern:

```python
def store_recovery(failure_type, strategy):
    requests.post(f"{URL}/memory",
        headers={"Authorization": f"Bearer {MIND_KEY}",
                 "Content-Type": "application/json"},
        json={
            "category": "skill",
            "key": f"recovery_{failure_type}",
            "content": strategy,
            "tags": ["test", "recovery", failure_type],
            "priority": "high"
        })

# Store recoveries for common failures
store_recovery("element_not_found",
    "When element not found by ID, try by CSS class, then by XPath, "
    "then by accessibility label. Take screenshot for debugging.")

store_recovery("timeout",
    "Increase timeout to 30s. If still fails, check if page is loading "
    "dynamically — wait for specific element instead of fixed time.")

store_recovery("stale_element",
    "Re-find element before each interaction. Don't cache element references "
    "across page transitions.")
```

### Schritt 4: CI-Integration

```yaml
# .gitlab-ci.yml
test:self-healing:
  script:
    - export SYNAPSE_MIND_KEY=$SYNAPSE_TEST_MIND_KEY
    - pytest tests/ --self-healing
  after_script:
    # Summarize new failures
    - python scripts/synapse_failure_summary.py
```

### Schritt 5: Failure-Analysis-Dashboard

```python
# Get all test failures from the last week
r = requests.get(
    f"{URL}/memory/search?q=test+failure",
    headers={"Authorization": f"Bearer {MIND_KEY}"}
)

# Group by test name
failures = {}
for mem in r.json().get("results", []):
    test_name = extract_test_name(mem["content"])
    failures.setdefault(test_name, []).append(mem)

# Report
for test, fails in sorted(failures.items(), key=lambda x: -len(x[1])):
    print(f"{test}: {len(fails)} failures")
```

## Best Practices

> [!TIP]
> - **Tracebacks speichern** — sie enthalten die exakte Zeile, die fehlgeschlagen ist
> - **Nach Test-Name taggen** — ermöglicht schnelle Filterung
> - **Kategorie `mistake` verwenden** — trennt von regulären Memories
> - **Priorität `high` setzen** — Failures sollten nie vergessen werden
> - **Periodische Bereinigung** — Memories für gelöste Issues löschen
> - **Keine sensiblen Daten speichern** — Credentials, PII

## Häufige Failure-Patterns zum Speichern

| Failure-Typ | Was speichern |
|--------------|---------------|
| Element not found | Versuchter Selector, Page-State, Screenshot |
| Timeout | Wartezeit, worauf gewartet wurde |
| Assertion failed | Erwarteter vs. tatsächlicher Wert |
| Network error | URL, Status-Code, Response-Body |
| Permission denied | Erforderliche Permission, aktuelle Nutzerrolle |

## Nächste Schritte

- [Automatisiertes iOS-Testing](/docs/guides/automated-testing-ios)
- [Memory-Best-Practices](/docs/guides/memory-best-practices)
- [Error-Recovery-Cookbook](/docs/llm-cookbook/error-recovery)