Verification and Smoke Tests

Purpose

Verification proves that a change actually works in the current Amvionlie build.

Minimum checks

For PHP changes:

• lint every changed PHP file
• run the addon smoke test when one exists
• verify relevant admin/public URLs return HTTP 200

UI checks

When changing admin UI, check that the screen uses the central admin shell, shared list helpers, CSRF, permission checks, notices, pagination, and row actions correctly.

When changing frontend UI, check the public route, template safety, access behavior, and public target metadata where applicable.

Smoke tests

Smoke tests should assert the addon contract, not just that a function exists. A useful smoke test checks schema readiness, route registration, permission declarations, rendering markers, and critical behavior.

What to report

Report what passed, what failed, and what was not run. Do not imply a check passed if it was skipped.

Good habit

If a change touches integration, verify the neighbors too. A route that works by breaking the catalog is not a win; it is a trade nobody approved.