fix(CI): add the job to run go test on the KubeArmor/KubeArmor directory #1267
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 current implementation does not have a job in CI to run tests for golang programs under the KubeArmor/KubeArmor directory.
Therefore, this commit will add the job to ci-test-go.yml to run tests for golang programs under the KubeArmor/KubeArmor directory.
Purpose of PR?:
Fixes #
I haven't created an issue. However, in the pull request #1264 , we were advised to add a CI to run tests of golang programs under KubeArmor/KubeArmor directory. Specifically, this part is applicable.
Does this PR introduce a breaking change?
No.
I added a job to
ci-test-go.yml
with this commit.If the changes in this PR are manually verified, list down the scenarios covered::
In the CI job, tests of golang programs can be run in the KubeArmor/KubeArmor directory.
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Attached below is a screenshot of running the job I added in my verification environment.
Note that at the moment, the test fails at the process in
KubeArmor/KubeArmor/core/karmorprobedata.go:61:17
as shown in the image. I will try to fix this in another pull request.Checklist:
<type>(<scope>): <subject>