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

tests: use stretchr/testify instead of custom check package #130

Merged
merged 2 commits into from
Sep 6, 2024
Merged

Conversation

mfridman
Copy link
Owner

@mfridman mfridman commented Sep 5, 2024

Fix #129

@ccoVeille
Copy link
Contributor

before starting going further, I would suggest you to enable testifylinter at golangci-lint

Your life will become way better.

@mfridman
Copy link
Owner Author

mfridman commented Sep 5, 2024

Don't we already have this enabled?

tparse/.golangci.yaml

Lines 29 to 30 in 2f5079b

# testify checks good usage of github.com/stretchr/testify.
- testifylint

@mfridman mfridman merged commit 458bfb4 into main Sep 6, 2024
3 checks passed
@mfridman mfridman deleted the mf/gh129 branch September 6, 2024 00:05
@ccoVeille
Copy link
Contributor

Don't we already have this enabled?

tparse/.golangci.yaml

Lines 29 to 30 in 2f5079b

# testify checks good usage of github.com/stretchr/testify.
- testifylint

Oh my bad, indeed. I wasn't expecting the linter to be enabled in the configuration before testify was used.

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.

Switch to using https://github.com/stretchr/testify
2 participants