Sorry for the delay in responding, this repository has not been finalized, but the central idea is still the same.

It is a very important subject indeed, touching on this subject is essential especially for developers who work directly on highly complex products, planning will always be essential.

Great tip!

Thanks for reading! I agree with what you said, we need to be aware of these details too!

Great article!

Great explanation! These are important resources that help us a lot to solve specific problems. Thanks for sharing with the community!

Awesome! Dart and Flutter are on my future study list, thanks for sharing this rich content with the community!

Excellent explanation, thanks for sharing your knowledge!

Exactly Anthony Fung , it already falls in frontend cases in specific situations where it was necessary to perform two actions. In most cases this was not necessary. When I began to apply a critical eye more frequently to unit tests, I began to observe that the more actions in a single test method, the more easily it broke.

Anthony Fung Nice, I think it's important to have this view you commented, in the last year I have adopted a more simplistic testing strategy, look at the requirement, understand the expected behaviors and just check what really matters in the assert. I also look for invalid scenarios, unusual inputs that I wouldn't normally think of if I just did the happy path of unit testing. Obviously this is not always easy to apply, especially in complex systems. I am writing about this as well. What strategy do you usually put into practice for your test cases?