1. What
   1. It’s a test that sometimes fails, but if you retry it enough times, it passes, eventually.
2. Some causes
   1. Test suite is run in parallel
   2. Data from previous tests
   3. Speed & Order
      1. Slow Internet connection
      2. Web elements were not drawn
      3. Ajax requests
      4. JS
   4. Browser
      1. stability
      2. parallel browsers (loss of focus)
      3. window size
   5. Application cache
   6. Time
   7. Remote Services
   8. Resource Leaks
3. Help you
   1. Logs of previous builds
   2. A clean data base before each test
   3. Split up test suites
   4. Service emulators
   5. Test Pyramid
   6. Video/screenshot on failure
4. 4 Steps
   1. Plan
      1. Find Flaky Tests
   2. Do
      1. Document Flaky Tests
   3. Check
      1. Determine the root cause
   4. Act
      1. Fix it
5. sources
   1. https://docs.gitlab.com/ee/development/testing_guide/flaky_tests.html
   2. https://assets.ctfassets.net/ut4a3ciohj8i/4av6djQ7McGS0OcM62y4iQ/d66a9244002a6b8531a6d5438d4c7b8a/andrei-solntsev.flaky-tests.ru.2017.pdf
   3. http://semaphoreci.com/blog/2017/04/20/flaky-tests.html
   4. https://www.ombulabs.com/blog/rspec/continuous-integration/how-to-track-down-a-flaky-test.html
   5. https://circleci.com/blog/use-circleci-orbs-to-build-test-and-deploy-a-simple-go-application-to-aws-ecs/
   6. https://semaphoreci.com/community/tutorials/how-to-deal-with-and-eliminate-flaky-tests
   7. https://www.deflaker.org/flaky-tests/
   8. https://martinfowler.com/articles/nonDeterminism.html
   9. https://www.thoughtworks.com/insights/blog/no-more-flaky-tests-go-team
   10. https://semaphoreci.com/community/tutorials/how-to-deal-with-and-eliminate-flaky-tests
   11. https://docs.pytest.org/en/latest/flaky.html