Audit Trail tests

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.

• First verify that audittrail events has been collected. All audittrail events should be requested via the web interface.
  
  • The returned list should contain entries from all the different components expected to deliver audit trail information.
• Test the different filters
  
  • Dates:
    
    • Filter on a valid date range
      
      • Only audit trail events from the date range should be present in the list of audit trail events.
    • Filter on an invalid date range (the start date being after the end date)
      
      • No change should happen to the list of events
    • Filter only on a start date
      
      • Only events from the start date and forward should be present in the event list
    • Filter only on a end date
      
      • Only event prior and up to the end date should be present in the event list
  • Filter on a known fileID
    
    • Only events related to the specified fileID should be present in the event list.
  • Filter on an unknown fileID
    
    • No events should be present in the event list
  • Filter on a known component
    
    • Only events from the specified component should be present in the event list
  • Filter on an unknown component
    
    • No events should be present in the event list
  • Filter on a known actor
    
    • Only events related to the specified actor should be present in the event list
  • Filter on an unknown actor
    
    • No events should be present in the event list
  • Filter on the different action types
    
    • Only actions from the specified type should be present. "ALL" being the exception, as it should allow for any type.
  • Filter a couple of collections and verify only audit trails for the selected collection is listed.
  • Change the number of listed event and verify the number of listed event changes accordingly.