>But the PvdD, which has long opposed the experiment, has started a social media campaign raising its concerns about animal welfare, after a second cow fell into the water and had to be rescued on King’s Day. It is believed that the animal was crossing from the floating platform to a small area of grassland for the cows on the dockside, and could not climb out.
Oh bummer, it's really hard to get a cow crane on Kings day, they are all tied up rescuing drunks from the canals. Surge pricing, owch!
Most likely the latter. Thousands of bikes, a hundred people, and more than thirty cars fall in to Amsterdam canals each year. "What to do if your car falls in the water" is part of driver's ed.
When learning kayaking you have to practice a water escape, I wish there was something similar for driver's ed in the Netherlands. Thinking about it is terrifying.
I think it's relative, right? That's how abstractions and interfaces work.
I can write a module with integration tests at the module level and unit tests on its functions.
I can now write an application that uses my module. From the perspective of my application, my module's integration tests look like unit tests.
My module might, for example, implicitly depend on the test suite of CPython, the C compiler, the QA at the chip fab. But I don't need to run those tests any more.
In your case you hope the in-memory database matches the production one enough that you can write fast isolated unit tests on your application logic. You can trust this works because something else unit-tested the in-memory database, and integration tested the db client against the various db backends.
https://www.dutchnews.nl/2021/05/rotterdam-floating-farm-cri...