Child pages
  • Audit Trail tests
Skip to end of metadata
Go to start of metadata
Describes the tests needed to validate the Audit Trail functionality. This includes test of both the Audit trail service and the audit trail service functionality on the contributing components.


The AuditTrail service should have been running for enough time for the collector to have collected audittrail events from the components prior to the test.

WebGUI

  • First verify that audittrail events has been collected by expanding the Show collection schedule panel.
  • Verify that new audit trails are collected:
    •  Put a new file.
    • Trigger a new retrieval of audit trails.
    • Verify that Last collected number of audits column of the Show collection schedule panel show a number of audit trails where collected from the relevant collection.
  • Test the different filters: Set each filter to a given value and verify that the table filters correctly.

Audit trail preservation

This test is rather cumbersome, and should only be run in case of changes to the code affecting the audit trail preservation

  1. Configure the audit trail preservation to run every 10 minutes and set the log level to debug. Also configure the audit trail collect grace period so the collection never starts.

     <AuditTrailServiceSettings>
        ...
        <GracePeriod>99999999999</GracePeriod>
        <AuditTrailPreservation>
          <AuditTrailPreservationInterval>6000</AuditTrailPreservationInterval>
          ....
        </AuditTrailPreservation>
  2. Clear the (audit trail service) database.
  3. Restart the tomcat
  4. Look in the audit trail service log to verify that:
    1. The audit trail preservation is scheduled to run every minute
    2. The first preservation run should start quickly.
    3. The preservation should finish quickly packing 0 audit trails (no audits have been collected yet).
    4. All collections are preserved
  5. Start the collection of audit trails.
  6. Look in the audit trail service log to verify that:
    1. Some audit trail have been collected prior to the preserver running.
    2. The preserver start as scheduled.
    3. A number of audit trail are packed and ingested.
    4. The contents of the packed  

Unresolved audit trail issues. (${entries.size()} issues)

Key P Summary T Created Fix Version/s
Loading...
Refresh

  • No labels