Search for a command to run...
Series
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.
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. /*...
It's the structure we use to name a unit test in a way that it鈥檚 identified and its context understood.Each letter represents a section: Unit under test: Which unit are we testing? Scenario or inputs to the unit: What situation are we simulating? Ex...
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...
In this section we execute the unit of code that we're going to test through its entry point by using the required parameters to simulate the situation we're going to verify in the unit test. test("the airplane state should be FLYING after takeoff", ...
