What's the anatomy of a perfect unit test?
Let's unpack this a bit. A suite of quality unit tests allows you to refactor code without breaking things and adding features without creating new bugs.
A good unit test is:
Simple - it's easy to read and understand
Isolated - it's independent of test cases
Fast - it only takes a few seconds to run it
Well-structured - each developer reading another developer's code should see what each unit test is doing
Reliable - a unit test must be failure-free no matter how many times you run it
It's worth noting that unit tests are written by developers who have a deep understanding of the inner workings of system functionality. So if the test fails, the reason might be the required changes or implementation problems
