I used to think Rust testing was far behind Python with pytest, but that’s not really the case. There's a googletest crate that fixes so many pain points: clearer failure messages, test fixtures, approx comparisons for floats, and more.
If you write tests in Rust, it’s worth giving this crate a try. I'm surprised it isn’t more widely used, because it makes the testing experience much smoother.
The CLion 2025.2 Early Access Program Is Open
#Clang #CLion #Eap #News #Clionnova #Cmake #Googletest
A multi-part series of #LinkedIn posts (ugh!) by the creator of the #GoogleTest framework on the fall of #Google:
“The Wasted Times Of Google – Part 1”, Zhanyong Wan (https://www.linkedin.com/pulse/wasted-times-google-part-1-zhanyong-wan-jzerc).
Anyone here a #googletest #gtest contributor and willing to take a look at my PR? Boosts very welcome :3
Allowing custom gtest_main implementations to instantiate the XmlUnitTestResultPrinter with either a given file path or any other kind of std::ostream to write to. This is useful for e.g. embedded ...
Okay, so when using #gtest / #gmock / #googletest to write C++ unit tests for code that uses dependency injection, how the *hell* do go about mocking dependencies of a class under test without having to mock the dependency class' dependencies, and *those* class' dependencies, and so on until you've mocked every class in the dependency tree of the class under test?
"Interfaces" or "templates" are *not* valid answers, as they drive complexity into your non-test code purely to support testing!
Ihor Kalnytskyi
CLion Blog
रञ्जित (Ranjit Mathew)
Saphira Lohikäärmekettunen 
🚫 KubeCon Europe
Ben S.