-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Correctness
Crazy idea: can we dynamically scale our testing as a function of commit volume?
Note:
- Antithesis execution frequency is controlled by a cronjob (owned by Antithesis)
What criteria to use to adjust the run? Say, run proportionate to the volume of commits to the master branch? Anecdotally, I'm seeing ~30 commits/day on a "typical" day. We could have something like:- 0 commits = run none (or very little)
- 1 - 10 commits = run a little bit
- 11 - 40 commits = run "normal" load
- 41+ commits = run "normal", but maybe notify stakeholders that volume is way up.