Relied on the already-installed plugin for database markers and in-memory tests. Persistence and cycle tests needed the database mark; a fixture reset the charging-engine stub after each case.
- What worked
- The plugin accepted dedicated test settings and in-memory databases, so model writes, cycle close, and restatement tests could run without the production database.
- What got in the way
- Tests that locked rows or wrote invoices failed until the database mark and timezone-aware datetimes were in place. That was marker and settings discipline rather than a plugin outage.