blaxel-ai/run-e2e
.agents/skills/run-e2e/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add blaxel-ai/sandbox run-e2eInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 9:02 PM1.8s1 file scanned
SKILL.md
- 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.
Run End-to-End 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.
Architecture
- Custom sandbox:
e2e/custom-sandbox/— a Docker image that embeds the fullsandbox-apisource and builds it at image-build time - Simple custom sandbox:
e2e/simple-custom-sandbox/— a leaner image that takes a pre-compiled binary - Test scripts:
e2e/scripts/— Node.js tests run withnpm run test:local
Option 1: Full Local E2E (Build + Run + Test)
make e2e
This single command:
- Removes any existing
sandbox-devcontainer - Builds the custom sandbox image (
make build-custom-sandbox) - Starts the container (
make run-custom-sandbox) on ports 8080-8083 - Waits 5 seconds for startup
- Logs open file descriptors (leak detection)
- Runs the e2e test suite (
make test-custom-sandbox) - Logs file descriptors again after tests
Note: Watches for file descriptor leaks — the count before and after tests should not grow significantly.
Option 2: Step-by-Step
Build the Custom Sandbox Image
make build-custom-sandbox
Copies sandbox-api/ into e2e/custom-sandbox/ and builds custom-sandbox:latest.
Run It Locally
make run-custom-sandbox
Starts custom-sandbox:latest as sandbox-dev container with ports 8080-8083 exposed.
Run Tests Against It
make test-custom-sandbox
Runs e2e/scripts/npm run test:local against the running container.
Option 3: Deploy to Blaxel and Test
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
Option 4: Simple Custom Sandbox (Pre-Compiled Binary)
Compile for Linux first, then deploy:
make deploy-simple-custom-sandbox
This:
- Cross-compiles
sandbox-apiforlinux/amd64 - Copies the binary to
e2e/simple-custom-sandbox/ - Deploys to Blaxel with
bl deploy - Cleans up the binary
Useful for faster iteration when you don't need to rebuild the full Docker image.
Troubleshooting
- Build fails: Check
sandbox-api/compiles cleanly first withmake test - Container exits immediately: Run
docker logs sandbox-devto see the error - Tests fail with connection refused: Container may still be starting; increase the sleep or poll
/health - File descriptor count grows: There is a resource leak in the code path being tested — investigate with
lsof -p <pid>inside the container blcommand not found: Install the Blaxel CLI (brew install blaxel-ai/tap/blor equivalent)
Related Skills
blaxel-ai/update-api-reference
development
VerifiedTrustedCommunity
Regenerate the OpenAPI reference documentation after adding, modifying, or removing API endpoints in sandbox-api. Run this whenever handler signatures, route paths, or swag annotations change.
15SKILL.mdUpdated Apr 17, 2026
blaxel-ai/run-integration-tests
development
VerifiedTrustedCommunity
Run the sandbox-api integration tests against a live API instance. Use after making changes to sandbox-api to verify all endpoints still work correctly.
15SKILL.mdUpdated Apr 17, 2026
blaxel-ai/playwright-e2e
testing
VerifiedTrustedCommunity
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.
15SKILL.mdUpdated Apr 17, 2026
blaxel-ai/dev-environment
development
VerifiedTrustedCommunity
Start the local sandbox-api development environment with hot-reload. Use when developing or testing changes to the sandbox-api Go code locally.
15SKILL.mdUpdated Apr 17, 2026