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
containExactly* assertions don't respect given verifier #3970
Comments
yes - I've noticed that too: as a result of the discussion there, we should take out custom verifier. |
It would be better to remove the custom verifier than to leave things as they are. But it would be really nice if there was a way to support custom verification with these assertions. We use custom verifiers a lot because our domain objects contain randomly generated IDs and we want to exclude those for testing |
Makes sense. I'm working on a fix, keeping the signature as is. |
the fix only for |
Which version of Kotest are you using
Using Kotest 5.8.0.
containExactly
andcontainExactlyInAnyOrder
takes a verifier parameter, but doesn't respect it in the matching logic. For example, the first two of these tests fail when they should pass:The text was updated successfully, but these errors were encountered: