We want some coverage on the config parsing code. Currently the apitests define the config as structs, which is post validation in the code. We could either
- Unit test the file/config.go code
- Define the config as json in the apitest, which means apitests tests cover config parsing and validation
My preference is for 2 but I am open to suggestions.
We want some coverage on the config parsing code. Currently the apitests define the config as structs, which is post validation in the code. We could either
My preference is for 2 but I am open to suggestions.