Joakim Rosendahl
@kimmen.bsky.social
Software developer since 2005, focused on building solution with better user experience. Recreational tennis player who picked up the game in 2020. Gamer at heart, soft spot for single player RPGs, but mostly a family man and father nowadays.
One method I haven't really looked into replacing yet is Should().BeEquivalentTo(new { ... }) that we use quite often.
January 30, 2025 at 2:29 PM
One method I haven't really looked into replacing yet is Should().BeEquivalentTo(new { ... }) that we use quite often.
Done it for a couple of our projects. Mostly you can do replace `Should().` with `Should`, ex: FA:s Should().BeTrue() can be replaced ShouldBeTrue() in Shouldly. There are some methods no available in Shouldly though, like stream.Should().BeReadable().
January 30, 2025 at 2:27 PM
Done it for a couple of our projects. Mostly you can do replace `Should().` with `Should`, ex: FA:s Should().BeTrue() can be replaced ShouldBeTrue() in Shouldly. There are some methods no available in Shouldly though, like stream.Should().BeReadable().
I think for an assertion library it's quite expensive, especially when it's a cost per developer and year! We are moving to Shouldly instead: easy enough conversion.
January 17, 2025 at 1:57 PM
I think for an assertion library it's quite expensive, especially when it's a cost per developer and year! We are moving to Shouldly instead: easy enough conversion.