What I’m here to convince you of today is that this principle applies additionally to error types: that is, error types should be located near to their unit of fallibility. To illustrate this point, I will follow the initial development and later API improvement of a hypothetical Rust library.
Source: Modular Errors in Rust, an article by Sabrina Jewson.
The integration tests are most effective way to test your application. Those tests are usually written by the developers themselves. The purpose of this tutorial is to show you how easy and efficient it is to write integration tests with
dockertest.
Source: Write integration tests with dockertest in Golang, an article by Roman Kiselenko.
If you’re used to writing unit tests, you might already know that when you’re testing a function with parameters, you want to test it using many (or ideally, all) possible inputs. That is to ensure that the function is doing what we want for anything we decide to throw at it. However, if we’re repeating the same pattern of set up data – run function – expect certain result for writing unit tests, an undesirable pattern could potentially emerge.
Source: Write Cleaner Unit Tests Using Parameterization, an article by Teagen Kiel.
Which is better, Rust or Go? Go or Rust? Which language should you choose for your next project in 2023, and why? How do the two compare in areas like performance, simplicity, safety, features, scale, and concurrency? What do they have in common, and where do they fundamentally differ? Let’s find out, in this friendly and even-handed comparison of Rust and Golang.
Source: Rust vs Go in 2023, an article by John Arundel.
Recuperating from trauma, Jennifer remains in danger as she returns to a life she doesn't remember.
In the evening Alice, Esme, and I watched Secret Obsession. The movie was OK and I give it a 6 out of 10.