When changing Bloom code, make sure the following main features or happy paths are not broken by the changes.

Each feature can be tested locally before deployment. Features can also be tested on staging after a PR has been merged to develop.

Where possible, tests should be written for these paths so that they can be tested automatically.

There are other happy paths within Bloom which aren’t listed here as they’re not considered key features of Bloom. However if a particular feature is being changed, ensure that feature has not regressed!