AAA - Test Structure
Command Palette
Search for a command to run...
Comments
Join the discussionNo comments yet. Be the first to comment.
Unit Testing
Part 12 of 19
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.
Arrange
In this section we are in charge of initializing all the dependencies (real or test doubles) required to simulate the situation we are going to verify in the unit test. test("the airplane state should be FLYING after takeoff", () => { /** * Noti...
More from this blog
The Array
The Numbered Shelf
Oct 5, 20251 min read
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 read
S - Scenario
or Inputs to the Unit
Oct 23, 20221 min read
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 read
USE - Test Naming
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: Unit under test: Which unit are we testing? Scenario or inputs to the unit: What situation are we simulating? Ex...
Oct 23, 20221 min read
F
Fifty Words
21 posts