Jul 3, 2026, 9:10 AM- Jul 3, 2026, 9:10 AM
Replies
- Jul 3, 2026, 4:04 PM
also love that "cargo test" is built-in. (first time I've seriously done this in a project :P).
when a test fails I think "yes! that saved me another hour or two of debugging!" and I take a nap.
Jul 3, 2026, 9:35 AM@hbons I'm always astonished when some of our gnome friends tell me that cargo is horrible in their opinion
- Jul 3, 2026, 9:37 AM
@zeenix I agree on the build.rs part, but I don’t use that. :)
- Jul 3, 2026, 10:00 AM
@hbons yeah, I try to avoid that too but it's not always possible. I think for apps, it's fine. In libraries you hardly ever need it anyways.
laundlaund@wetdry.worldJul 3, 2026, 10:49 AM- Jul 3, 2026, 11:12 AM
MostlyBlindGamerMostlyBlindGamer@dragonscave.spaceJul 3, 2026, 5:18 PM@hbons Rust makes testing incredibly smooth for a solo developer. I write a lot of tests for .NET, sure, but that’s because I have a whole internal testing framework I can use.
You can get to that low friction point in any stack, I suppose, but cargo definitely makes it take less effort. That means it makes it more natural to shift left.
- Jul 3, 2026, 5:19 PM
@MostlyBlindGamer that's what always kept me from doing it. already choice paralysis picking a testing framework...
- MostlyBlindGamerMostlyBlindGamer@dragonscave.spaceJul 3, 2026, 5:26 PM
@hbons we have a whole domain-oriented framework, so TDD with integration tests is actually worth considering. Just don’t ask how much it cost to get there.
Unit tests in Rust come super naturally. Big integration stuff, less so, at least for me. - Jul 3, 2026, 5:27 PM
@MostlyBlindGamer right, still need to do the integration tests. I think these will just be simple CLI scripts. any recommendations?
- MostlyBlindGamerMostlyBlindGamer@dragonscave.spaceJul 3, 2026, 6:10 PM
@hbons not really… I guess all you need for your asserts is the odd ls or hash, right?
That feels doable in some kind of containerized fashion.