Skip to content

Latest commit

 

History

History
3 lines (2 loc) · 251 Bytes

File metadata and controls

3 lines (2 loc) · 251 Bytes

Unit Testing

The purpose of writing unit tests for pipeline libraries is to confirm that they function the way we expect. It also gives us a way to confirm that any features that were added to a library didn’t inadvertently break other features.