• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Team education for Cucumber adoption

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"When we write these tests before development starts, we can explore and eradicate many misunderstandings long before they ooze their way into the codebase."

To me, these are wise words of one who has been through such projects. Although Cucumber is new to me, I see value in using it. It seems that teams need to learn the value, before adoption increases. Is this part of the problem around Cucumber and BDD? Are there project successes that I can use to educate others?



 
author
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Marty,

I regularly get involved with teams who are beginning a new project and want to make BDD-style collaboration a core part of their working practices. With a couple of days' training with the right person you can set the project out on a much better trajectory.

If it isn't possible to have me come to your workplace and convince people personally. there are loads of great success stories in Gojko Adzic's book, 'Specification by example'.
reply
    Bookmark Topic Watch Topic
  • New Topic