feat(test): test audit logs

[papidb]

No description provided.

[github-actions]

Test Results

1 006 tests  +167   992 ✅ +167   45s ⏱️ +2s
   35 suites +  1     0 💤 ±  0 
    1 files   ±  0    14 ❌ ±  0 

For more details on these failures, see this check.

Results for commit 926397e. ± Comparison against base commit 3b213f6.

This pull request removes 2 and adds 169 tests. Note that renamed tests count towards both.

AuditLogsController should be defined ‑ AuditLogsController should be defined
AuditlogsService should be defined ‑ AuditlogsService should be defined

AuditLogsController Event Logging (via service) automatic event capture should log event metadata as details ‑ AuditLogsController Event Logging (via service) automatic event capture should log event metadata as details
AuditLogsController Event Logging (via service) automatic event capture should log event name correctly ‑ AuditLogsController Event Logging (via service) automatic event capture should log event name correctly
AuditLogsController Event Logging (via service) automatic event capture should log events with companyId from event author ‑ AuditLogsController Event Logging (via service) automatic event capture should log events with companyId from event author
AuditLogsController Event Logging (via service) automatic event capture should log events with userId from event author ‑ AuditLogsController Event Logging (via service) automatic event capture should log events with userId from event author
AuditLogsController Event Logging (via service) automatic event capture should save without reloading entity ‑ AuditLogsController Event Logging (via service) automatic event capture should save without reloading entity
AuditLogsController Event Logging (via service) automatic event capture should verify OnEvent decorator captures all events (**) ‑ AuditLogsController Event Logging (via service) automatic event capture should verify OnEvent decorator captures all events (**)
AuditLogsController Event Logging (via service) event data validation should handle events with complex metadata objects ‑ AuditLogsController Event Logging (via service) event data validation should handle events with complex metadata objects
AuditLogsController Event Logging (via service) event data validation should handle events without author information ‑ AuditLogsController Event Logging (via service) event data validation should handle events without author information
AuditLogsController Event Logging (via service) event data validation should handle events without metadata ‑ AuditLogsController Event Logging (via service) event data validation should handle events without metadata
AuditLogsController Event Logging (via service) event data validation should preserve metadata structure in details field ‑ AuditLogsController Event Logging (via service) event data validation should preserve metadata structure in details field
…

♻️ This comment has been updated with latest results.