Rewrite audit/transactions.js to use the AuditSpooler correctly

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Security 2021-04-19, Security 2021-05-03, Security 2021-05-17
    • 29
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, the test in transactions.js is just calling getNextEntry() and examining the next line in the audit spooler to see that the entry that it expects is present. However, this uses the incorrect assumption that there are no other processes auditing at the time. This should be fixed to use the AuditSpooler functionality like assertEntry and findEntry.

            Assignee:
            Shreyas Kalyan
            Reporter:
            Shreyas Kalyan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: