Running npm run test:coverage shows that there are a few unhappy paths not covered by our tests. It's possible that these are no longer needed due to the work done to tighten up types and make all properties required.
However, if it's possible to reach these sections of code, we should test them.
As the models contain core business logic, it makes a lot of sense to aim for 100% coverage here.
Bonus points: once 100% is reached, don't allow regressions by enforcing this setting up jest.config.ts
Running
npm run test:coverageshows that there are a few unhappy paths not covered by our tests. It's possible that these are no longer needed due to the work done to tighten up types and make all properties required.However, if it's possible to reach these sections of code, we should test them.
As the models contain core business logic, it makes a lot of sense to aim for 100% coverage here.
Bonus points: once 100% is reached, don't allow regressions by enforcing this setting up jest.config.ts