Search for a command to run...
It's the structure we use to name a unit test in a way that it’s identified and its context understood.
Each letter represents a section:
No comments yet. Be the first to comment.
Unit tests are a tireless guard that overwatch your software to ensure it always behaves as it's expected. In this series I'll introduce to you its basic concepts.
In this section we verify that the unit of code, effectively, produces the expected result for the simulated situation. Only one exit point must be verified for each unit test and it's that exit point this section is focused on. test("the airplane st...
The Numbered Shelf
It's the third section in the name. It specifies what's the expected result after executing the unit of code under the simulated scenario. /** In this example the three sections of the name are in the same text. * Airplane is the Unit under test * ...
or Inputs to the Unit
It's the first section in the name. It specifies which is the unit that we're currently testing. The unit can be in the same text as the other sections or separated in a group if we're going to create multiple unit tests for the same unit of code. /*...
Fifty Words
21 posts
