Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests for log analyzer using Github Actions #55

Open
WizardCM opened this issue Jun 2, 2020 · 2 comments
Open

Tests for log analyzer using Github Actions #55

WizardCM opened this issue Jun 2, 2020 · 2 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@WizardCM
Copy link
Member

WizardCM commented Jun 2, 2020

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

@WizardCM WizardCM added help wanted Extra attention is needed good first issue Good for newcomers labels Jun 2, 2020
@WizardCM WizardCM changed the title Tests for log analyzer Tests for log analyzer using Github Actions Jun 2, 2020
@WizardCM
Copy link
Member Author

WizardCM commented Jun 2, 2020

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

@RytoEX
Copy link
Member

RytoEX commented Mar 21, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants