0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-08 19:56:53 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 b40aa731fb fix(workspace): resolve the stack URLs when a step needs them, not on source

769163ca7 computed DASHBOARD_URL and MATOMO_URL from INFINITO_DOMAIN
right after load_repo_env in common.sh. The orchestrator sources
common.sh inside the bare runtime image before Python is installed,
where load_repo_env returns without loading the env, so the guard
aborted the debian, ubuntu and fedora workspace jobs before their first
step.

common.sh now offers stack_url, which reads INFINITO_DOMAIN when it is
called. The compose steps resolve their URLs in plain assignments after
their own source of common.sh, so a missing domain still aborts the step
instead of handing an empty URL to an assertion that expects 000.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-22 00:11:38 +02:00

code

perf(test): pay a class fixture once instead of once per xdist worker

2026-09-19 07:46:18 +02:00

deploy

feat(swarm): let the local loop drive the architecture axis

2026-09-19 11:57:03 +02:00

dns

perf(ci): stream the DNS run per distro instead of replaying it

2026-09-16 22:04:28 +02:00

e2e

fix(e2e): derive the shared Playwright helpers instead of listing them

2026-08-29 10:45:20 +02:00

install

ci: keep one install test, the one that matches how images are built

2026-09-21 10:25:30 +02:00

unit

feat(test): report the javascript, php and ruby suites in the CI summary

2026-08-22 22:27:12 +02:00

workspace

fix(workspace): resolve the stack URLs when a step needs them, not on source

2026-09-22 00:11:38 +02:00

dns.sh

…

README.md

…

README.md

Test Utilities 🧪

This directory holds the operational side of testing in Infinito.Nexus.

These assets are meant to support confidence, not ceremony. They help the project validate real-world behavior across local development, CI environments, and deployment-oriented smoke tests. The emphasis is on practical feedback: when something breaks, the surrounding test tooling should make the failure easier to understand, easier to reproduce, and easier to clean up. 🚀

Good changes in this area usually make the test experience more:

repeatable
diagnosable
environment-aware
safe to rerun

The ideal outcome is boring reliability: contributors should be able to trust that a test run says something meaningful about the system, not just about the machine that happened to execute it. ✅