test: add integration test for audit script results#1235
Merged
RoyalOughtness merged 2 commits intosecureblue:livefrom Aug 8, 2025
Merged
test: add integration test for audit script results#1235RoyalOughtness merged 2 commits intosecureblue:livefrom
RoyalOughtness merged 2 commits intosecureblue:livefrom
Conversation
This integration test checks that the results of the audit script on first boot are as expected. (It's unclear why the sysctl kernel.printk has the value `0 3 3 3` rather than `3 3 3 3` in the integration test image, but for now we'll just include it in the expected results.) Signed-off-by: Daniel Hast <[email protected]>
RoyalOughtness
approved these changes
Aug 7, 2025
EsseLowNitro
approved these changes
Aug 8, 2025
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
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.
This integration test checks that the results of the audit script on first boot are as expected.
(It's unclear why the sysctl
kernel.printkhas the value0 3 3 3rather than3 3 3 3in the integration test image, but for now we'll just include it in the expected results. This issue is not observed on a real installation.)