|
|
|
|
|
|
by mason55
1331 days ago
|
|
|
I wouldn't write unit tests for an external library but any integration test will implicitly test any external libraries that are in the code path. That's one of the points of integration tests - catching cases where the underlying code still works as it's supposed to but the way it's supposed to work has changed. Whether it's an external library or code you wrote, your goal is to test that all the pieces still fit together like they're supposed to. In the case of something like Noloco, I imagine it would be more like "we need to change this DB schema, can we update the schema in a test environment and make sure that we didn't break our Noloco app?" There's nothing to unit test there but if you don't have a solid set of integration and e2e tests then you might have a form that's halfway through a flow that suddenly stops working and you don't notice until your conversions crater to zero. |
|
|