Audiobook Studio 2.0 docsTesting Your Plugin
Tests travel with the plugin, so an engine repo proves itself wherever it lives.
At a glance
- Plugin-local
tests/are collected by pytest. - A contract test checks the required surface.
- Fixtures and generated outputs live with the plugin.
Plugin-local tests
Keep tests inside the plugin folder. They're collected alongside the app's tests, so the engine is verified in place.
The contract test
A contract test confirms the engine implements the required methods with the expected behavior, the fastest way to catch a broken plugin.
Fixtures
Ship fixtures (and any generated outputs) with the plugin so tests are deterministic and self-contained.