loganalyzer icon indicating copy to clipboard operation
loganalyzer copied to clipboard

Tests for log analyzer using Github Actions

Open WizardCM opened this issue 5 years ago • 2 comments

Using something like pytest, a simple method of verifying some detailed logs continue to get analyzed correctly.

WizardCM avatar Jun 02 '20 13:06 WizardCM

Including a folder full of log files in the repo would be fine for a first version, triggering py loganalyzer.py <filename/url>

WizardCM avatar Jun 02 '20 13:06 WizardCM

Was thinking about this. A comprehensive solution would probably involve changing every check function that returns a message (info/warning/error) to add a unique error code as an element in its returned array so that we can check against that instead of checking its message content or title. If we wanted to do "bare minimum" checks, we could just check the returned severity value for the various check functions for a given log, but that wouldn't tell us if we're getting the exact result we expect if a function can return multiple messages of the same severity.

RytoEX avatar Mar 21 '24 00:03 RytoEX