qharper

Yeah, the only case I've personally seen them paying off when you're using them as more of an integration test -- i.e. the component under test is a large complex one, containing many sub-components, and you want to make sure they integrate well together -- but setting up the various cases is easier at a component level than in a full ETE test (e.g. maybe render it over a list of data/prop examples and check it renders as expected). But this is relatively rare.

Runnable has one of the most beautiful APIs I’ve seen — everything is very carefully designed from the users perspective to make it as easy as possible. At the same time very flexible and powerful.