-
-
Notifications
You must be signed in to change notification settings - Fork 402
Improved test setup #2363
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
Improved test setup #2363
Conversation
1fdf76d
to
0c36cf6
Compare
I see some util/regexp-assembly/data files changed. Is this part of this PR? |
No, that was an accident (I had been working on something else originally). I've removed those changes. |
Note: tests are failing because there is no version 1.3.0 of |
ftw version 1.3.0 is out, this one can be tested now! |
79e86b7
to
5cfbc2d
Compare
Are we ready to merge this one? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How fast will this be running now? Comparable times to go-ftw? Do we need to keep tests split in that many parallel checks?
@theseion Yes, comparable: 1m 17s vs. 1m 20s. I would say let's remove the tests matrix:
And run it with |
Cool! I didn't have any numbers :) Yes, let's remove the matrix. I've always run all tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now, this is progress! Good job on getting this to the finish line!
Thanks for the help! |
This reverts commit af5ea8d.
Improved CRS_Tests.py
Removed unused fixture parameters
Completely rewrote log checker to use the new marker feature instead of parsing log timestamps
Added a bit of magic to detect the correct log to scan. This should reduce the number of times you run tests with the wrong configuration
This PR relies on two other PR's: coreruleset/modsecurity-crs-docker#58, coreruleset/ftw#66.