Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: improve unit tests in debian provider #311

Merged
merged 1 commit into from
Oct 3, 2023

Conversation

willmurphyscode
Copy link
Contributor

The provider is intentionally resilient to malformed records, and implements this resilience by logging and continuing on when any exception is thrown. However, this prevents the unit tests from many errors in the implementation of the provider. Therefore, spy on the provider and fail unit tests if it is logging exceptions.

Part of #309, but doesn't resolve it.

The provider is intentionally resilient to malformed records, and
implements this resilience by logging and continuing on when any
exception is thrown. However, this prevents the unit tests from many
errors in the implementation of the provider. Therefore, spy on the
provider and fail unit tests if it is logging exceptions.

Signed-off-by: Will Murphy <[email protected]>
@willmurphyscode willmurphyscode changed the title chore: assert no exceptions logged during test run chore: assert no exceptions logged during debian provider unit test Sep 29, 2023
@willmurphyscode willmurphyscode changed the title chore: assert no exceptions logged during debian provider unit test chore: improve unit tests in debian provider Sep 30, 2023
@spiffcs spiffcs merged commit c4680bf into main Oct 3, 2023
6 checks passed
@spiffcs spiffcs deleted the chore/test-no-exceptions-logged-during-debian branch October 3, 2023 12:46
andrew pushed a commit to andrew/vunnel that referenced this pull request Oct 4, 2023
The provider is intentionally resilient to malformed records, and
implements this resilience by logging and continuing on when any
exception is thrown. However, this prevents the unit tests from many
errors in the implementation of the provider. Therefore, spy on the
provider and fail unit tests if it is logging exceptions.

Signed-off-by: Will Murphy <[email protected]>
Signed-off-by: Andrew Nesbitt <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants