Skip to content

Latest commit

 

History

History
4 lines (3 loc) · 243 Bytes

File metadata and controls

4 lines (3 loc) · 243 Bytes

Overview

The purpose of writing unit tests for pipeline libraries is to confirm that the libraries functions as expected. It is also a way to confirm that any features that were added to a library didn't inadvertently break other features.