Print

Cucumber puts plain English on requirements



Alex Handy
Email
September 13, 2010 —  (Page 1 of 2)
Remember: Cucumbers are fruits, not vegetables. And businesspeople are suits, not programmers. For two years, the Cucumber project has sought to change that.

Originally created by Aslak Hellesoy as a rewrite of RSpec's Story Runner tools, Cucumber has matured enough for enterprise work. But can the suits be taught to use it properly?

The idea of plain-English requirements gathering tools is nothing new. Both Ravenflow and ThoughtWorks offer similar takes on requirement tools. Cucumber's take on the idea comes from the behavior-driven development world, however, and focuses on taking the task to the businesspeople inside their comfort zones.

But Ryan Smith, software developer at consulting firm Entryway, thinks that this is a nigh impossible task. “In all fairness, I don't think the intention was ever for businesspeople to be writing these, although they kind of marketed [Cucumber] that way,” he said.

“They should have correctly said it’s easy enough for people who don't know code to write this, because it's English. It's not code. I work on a project where I did have a client try to write requirements in Cucumber. That was an experiment we did for a week, and it didn't turn out well. I stopped doing that altogether.”

Smith feels it's better to gather requirements in person, then build the code from those spoken and written cues, rather than rely upon the businesspeople to write requirements in a special subset of English.

Overcoming people problems
Joseph Wilk, a contributor to the Cucumber project, said that many of the problems traditionally associated with getting technical contributions and buy-in from business folk can get in the way of successfully using Cucumber.

“There is more to this problem than just tools," he said. "If there is a people problem with businesspeople not wanting to engage in writing specifications, forcing a tool on them may be the wrong way to approach the solution and something Cucumber can do nothing about."

But as a Ruby developer, Smith sees little value in adding Cucumber to the requirements process. He said that using it adds another step to his development tasks.



Related Search Term(s): Cucumber, requirements

Pages 1 2 


Share this link: http://sdt.bz/34631
 
Most Read  Latest News  Resources

close
NEXT ARTICLE
Why system requirements are a dangerous illusion
The definition of requirements is flawed in such a way that it hinders our ability to properly see what a project needs Read More...
 
 
 




News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>

   
 
 

 


Download Current Issue
MAY 2013 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?