Better test structure validation and logic, PascalCase mandatory#5
Merged
fr0gger merged 9 commits intoNova-Hunting:mainfrom Mar 2, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey Thomas, I've improved the test structure validation and whole logic and then I've enforced the PascalCase convention for the rule titles, before it was only warning, now i set it as a hard requirement for the test to pass.
I've introduced yaml lint check for the tests in the CI to make sure the Test yaml are ok (before it would have caused the whole test job to fail) and made the workflow faster by installing the requirements in a different way
I've reduced also the timeouts, before they were too large