idea - throttle
nitsanavni opened this issue · comments
re:
If you run multiple tests, each result is published, so gren, red, green, green test results in four tests would count as as very short red phase
Idea: throttle events to smooth these kinds of glitches
I'm not quiet sure: The graph shows you at what point in time your tests have been red/green, so when throttling this would skew the graph. I'd guess the opposite could be a solution: If one of n tests within a second was red, the result is red at all.
I tried to hook into the test engine to get the result of all tests executed but it seems much more complicated than hooking into the result of a single test.
Not sure what to try as a next best guess, any ideas welcome :)
- So for clarification: If you run 8 tests and the last is green, that gets interpreted as the beginning or part of an existing green phase, if the last test is red vice versa, the other 7 tests beforehand are the possible glitches
without looking at the code.
maybe add a state like:
test1: passed, 3s ago
test2: failed, 2s ago
test3: passed, 1s ago
the graph will show:
all_tests_passed: all(tests.passed)
🤷♂️