@dmitrykandalov Yeah, definitely an annoying default. I tend to set `testLogging.showStandardStreams = true`. Then of course you have the problem that every test's output is logged, but I like to make sure that test logging is only dumped out on failures, so this works nicely for me :)
The reason why using "eventually {...}" in tests is not a good idea is that it will make your build slow and non-deterministic. Retries will slow down passing tests, timeouts will make failures even slower, and failure messages will read like "something didn't happen on time" 🤷
@dmitrykandalov Most important thing first. Probably not quite right, I like to _think_ of it as similar to writing’s “inverted pyramid” — https://t.co/idKekpzuiP
If you put a hold on deploys, and you don't simultaneously put a hold on development or merges, then yeah sure you might buy yourself some peace in the near term.
At the expense of the land mines you are piling up in your future.
Looking for a lead dev or Agile coach role in Eco or Tech for Good, 4 days a week, London-based or remote. Willing to go *permie* with the right org; until then happy to contract, but ready to settle down. Kotlin, Java, C#, learning Rust, open to other stacks. Please pass it on!
Here is a video from 1975 about how to approach software understanding:
https://t.co/evbYZ41Ogd
(H/T @AliakseiSyrel)
How does your practice today compare to that?
Where do you see improvements possible?
👇
Question for #java developers. What are `BeforeAll` and `AferAll` used for in the test suites for code you maintain?
Interested in what you actually see in the code you have access to, rather than what you *think* they should be used for.
Is it always for heavyweight stuff?