القائمة
Use when running integration tests in the mobster repository — requires docker compose, tests OCI registry interactions, cosign, syft, and TPA upload flows
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when checking formatting, linting, type errors, or security issues in the mobster repository — ruff, pylint, mypy, bandit, yamllint, pip-audit
Use when preparing a new release of mobster — release-please, version bump, GitHub release, PyPI, container image
Use when running, filtering, debugging, or adding unit tests in the mobster repository — tox, pytest, coverage
Use when writing, updating, or adding documentation for mobster commands, features, or developer internals — covers file placement and mkdocs.yml nav rules
| name | run-integration-tests |
| description | Use when running integration tests in the mobster repository — requires docker compose, tests OCI registry interactions, cosign, syft, and TPA upload flows |
Integration tests require a running local registry and supporting services:
docker compose up -d
Check services are healthy before running tests:
docker compose ps
tox -e test-integration # all integration tests
tox -e test-integration -- -k name # single test by name
tox -e test-integration -- -v # verbose output
oras)cosign signature verification flowssyft SBOM generation against real imagesThese tests are excluded from unit test runs and coverage gates — they verify end-to-end flows, not individual functions.
docker compose down
docker compose up -d first — tests will fail with connection errors, not a helpful messagetox -e test expecting integration tests to be included — they are not; use tox -e test-integration