Mocking config data in tests
- Each option has a set of values, which come from the app state
- Options also each have a config, which are defined in
configs.js(potentially a large list, with 'dynamic' data-like variations)
We're testing the
summarise function. To isolate my tests, I've mocked the option configs. This means we don't have to couple the test to certain option configs, which allows an author to change the settings (e.g. option names) freely.