#116: DataTransferAuditDaoTest.kt

Integration test for DataTransferAuditDao — verifies the audit log DAO's queue management, notification tracking, and entry retrieval. Extends AbstractTestBase with Spring autowired DAOs and recreateDataBase() for test isolation.

Test methods (from source analysis)

• removeFromQueueTest() — creates audit entries with different timestamps, verifies internalGetEntriesByAreaId() returns all 3, then tests queue retrieval logic: entries older than a threshold should be eligible for notification, recent entries should remain queued
• Tests use PFDateTime.now().minus(D, ChronoUnit.DAYS/MINUTES) to simulate time-shifted audit entries
• internalGetQueuedEntriesByAreaId() — filtered query returning only entries pending notification
• Verifies the notified flag transition: queued → notified → removed from queue

Test setup

• @Autowired DataTransferAuditDao — the DAO under test (manages t_plugin_datatransfer_audit table)
• @Autowired DataTransferAreaDao — injected only to satisfy DataTransferAuditDao.dataTransferAreaDao dependency
• override fun beforeAll() — calls recreateDataBase() to wipe any test data from other test classes
• init { DataTransferTestService.addPluginEntitiesForTestMode() } — registers plugin entities with the persistence layer

Audit queue system

The audit queue is the mechanism for observer notifications (see mail template #112):

1. File actions (upload/download/delete) call dataTransferAuditDao.insert() with notified=false
2. A scheduled job calls internalGetQueuedEntriesByAreaId() to find un-notified entries
3. After sending emails, the job marks entries as notified=true (via removeFromQueue())
4. Old entries (>30 days) are periodically purged