-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fail tests on NewConfig error #145
Labels
cleanup
Maintenance, cleaning up codebase or repo
Milestone
Comments
adatzer
added a commit
that referenced
this issue
Jun 21, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 1, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 1, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
pushed a commit
that referenced
this issue
Aug 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some tests we call
NewConfig
and then assert it is not nil. If there is an error, the assertion will fail, however the test will continue. At the same time, in that case the config will be nil, which then triggers a panic for following assertions on its fields. We could fail the test instead.The text was updated successfully, but these errors were encountered: