@shibao@vriska@sun the short explanation is that unit tests in real world projects with real customers and constantly changing requirements are ephemeral trash that pop in and out of existence at random. Attempting to abstract too much code into common paths results in tests that are difficult to change in isolation and end up consuming a lot of production time.