You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: