Summary

Refactor or add new unit tests to use exported errors

Problem Definition

There is no consistency in using exported errors (#1140) throughout the internal modules. Exported errors should be used in the unit tests.

Proposal

After issue #1140 is resolved, we should make use of all the exported errors in our unit tests to enhance the testing process. Currently, several unit tests depend on logic to compare generic errors and not specific errors. However, with the creation of exported errors, we can start comparing specific errors as well. This could also be an excellent chance to introduce new unit tests using the newly exported errors.

DoD

• Exported errors are used in unit tests for all internal modules listed in Export errors for easier programmatic use #1140
• Additional unit tests are created for exported errors