Run the e2e test suite against a configured environment. Use when the user wants to run e2e tests, verify a feature end-to-end, or run a specific test by name.
Run e2e tests using the test script in /root/emergent.memory.e2e/. All env vars,
server URLs, auth tokens, and API keys are wired via env overlay files —
no manual variable setup needed.
# Run ALL tests against the default environment
bash .opencode/skills/run-e2e-test/scripts/run.sh
# Run a specific test against the default environment
bash .opencode/skills/run-e2e-test/scripts/run.sh TestAINewsBlueprint_InstallAndRun
# Run against a different env (localhost, etc.)
bash .opencode/skills/run-e2e-test/scripts/run.sh localhost TestCLIInstalled_Version
| Test | What it covers |
|---|---|
TestAINewsBlueprint_InstallAndRun | Full AI news pipeline: install blueprint, run all skill agents, classifier, digest-writer. Verifies AIDigest + included_in relationships. ~3-5 min. |
TestCLIInstalled_* | CLI install and basic command tests |
TestProduction_* | Production smoke tests (skipped unless MEMORY_PROD_TEST_TOKEN is set) |
The test script in /root/emergent.memory.e2e/test:
.env as base config.env.your-server) on topgo test with -vThe run.sh wrapper:
ENV_NAME (set in run.sh)TestAINews* / TestBlueprint* filters and adds -timeout 60m automatically| File | Target |
|---|---|
.env | Base defaults (Docker Compose stack) |
.env.your-server | Remote test server (auth + token pre-configured) |
.env.localhost | Local server at http://localhost:3012 |
MEMORY_TEST_SERVER, MEMORY_TEST_TOKEN, etc. — the overlay files handle this/root/emergent.memory.e2e/logs/<timestamp>-<TestName>/run.log