4 ms·
Tests can fail for a multitude of "flakey" reasons, that aren't due to 'source code' changes. - Network connections failed - Run out of memory - Duration tim
by gitgud 5y ago
Tests can fail for a multitude of "flakey" reasons, that aren't due to 'source code' changes.
- Network connections failed
- Run out of memory
- Duration timeouts
- Setting up the test infrastructure failed
All these can contribute to flakiness, and could be detected and reported by a bot like this. Making this a useful idea!
"Your test failed, but it was consider a flakey fail [Network Flakiness]" - FlakyBot