3 ms·
i certainly agree that there are a lot of extra sources for error using Cucumber, and learning the regexp-style programming and syntax was a pain. one of the t
by jdp23 16y ago
i certainly agree that there are a lot of extra sources for error using Cucumber, and learning the regexp-style programming and syntax was a pain.
one of the things I like a lot about Cucumber is having precise definition of stories in a way that I can discuss with actual users. in a Steak world, what mechanisms get used for that?
- swombat 16y agoMy cofounder is reasonably technically minded (for a business guy), and yet I've never seen him glance at more than the headline description of a test. Steak provides those. The actual steps of the test are just implementation details. The headline should say what the test does, reasonably precisely.
- bphogan 16y agoI routinely write plain-text with my clients and stakeholders - they like cucumber. I could not show them Steak. When working with end users Cucumber works really really well for me. However, the idea of Steak on projects where I'm the stakeholder, or only developers are working on a team, seems like a nice idea because it is less maintenance.
- jdp23 16y agoi use Cucumber for behavior definitions, not tests ... and for me it's very useful to be able to discuss this with a non-technical person. "is this how you'd go about accomplishing something? is this how you'd expect the system to behave if you do X?" [which isn't to downplay the value of tests, those are important too, and I could see Steak potentially adding value on that front]