Bamboo Inspect
Easy test management for Playwright and AI-driven tests.
Architecture
Bamboo Inspect uses a Core Manager + Test Agent architecture (similar to GitHub Actions self-hosted runners):
| Component | Core Manager | Test Agent |
|---|---|---|
| Deployment | Docker | pip install bamboo-inspect |
| Role | Manages tests, agents, results | Executes tests |
| Port | 8686 (web dashboard) | 8787 (agent dashboard) |
| Database | PostgreSQL | None |
| Executes tests? | No | Yes |
Multiple Test Agents can connect to one Core Manager.
Quick Start
1. Deploy Core Manager
git clone https://github.com/bamboo-inspect/bamboo-inspect.git
cd bamboo-inspect
make docker-dev
# Dashboard at http://localhost:8686
2. Install & Register Test Agent
pip install bamboo-inspect
# Generate a token from the Core Manager dashboard, then:
bambooinspect agent register \
--url http://localhost:8686 \
--token <registration-token> \
--name my-agent \
--labels linux,playwright
bambooinspect agent start
# Agent dashboard at http://localhost:8787
3. Sync a Repo & Assign Tests
# Agent scans a local git repo and pushes test structure to Core Manager
cd ~/my-project
bambooinspect agent sync-repo .
Then use the Core Manager dashboard to:
- Select tests and assign them to an agent (Tests → Assign to Agent)
- Monitor results in the Tasks tab
Stateless CLI (no Core Manager needed)
cd ~/my-project
bambooinspect run-all --type script
bambooinspect run-module auth --type script
bambooinspect run login_test --type script
Test Structure
Monitored repositories must follow this structure:
my-project/
tests/
scripts/ # Playwright tests
auth/
login_test.py
checkout/
cart_test.js
prompts/ # AI prompts (Claude Code)
auth/
test_login.prompt
License
MIT
Metadata
Release files for bamboo-inspect 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| bamboo_inspect-1.0.0.tar.gz | 311.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bamboo_inspect-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 349.5 kB
Release files / bamboo_inspect-1.0.0.tar.gz
| Download URL | bamboo_inspect-1.0.0.tar.gz |
|---|---|
| Size | 311.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
894e108e8f4899bc728c3f5cfc2828a1fff6dd70e330b6226b1cc422e42ebbbe
|
|
BLAKE2b-256 checksum How to use checksums |
17383b960eeb1d15ad35c5c607ea0bb848187041a9cbf0e2e26a5905e6c23378
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / bamboo_inspect-1.0.0-py3-none-any.whl
| Download URL | bamboo_inspect-1.0.0-py3-none-any.whl |
|---|---|
| Size | 38.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1405447f8704f604957e620f6a1da09e1e655794c1a61ec00adbfe891206577
|
|
BLAKE2b-256 checksum How to use checksums |
699be9a2a80c23801693a44c60ff137792d5a2bca7bd5ee4b3f4fac82dbc6058
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for bamboo-inspect 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.