# Self-Healing Test Pipelines Traditional test suites break when the UI changes. Self-healing tests use Synapse memory to learn from past failures and adapt — reducing flaky tests and maintenance burden. ## Concept ``` ┌─────────┐ fails ┌──────────┐ store ┌──────────┐ │ Test │ ───────▶ │ Synapse │ ───────▶ │ Memories │ │ Run │ │ Memory │ │ (failures)│ └─────────┘ └──────────┘ └──────────┘ ▲ │ │ recall │ │ before next run │ └─────────────────────┘ ``` 1. Test runs 2. If it fails, store the failure (what went wrong, why, how to fix) 3. Next run: recall relevant failures before executing 4. Apply known fixes automatically ## Implementation ### Step 1: Test Wrapper Wrap each test with memory recall/store: ```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" }) ``` ### Step 2: Adaptive Test Logic Inside the test, check for known failures and apply fixes: ```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) ``` ### Step 3: Recovery Strategies Store recovery strategies as memories: ```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.") ``` ### Step 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 ``` ### Step 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] > - **Store tracebacks** — they contain the exact line that failed > - **Tag by test name** — enables fast filtering > - **Use `mistake` category** — separates from regular memories > - **Set `high` priority** — failures should never be forgotten > - **Periodic cleanup** — delete memories for resolved issues > - **Don't store sensitive data** — credentials, PII ## Common Failure Patterns to Store | Failure Type | What to Store | |--------------|---------------| | Element not found | Selector tried, page state, screenshot | | Timeout | Wait time, what was being waited for | | Assertion failed | Expected vs actual value | | Network error | URL, status code, response body | | Permission denied | Required permission, current user role | ## Next Steps - [Automated iOS Testing](/docs/guides/automated-testing-ios) - [Memory Best Practices](/docs/guides/memory-best-practices) - [Error Recovery Cookbook](/docs/llm-cookbook/error-recovery)