Alex Kuznetsov
Alex Kuznetsov
> I believe this would be valuable, yes. Even if we have to add a lot more test cases, having a clear vision of assertion failures is great! > >...
https://github.com/kotest/kotest/pull/3796
Personally I feel the following code would be confusing to me, as well as to most developers: `val game = Game("Risk", listOf("p1", "p2", "p3", "p4")).shouldNotContainDuplicates()` should I ever encounter that,...
I can take care of that. Thank you for calling it out!
the PR to fix it: https://github.com/kotest/kotest/pull/3965
yes - I've noticed that too: https://github.com/kotest/kotest/issues/3840 as a result of the discussion there, we should take out custom verifier. What do you think?
> 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...
the fix only for `containExactlyInAnyOrder` - the other matcher `containExactly` clearly has issues, will be fixed separately https://github.com/kotest/kotest/pull/3976
> fix documentation, table for date matchers where broken can you share some details?
> I'm not sure it should be incorporated to the core code. > > It would need maintenance to something we try the best we can to avoid: bringing mocking...