How familliar are the terms I used to you ?
Most were familiar; outside-in less so, collaboration tests, not at all.
Do you feel that TDD is strong in the community ?
Thats tough to answer, both because Rust is so young, and given the culture of the systems programming industry at large, which, IMHO, does not place nearly enough emphasis on testing at all, let alone TDD or BDD.
But overall, I’d say there is a healthy interest in the Rust community. I’ve found that the Rust community is a bit more receptive to doing things correctly, vs. just “getting it done”. That’s nice.
Recently I was looking for a mocking library for my project. I tried every one of them on crates.io, but found that most were not really suitable for a medium-to large-scale project.
The fact that there were choices available says something healthy about the community, so I’m optimistic. I settled on
galvanic-mock; together they let me write tests first, reduce boilerplate, and mock my dependencies.
The problem is, the IDE’s are not great at refactoring yet. I use JetBrains CLion with the IntelliJ Rust plugin. The test_suite! macro that
galvanic-test has me write my test in effectively disables all syntax checking. Any errors I generate are “somewhere” in the macro… tl;dr: there is quite a distance to go before I would consider the testing tools and development ecosystem to be at “1.0”, but we’re well on our way.
Would you be interested in reading a longer writeup on the above ?
Absolutely! Thank you for bringing up the topic–I think there are many of us who are always interested in learning new things from others who’ve faced similar challenges.