2 ms·
I get by just fine with Test::Unit too. RSpec smelled like gratuitous complexity from the get-go. Wasn't the whole point of Rails to get back to doing things si
by cageface 16y ago
I get by just fine with Test::Unit too. RSpec smelled like gratuitous complexity from the get-go. Wasn't the whole point of Rails to get back to doing things simply?
- jacques_chester 16y agoI'm ambivalent about RSpec, but the concept of a structured requirements language (which is front-end of Cucumber) is a good one. Cucumber grew out of testing; it'd be interesting to see the problem approached from the other end. Suppose you were designing a language, ab initio, for sharing requirements with end-users. What would it look like? I've seen Steve McConnell mention "Planguage" by Tom Gilb, but online resources are scarce.
- cageface 16y agoI have never, personally, worked with a client that was willing to work consistently at the level of detail that Cucumber provides. I suppose if I had such a client I might find it useful. For communicating requirements among developers I think plain Ruby is already readable enough.
- jacques_chester 16y agoWhat level of detail do you use with clients?
- cageface 16y agoWireframes for UI, informally written use cases for features. I try to get working prototypes up on screen as quickly as possible.
- sunkencity 16y agoBest thing about cucumber is the possibility to set up a matrix of conditions and run through the scenarios that way - can be used as a poor mans quickcheck. https://github.com/aslakhellesoy/cucumber/wiki/scenario-outlines https://github.com/aslakhellesoy/cucumber/wiki/scenario-outl...