-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Comparing changes
Open a pull request
base repository: stretchr/testify
base: v1.8.2
head repository: stretchr/testify
compare: v1.8.4
- 6 commits
- 19 files changed
- 9 contributors
Commits on Mar 14, 2023
-
Compare public elements of struct (#1309)
* Implement checking only exported fields Co-authored-by: Anthony Chang <[email protected]> * Update comment * Run go generate * Make compatiable with Go 1.16.5 * Fix go generate files * Fix white space changes * Fix whitespace changes * Fix whitespace changes in gogenerate files --------- Co-authored-by: Anthony Chang <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for c5fc9d6 - Browse repository at this point
Copy the full SHA c5fc9d6View commit details
Commits on May 5, 2023
-
assert: fix error message formatting for NotContains (#1362)
* assert: rename and refactor TestContainsFailMessage I've renamed it to TestContainsNotContains and added a test case structure so that I can use this test to validate the failure messages from both Contains and NotContains, There are no functional changes here, strictly refactoring. A new test case will be added in a subsequent change. * assert: fix error message formatting for NotContains It was using "%s" to format the s and contains arguments, but these could be any type that supports iteration such as a map. In this case of NotContains failing against a map, it would print something like: "map[one:%!s(int=1)]" should not contain "one" Fix this using "%#v" as was already done for Contains and added test cases covering both the "len()" / iterable failure messages as well as the Contains/NotContains failure case. The new message for this example map would be something like: map[string]int{"one":1} should not contain "one"
Configuration menu - View commit details
-
Copy full SHA for 437071b - Browse repository at this point
Copy the full SHA 437071bView commit details
Commits on May 9, 2023
-
allow testing for functional options (#1023)
* allow testing for functional options * add linting docs * use reflect magic to obtain FunctionalOption name Co-authored-by: dillonstreator <[email protected]> --------- Co-authored-by: dillonstreator <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for b3106d7 - Browse repository at this point
Copy the full SHA b3106d7View commit details -
add EventuallyWithT assertion (#1264)
* add EventuallyWithT assertion * Change "EventuallyWithT" condition acceptance to no-errors raised This change updates the "EventuallyWithT" assertion variants (regular, formatted, requirement) to consider a condition as "met" if no assertion errors were raised in a tick. This allows to write easier conditions which simply contain assertions, without needing to return a bool. The equivalent of a condition returning true in the previous implementation would be a a condition with a single "assert.True(..)" call. * Declare the "Collect.Copy(T)" method as a testing helper * run go generate --------- Co-authored-by: Arik Kfir <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 4b2f4d2 - Browse repository at this point
Copy the full SHA 4b2f4d2View commit details
Commits on May 10, 2023
-
EqualExportedValues: Handle nested pointer, slice and map fields (#1379)
* EqualExportedValues: Handle pointer and slice fields * Update assert/assertions.go Co-authored-by: Michael Pu <[email protected]> * Reduce redundant calls to 'copyExportedFields' * Update comments * Add support for maps * Update Go version support to 1.19 and onward * Re-generate after rebasing --------- Co-authored-by: Michael Pu <[email protected]>
1Configuration menu - View commit details
-
Copy full SHA for 4c93d8f - Browse repository at this point
Copy the full SHA 4c93d8fView commit details
Commits on May 30, 2023
-
Configuration menu - View commit details
-
Copy full SHA for f97607b - Browse repository at this point
Copy the full SHA f97607bView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.8.2...v1.8.4