4 ms·
I’m not sure I take from this what your complaint is. You don’t like the way that it looks? Or reads? Or is there a functional complaint I’m missing? It looks
by tsuujin 3y ago
I’m not sure I take from this what your complaint is. You don’t like the way that it looks? Or reads? Or is there a functional complaint I’m missing?
It looks like a pretty standard builder pattern to me.
It may help if you give examples. What language allows an integration test in two lines of code? Can you show me the code? Can you show me the same integration test in rspec so we can see how it is empirically worse?
I’ve done testing in a dozen or so languages/frameworks at this point, and they’ve all felt about the same (except JS, which felt like pulling teeth back when I was doing it). Rspec never struck me as particularly bad, unless you’re looking at intentionally hyperbolic examples.
- bitwize 3y ago> You don’t like the way that it looks? Or reads? Or is there a functional complaint I’m missing? It looks twee, is much more to type, and doesn't get you anything that an assertion-based framework doesn't have except aEsThEtIcS. I loathe the prospect of having to write line after line of that when simple assertions would do the exact same thing just as well. > What language allows an integration test in two lines of code? I worked on QRes (ITA Software's reservation system) as a contractor. The integration tests were written in a custom sexpr-based language that was interpreted by the testing framework. You could specify a template that was filled in with generated sample data, and a spec against which the XML response would be checked, and the framework would run the query, get the response, and show you where any part of it differed from the spec. This is proprietary stuff, so I can't show it to you, but it's one of the reasons why QRes is the most elegant enterprise program I'd ever seen, and a joy to maintain. Too bad it had the plug pulled midway through my contract...