✏️ Testing

[jamie-lynch]

One of the benefits of writing our infrastructure in a fully fledged programming language is the ability to write reusable components which can be tested. This library defines those components, both in the form of constructs and patterns (see 001-constructs-and-patterns for more details).

There are two main strategies that can be used to unit test these components.

1. Snapshot tests synthesise a given stack and compare the output to a previous version that has been verified by the user and checked into the repository. If there are any changes, the test fails and the user is displayed the diff to either fix or update the stored snapshot.
2. Direct Assertions use the different assertions provided by the test framework to test specific functionality. For example, asserting that a property exists or that an array contains a particular value.

The Testing ADR should capture the context, possible approaches and final decisions on this topic. This discussion can be used to talk through our ideas and finalise the ADR.

Doc: 004-testing