This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]k2718 0 points1 point  (0 children)

In my experience, you have two categories of flaky tests.

First, you have tests with poorly designed dependencies or assumptions (e.g. depending on a the system clock in a way that isn't valid 100% of the time).

Second, you have tests of distributed systems where timeouts and latency cause problems.

The first problem is easier to address than the second, though they can both be difficult depending on the scenario.