This document serves as reference for current practices and patterns that we want to standardize across Amundsen’s frontend application code. Below, we provide some high-level guidelines targeted towards new contributors or any contributor who does not yet have domain knowledge in a particular framework or core library. This document is not intended to provide an exhaustive checklist for completing certain tasks.
We aim to maintain a reasonably consistent code base through these practices and welcome PRs to update and improve these recommendations.
- Leverage TypeScript to prevent bugs in unit tests and ensure that code is tested with inputs that match the defined interfaces and types. Adding and updating test fixtures helps to provide re-useable pieces of typed test data or mock implementations for this purpose.
beforeEach()for test setup when applicable. Leverage
afterEachfor test teardown when applicable to remove any side effects of the test block. For example if a mock implementation of a method was created in
beforeAll(), the original implementation should be restored in
afterAll(). See Jest’s setup-teardown documentation for further understanding.
- Use descriptive title strings. To assist with debugging we should be able to understand what a test is checking for and under what conditions.
- Become familiar with the variety of Jest matchers that are available. Understanding the nuances of different matchers and the cases they are each ideal for assists with writing more robust tests. For example, there are many different ways to verify objects and the best matcher to use will depend on what exactly we are testing for. Examples:
- If asserting that
inputObjectis assigned to variable
x, asserting the equivalence of
.toBe()creates a more robust test for this case because
.toBe()will verify that the variable is actually referencing the given object. Contrast this to a matcher like
.toEqual()which will verify whether or not the object happens to have a particular set of properties and values. In this case using
.toEqual()would risk hiding bugs where
xis not actually referencing
inputObjectas expected, yet happens to have the same key value pairs perhaps due to side effects in the code.
- If asserting that
expectedObject, asserting the equivalence of each property on
.toBe()or asserting the equality of the two objects using
.toMatchObject()is useful when we only care that certain values exist on
outputObject. However if it matters that certain values do not exist on
outputObject– as is the case with reducer outputs –
.toEqual()is a more robust alternative as it compares all properties on both objects for equivalence.
- Mock the Date object and its methods’ return values, and run assertions based on the mock values.
- Create assertions knowing that the unit test suite will run as if we are in the UTC timezone.
- Code coverage is important to track but it only informs us of what code was actually run and executed during the test. The onus is on the developer to focus on use case coverage and make sure that right assertions are run so that all logic is adequately tested.
- Enzyme provides 3 different utilities for rendering React components for testing. We recommend using
shallowrendering to start off. If a component has a use case that requires full DOM rendering, those cases will become apparent. See Enzyme’s api documentation to read more about the recommendations for each option.
- Create a re-useable
setup()function that will take any arguments needed to test conditional logic.
- Look for opportunities to organize tests a way such that one
setup()can be used to test assertions that occur under the same conditions. For example, a test block for a method that has no conditional logic should only have one
setup(). However, it is not recommended to share a
setup()result across tests for different methods, or across tests for a method that has a dependency on a mutable piece of state. The reason is that we risk propagating side effects from one test block to another.
- Consider refactoring components or other files if they become burdensome to test. Potential options include (but are not limited to):
- Create subcomponents for large components. This is also especially useful for reducing the burden of updating tests when component layouts are changed.
- Break down large functions into smaller functions. Unit test the logic of the smaller functions individually, and mock their results when testing the larger function.
- Export constants from a separate file for hardcoded values and import them into the relevant source files and test files. This is especially helpful for strings.
- Because the majority of Redux code consists of functions, we unit test those methods as usual and ensure the functions produce the expected output for any given input. See Redux’s documentation on testing action creators, async action creators, and reducers, or check out examples in our code.
- Unless an action creator includes any logic other than returning the action, unit testing the reducer and saga middleware logic is sufficient and provides the most value.
redux-sagagenerator functions can be tested by iterating through it step-by-step and running assertions at each step, or by executing the entire saga and running assertions on the side effects. See redux-saga’s documentation on testing sagas for a wider breadth of examples.