aquasecurity / aquasecurity/tracee
add e2e test of tracee triggered events
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 507
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
add e2e tests to check that the following events are triggered at the start of tracee:
- [ ] hooked_syscalls
- [ ] hooked_proc_fops
- [ ] hooked_seq_ops
- [ ] print_mem_dump
- [ ] init_namespace
Also add tests for the following events to check that they are retriggered on kernel module loading:
- [ ] hooked_syscalls
- [ ] hooked_proc_fops
- [ ] hooked_seq_ops
- [ ] print_mem_dump
Contributor guide
Research direction
Start by locating Tracee's existing end-to-end test entry point and the checks for startup and kernel module loading. Add coverage for each listed event at Tracee startup, then verify the specified events are triggered again after module loading. Done means all checklist events are exercised and the e2e tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- operating-systems, security, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100