feat: migrate assertions from gotest.tools to testify #915
+508
−521
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR migrates all test assertions from gotest.tools/v3/assert to github.com/stretchr/testify/assert, consolidating the codebase on a single testing library. The migration maintains full test coverage and behavior.
Implementation Details
Assertion Mapping:
Complex Comparisons:
For tests requiring cmpopts (specifically helpers_test.go), I retained google/go-cmp directly and used assert.Empty(t, cmp.Diff(expected, actual, opts)) pattern. This preserves the powerful comparison options needed for complex struct comparisons while still using testify for the assertion.
Files Migrated (24 total):
Command packages:
Root level:
Package tests:
Test directory:
Test utilities:
Testing
All existing tests continue to pass with the new assertions:
go test -short ./...
Build verification:
go build ./...
I verified that:
Notes
Fixes #913