On 02/07/15 14:28, Dicebot wrote:
Neither. But with the second one I at least have a chance to figure out what it actually tests. To understand the first one I'd need to read the code of that custom matcher.
Once you know what a matcher does or how it's used it's a lot more readable and easier to create new tests.
This is exactly the problem with all that fancy - library/app author (who by definition knows the domain well) implicitly introduces custom DSL and expects everyone (who, by definition, have very vague understanding of domain) to be able to read it as comfortably as himself.
By that definition we should all write object oriented code in C. Heck, why don't we just use assembly and be done with it.
-- /Jacob Carlborg
