Testing

Honest status of framework vs business-addon tests and practical manual checks.

What exists today

Core ships unit and smoke tests under sumeru/test/ (ORM, API, web, viewinherit, ...). Business addons and custom modules often lack automated coverage. Treat manual checks as required in pre-alpha.

Running core tests

$cd sumeru$go test ./...

Integration tests (PostgreSQL)

Start a disposable database and run tagged integration tests:

$cd sumeru$make test-db$make test-integration

Requires Docker. Tests live under test/integration/ with build tag integration.

Practical checklist for an addon

• Install with -i and confirm no loader errors.
• Open tree/form/kanban for the model; create and edit a row.
• Log in as a user in the restricted group. Confirm read-only ACL.
• GET /api/health and a search_read with an API key.
• Run -u after XML edits and confirm menus still resolve.

Compile and run

$cd sumeru && go test ./...$cd ../sumeru_custom_addons && make run

What not to do

• Do not claim production readiness based on green core unit tests alone.
• Do not skip ACL checks when your CSV grants write to a broad group.
• Do not ignore schema-sync failures on update. Fix FieldDefinition mismatches.

Next step

Plan a host in Deployment.

Sumeru is pre-alpha (no tagged release, no upgrades). Part of Project Meru.