The Array
The Numbered Shelf
Oct 5, 20251 min read7
Command Palette
Search for a command to run...
#software-engineering
Articles tagged with #software-engineering
E - Expected Value
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 * ...
Oct 23, 20221 min read5
S - Scenario
or Inputs to the Unit
Oct 23, 20221 min read11
U - Unit Under Test
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. /*...
Oct 23, 20221 min read24
USE - Test Naming
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...
Oct 23, 20221 min read44
Assert
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...
Oct 23, 20221 min read10