Cucumber is a very good tool for achieving functional testing. However your cuke suite can become unwieldy very soon. Even a little bit of indiscipline can lead to huge build times, with random failures. Over time, maintaining and writing the cukes starts costing more than the benefit derived out of it. On the other hand, you can start ignoring your functional build only to discover some nasty bug later which your poor cuke suite was telling you.
In this presentation we try and look at what can be done to avoid this and derive complete value from cukes. We share experiences and learnings about cuking the right way from real projects
1) best practices of writing and maintaining cukes
2) some new things that could be tried out with cukes to make them more reliable and valuable.