miniblog.

There are *so many* ways that reading a text file can fail. Maybe it doesn't exist, it's a broken symlink, it's actually a directory, it's not the encoding you expected, or perhaps you just don't have the correct permissions. Reporting good errors is surprisingly labour intensive.

I'm still experimenting with UIs for live (sandboxed) evaluation of tests. I've realised that you really want to highlight the failing assertion, not just the failing test. Feedback welcome :)

"Example Driven Development" using Glamorous and Pharo Smalltalk: https://medium.com/feenk/an-example-of-example-driven-development-4dea0d995920 Tests returning values and composing is a really interesting model. It establishes structure and shows which test failure is the most 'fundamental'.