메뉴
Run the full end-to-end test suite against a custom sandbox image deployed locally or on Blaxel. Use before merging significant changes to validate the complete sandbox-api binary, not just unit/integration tests.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Add or update a Blaxel Sandbox Hub image/template under hub/. Use when adding a new hub image, sandbox image, runtime image, template.json, Dockerfile, hidden/internal image, or workflow-dispatch build option in the blaxel-ai/sandbox repository.
Deploy a Playwright sandbox (chromium or firefox) on Blaxel and run e2e tests against it. Use to validate that playwright hub images work end-to-end (browser connection, page navigation, DOM interaction) after changes.
Poll CI status on a branch until the "Build and Push Sandbox" workflow completes. Use after pushing to develop or any branch where you need to confirm the build succeeded before proceeding.
Watch CI until the "Build and Push Sandbox" workflow completes. For dev deployments, watches the develop branch. For prod deployments, watches the latest tag. Use after merging into develop or pushing a release tag.
Deploy the app to the dev environment. Use after a PR is marked as reviewable (ready for review) so reviewers can check out the changes running in dev.
Start the local sandbox-api development environment with hot-reload. Use when developing or testing changes to the sandbox-api Go code locally.
| name | run-e2e |
| description | Run the full end-to-end test suite against a custom sandbox image deployed locally or on Blaxel. Use before merging significant changes to validate the complete sandbox-api binary, not just unit/integration tests. |
E2E tests build a real Docker image from the current source, deploy it, and run the test suite against it. This validates the full binary, not just the in-process unit tests.
e2e/custom-sandbox/ — a Docker image that embeds the full sandbox-api source and builds it at image-build timee2e/simple-custom-sandbox/ — a leaner image that takes a pre-compiled binarye2e/scripts/ — Node.js tests run with npm run test:localmake e2e
This single command:
sandbox-dev containermake build-custom-sandbox)make run-custom-sandbox) on ports 8080-8083make test-custom-sandbox)Note: Watches for file descriptor leaks — the count before and after tests should not grow significantly.
make build-custom-sandbox
Copies sandbox-api/ into e2e/custom-sandbox/ and builds custom-sandbox:latest.
make run-custom-sandbox
Starts custom-sandbox:latest as sandbox-dev container with ports 8080-8083 exposed.
make test-custom-sandbox
Runs e2e/scripts/npm run test:local against the running container.
Deploy the custom sandbox to the Blaxel platform, wait for it to be DEPLOYED, then run tests:
make deploy-custom-sandbox
Then wait and test:
# This waits until status=DEPLOYED, then runs tests
# (embedded in make test-custom-sandbox)
make test-custom-sandbox
Compile for Linux first, then deploy:
make deploy-simple-custom-sandbox
This:
sandbox-api for linux/amd64e2e/simple-custom-sandbox/bl deployUseful for faster iteration when you don't need to rebuild the full Docker image.
sandbox-api/ compiles cleanly first with make testdocker logs sandbox-dev to see the error/healthlsof -p <pid> inside the containerbl command not found: Install the Blaxel CLI (brew install blaxel-ai/tap/bl or equivalent)