Structuring Effective Unit Tests
I'm a seasoned Software Engineer with over half a decade of experience shaping the world of software development. My passion is anchored in writing code that is not just efficient, but also elegant and clean. An advocate for continuous improvement, I am forever on the hunt for the most cutting-edge developments in our dynamic industry.
"Maximizing Test Coverage and Efficiency: A guide to structuring Unit Tests"
๐จ๐จ๐จ ๐๐๐๐๐๐๐ - ( ๐ข๐ณ๐ณ๐ข๐ฏ๐จ๐ฆ, ๐ข๐ค๐ต, ๐ข๐ด๐ด๐ฆ๐ณ๐ต)
๐๐ข๐ฏ๐๐ง-๐๐ก๐๐ง-๐๐ก๐๐ง- very similar to 3A
In the ๐๐๐๐๐๐๐ section you bring the SUT and its dependencies to a desired state.
In the ๐๐๐ section, you call the methods on SUT, pass the prepared dependencies, and capture the output value ( if any )
In the ๐๐๐๐๐๐ section, you verify the outcome.
๐๐ข๐ฏ๐๐ง corresponds to arrange
๐๐ก๐๐ง corresponds to act
๐๐ก๐๐ง corresponds to assert
There's no difference between these two patterns, it's just that the Given-When-Then pattern is more readable to non-programmers.
