Tracee end-to-end tests #1033
Merged
Tracee end-to-end tests #1033
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
|
At the moment, let's start by having these tests merged in and be run manually. There are a few kinks to iron out for running these on GitHub Actions (mostly around building a docker image for Tracee) but that's a separate story to work on in a different PR. |
danielpacak
reviewed
Oct 5, 2021
There was a problem hiding this comment.
Great to see such integration tests! I left a few comments to better understand how we run them and whether https://github.com/testcontainers/testcontainers-go may be useful to run containers
Signed-off-by: Simar <simar@linux.com>
…launch Signed-off-by: Simar <simar@linux.com>
danielpacak
approved these changes
Oct 8, 2021
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.
The idea to have an automated test harness started in #1022. This PR tries to tackle some of that by starting with a few simple cases to launch and try tracee in various scenarios.
One use case of such a harness can be running on a cluster of a variety of Kubernetes flavours (mix of kernel versions, BTF on/off etc.) to see if we can guarantee existing behaviour while adding/replacing functionality to avoid regressions.