Automated summary
A comprehensive guide for testing Orient releases, covering unit tests, installer E2E tests, CLI verification, integration tests, eval tests, and success criteria validation.
Strengths
- Systematic approach with clear phases and expected results.
- Includes a quick test for rapid checks.
- Provides troubleshooting and cleanup steps.
- Defines success criteria with specific numeric thresholds.
Limitations
- Requires environment setup (Node 20+, pnpm, PM2, Docker optionally).
- Eval tests have known issues with OpenCode agent routing.
- Some tests may fail due to environment (e.g., Docker not running).
When preparing a new version of Orient for release and need to validate installation, functionality, and test coverage.
For routine development testing or when not working on an Orient release.
Security analysis
SafeThe skill only runs local development tests and health checks; it uses standard tools (pnpm, curl, sqlite3) on local resources, does not exfiltrate data, and includes no destructive or obfuscated commands. The ANTHROPIC_API_KEY is used locally and never transmitted externally.
No concerns found
How this analysis is madeExamples
Run quick release tests for Orient v0.5.0Test the new Orient release candidate thoroughlyRun installer E2E tests for Orient releasename: release-testing description: Comprehensive guide for testing Orient releases. Use this skill when asked to "test the release", "verify installation", "run release tests", "check v0.x.x", "validate installer", or when preparing a new version for release. Covers unit tests, installer E2E tests, CLI verification, integration tests, eval tests, and success criteria validation.
Orient Release Testing
Test releases systematically before shipping.
Quick Test (5 min)
pnpm test:unit # Should pass 240+ tests
orient doctor && orient status # If installed
curl -s http://localhost:4098/health
Full Release Testing Sequence
Phase 1: Unit Tests
pnpm test:unit
Expected: ~244 passed, ~33 skipped Acceptable: Docker tests may fail if Docker isn't running (environment issue, not code bug)
Phase 2: Local Installer E2E
./installer/install-local.sh
This will:
- Check prerequisites (Node 20+, pnpm, PM2)
- Clean and rebuild all packages
- Copy to
~/.orient/ - Initialize SQLite database
- Start services via PM2
- Open dashboard
Phase 3: Verify Installation
# Load into current shell
export ORIENT_HOME="$HOME/.orient"
export PATH="$ORIENT_HOME/bin:$PATH"
# Run all checks
orient doctor # All services should show online
orient status # PM2 status table
orient version # Should show correct version
orient logs --lines 5 --nostream # Should show recent logs
# HTTP checks
curl -s http://localhost:4098/health | jq . # {"status":"ok"}
curl -s -o /dev/null -w "%{http_code}" http://localhost:4098/ # 200
curl -s -o /dev/null -w "%{http_code}" http://localhost:4098/qr/ # 200
# Database verification
ls -la ~/.orient/data/sqlite/
sqlite3 ~/.orient/data/sqlite/orient.db ".tables" # Should list 30+ tables
Phase 4: Integration Tests
./run.sh dev start
sleep 60 # Wait for services
INTEGRATION_TESTS=true pnpm test:integration
./run.sh dev stop
Expected: ~43 tests passing
Phase 5: Eval Tests
# Without API key (graceful skip)
pnpm test:eval # Should pass with skip message
# With dev server running (full eval infrastructure test)
./run.sh dev start
ANTHROPIC_API_KEY=xxx pnpm test:eval
./run.sh dev stop
Requirements:
ANTHROPIC_API_KEYenvironment variable- Dev server running (
./run.sh dev start) for OpenCode at localhost:4099
Known Limitation: The eval/OpenCode agent routing integration needs work. The eval infrastructure (loading, filtering, running) works correctly, but actual agent invocations through OpenCode may fail with session errors. Test will pass while logging a warning about this.
Success Criteria
| Check | Pass | Fail |
| ----------------- | ----------------- | -------------------------------- |
| Unit tests | 230+ passed | <200 passed or critical failures |
| Integration tests | 40+ passed | <35 passed |
| Services start | PM2 shows online | errored/stopped status |
| Health endpoint | {"status":"ok"} | Connection refused or error |
| Dashboard HTTP | 200 | 4xx/5xx |
| QR endpoint HTTP | 200 | 4xx/5xx |
| Database | 30+ tables | Missing tables or errors |
| orient doctor | All green | Red status |
| CLI commands | All work | Any command fails |
Cleanup
# Stop services
orient stop
# Full uninstall
orient uninstall --force
# Or manual cleanup
pm2 delete orient
rm -rf ~/.orient
Troubleshooting
Port 4098 in use: lsof -i :4098 then kill <PID>
PM2 not starting: Check logs with pm2 logs orient --lines 50
Database errors: Delete and reinitialize:
rm ~/.orient/data/sqlite/orient.db*
cd ~/.orient/orient && pnpm --filter @orientbot/database run db:push:sqlite
Build failures: Clean rebuild:
find packages -name "dist" -type d -maxdepth 2 -exec rm -rf {} +
rm -rf .turbo node_modules/.cache
pnpm install && pnpm run build:all
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/orient-release-testing-mmk3nh3h/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/orient-release-testing-mmk3nh3h' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/orient-release-testing-mmk3nh3h/download' --output '.skill-downloads/orient-release-testing-mmk3nh3h/SKILL.md.part' && mv '.skill-downloads/orient-release-testing-mmk3nh3h/SKILL.md.part' '.skill-downloads/orient-release-testing-mmk3nh3h/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/orient-release-testing-mmk3nh3h/SKILL.md' && test -s '.skill-downloads/orient-release-testing-mmk3nh3h/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/release-testing' && cp -R '.skill-downloads/orient-release-testing-mmk3nh3h' '.claude/skills/release-testing'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/orient-release-testing-mmk3nh3h'openskills read 'orient-release-testing-mmk3nh3h'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/orient-release-testing-mmk3nh3h/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.