Comments by "TheEvertw" (@TheEvertw) on "Your Tests Are Failing YOU!" video.

  1. "Inherently flaky tests" That is a VERY small minority. Even waiting for external resources can be made deterministic, by waiting until the system is in a predefined state before running the actual test. I have spent years developing distributed systems, and flaky tests were NOT ACCEPTABLE to us. One major cause of flaky tests is not having the shutdown procedures properly implemented. That means that tests can not clean up after themselves properly. Make sure your shutdown procedure is bullet-proof, and tests where processes are started and stopped as part of the test will run flawlessly. For instance, if you terminate a thread, use `join` to wait until it is actually terminated.
    1
  2. Flaky tests indicate something is wrong. Either in the test case, the test framework, or in the system under test. You MUST find out which one of the three it is, and fix the problem. Because even if you think you know why the test is failing, that issue can hide an actual issue.
    1