An alternative idea is that some types of "boilerplate" can be annoying to write but actually helpful for people to read, and these tools might make that type o

An alternative idea is that some types of "boilerplate" can be annoying to write but actually helpful for people to read, and these tools might make that type of code more acceptable. For example, it's helpful to be able to see all the steps a test case is doing in the one function, so you can read that and see what's going wrong if it fails. If a lot of your test cases are similar you might be tempted to refactor and put common parts in separate methods, often with unhelpful names like "assertResult()", etc, but now the reader has to jump about to understand the logic. Whereas this allows you to write the more repetitive but also more readable code easier