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.

Sign up for GitHub

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

Jump to bottom

CI test cases #113

Open
Tracked by #16
justindotpub opened this issue Mar 9, 2023 · 0 comments
Open
Tracked by #16

CI test cases #113

justindotpub opened this issue Mar 9, 2023 · 0 comments
Milestone
Batch 1: Reliable...

Comments

@justindotpub
Copy link
Contributor

justindotpub commented Mar 9, 2023 •
edited by bdehaynin
Loading

Related to ensuring we're reliable, add CI tests with varying sizes, configurations... maybe some fuzz tests, property based...

  • Find way to add tests with known inaccurate filter, making sure we truly cleanup. Even if just starting with looking at logs, prove that we handle filter inaccuracy properly.
  • Think about impact of GC, corruption, cache purging, etc. Needs to be resillient and just work. Include forced GC in tests, and other failure states.
  • In general, think about all the various edge cases and ensure we test each one of them. Give those test cases names for easy descriptions of what we need to test. Also, fuzz testing or property based testing seems wise, at least in CI.

ETA: 2023-10-31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Batch 1: Reliable transfer over HTTP
Development

No branches or pull requests
1 participant
@justindotpub