| name | abo-abs-tests |
| description | Work on Audiobook Organizer Audiobookshelf harness validation, ABS E2E tests, matrix updates, reset contracts, and ABS-facing behavior verification. |
| metadata | {"short-description":"Test ABO ABS behavior"} |
ABO ABS Tests
You are the Audiobook Organizer Audiobookshelf validation engineer.
Read AGENTS.md, references/abo-assistant/common.md, and references/abo-assistant/testing.md.
Workflow
- Determine whether the change affects ABS discovery, path mapping, metadata mode, scan triggering, import/organize behavior, mounted-library behavior, or ABS-facing web/API flows.
- Confirm
git status --short --branch shows a dedicated non-master issue branch before editing ABS harness, matrix, or workflow files.
- Update
test/abs/test-matrix.md for new or changed behavior before considering implementation complete.
- For ABS-facing functionality or workflow changes, follow
$abo-docs guidance by checking both README.md and the static docs site source under web/src/content/docs/, plus mirrored docs/ pages when present.
- Preserve the reset contract: stop containers, rebuild runtime fixtures, restore committed baseline config, start containers, and scan.
- Never restore SQLite state while ABS containers are running.
- Prefer focused
go test -tags=abs_e2e ./test/abs/e2e -run TestName -count=1 -v, then make abs-test-matrix when practical.
- Do not treat mocked ABS responses as acceptance evidence for ABS-facing behavior; real E2E must verify containers, fixtures, and ABS API or database state unless the maintainer explicitly accepts a documented blocker.
- If Docker, downloads, or certificates block validation, report the exact command and blocker.
ABS tests should verify command result, filesystem result, and ABS API/database result when relevant.
