Skip to content
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

[TRACKING] End-to-End Test Contribution Proposal #1650

Closed
5 tasks done
therealbobo opened this issue Jan 26, 2024 · 10 comments
Closed
5 tasks done

[TRACKING] End-to-End Test Contribution Proposal #1650

therealbobo opened this issue Jan 26, 2024 · 10 comments
Assignees
Labels
kind/feature New feature or request lifecycle/rotten
Milestone

Comments

@therealbobo
Copy link
Contributor

therealbobo commented Jan 26, 2024

Motivation

As consumers of libs, we have developed a comprehensive set of end-to-end tests that have proven valuable in ensuring the reliability and functionality of falcosecurity/libs, particularly in conjunction with various drivers. Recognizing the benefits of community collaboration, we aim to upstream these tests to the falcosecurity/libs repository.

Feature

We propose the contribution of a set of private end-to-end tests specifically designed to validate the behaviour of libsinsp together with the associated drivers. These tests aim to cover critical scenarios, ensuring that the library performs optimally in various environments.

Additional Context

The proposed end-to-end tests cover a spectrum of scenarios, including but not limited to:

  • Interaction of libsinsp with various drivers.
  • Comprehensive coverage of edge cases and error scenarios.

These tests cover various areas of libsinsp interest, like:

  • processes
  • syscalls
  • cgroups
  • container runtimes
  • networking

To facilitate this process, we are creating this tracking issue to serve as a central point for discussion and coordination with the maintainers of falcosecurity/libs.

@therealbobo therealbobo added the kind/feature New feature or request label Jan 26, 2024
@incertum
Copy link
Contributor

Amazing @therealbobo, thanks for taking the lead on tracking this!

Re container runtimes cross-linking to #1298. Looking forward to seeing e2e tests expansions!

@therealbobo
Copy link
Contributor Author

/assign

@FedeDP
Copy link
Contributor

FedeDP commented Apr 16, 2024

@therealbobo what's the status of this one? Can you update the body?

Anyway, moving to 0.17.0 because the effort is not over yet!
/milestone 0.17.0

@poiana poiana modified the milestones: 0.16.0, 0.17.0 Apr 16, 2024
@FedeDP
Copy link
Contributor

FedeDP commented May 21, 2024

Moving to 0.18.0 because the effort is not over yet, i guess :)
/milestone 0.18.0

@poiana poiana modified the milestones: 0.17.0, 0.18.0 May 21, 2024
@poiana
Copy link
Contributor

poiana commented Aug 19, 2024

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

@Andreagit97
Copy link
Member

what is missing here @therealbobo ?

@therealbobo
Copy link
Contributor Author

There's only a PR left (which is already open) but I was asked to fix the flaky tests first. I looked into them but didn't find a solution yet.

@FedeDP
Copy link
Contributor

FedeDP commented Aug 27, 2024

I don't think we will make it for 0.18, let's move this to 0.19!
/milestone 0.19.0

@poiana
Copy link
Contributor

poiana commented Sep 26, 2024

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

@therealbobo
Copy link
Contributor Author

therealbobo commented Oct 17, 2024

This last PR #1958 ends this effort. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request lifecycle/rotten
Projects
None yet
Development

No branches or pull requests

5 participants