10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
Presentation
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
Cucumbered
Presented by
Joseph Wilk
on
Oct 08, 2009
Length 00:26:20
How would you like to view the presentation?
In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
In this talk from FutureRuby, Joseph Wilk gives an introduction to the BDD framework Cucumber and gives valuable tips for getting it adopted and used by customers and developers.
Bio
Joseph Wilk is a member of the core development team for Cucumber along with Aslak Hellesøy. He has been developing for the web for 10 years in both big and small companies and as an entrepreneur. After stints working with Java and Python he found Ruby. He now spends his time having more fun than is healthy working as a Software Gardener building web systems and working on open source projects.
About the conference
FutureRuby isn't a Ruby conference, but a conference for Rubyists. This is a call to order - a congress of the curious characters that drew us to this community in the first place. We have a singular opportunity to express a long-term vision, a future where Ruby drives creativity and prosperity without being dampened by partisan politics.
In this talk from FutureRuby, Joseph Wilk gives an introduction to the BDD framework Cucumber and gives valuable tips for getting it adopted and used by customers and developers.
Bio
Joseph Wilk is a member of the core development team for Cucumber along with Aslak Hellesøy. He has been developing for the web for 10 years in both big and small companies and as an entrepreneur. After stints working with Java and Python he found Ruby. He now spends his time having more fun than is healthy working as a Software Gardener building web systems and working on open source projects.
About the conference
FutureRuby isn't a Ruby conference, but a conference for Rubyists. This is a call to order - a congress of the curious characters that drew us to this community in the first place. We have a singular opportunity to express a long-term vision, a future where Ruby drives creativity and prosperity without being dampened by partisan politics.
RelatedVendorContent
Transforming Software Delivery: An IBM Rational Case Study
Five Key Practices to Agile ALM
Agility at scale, become as agile as you can be
Related Sponsor
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
- This article is part of a featured topic series on Agile
- See more Agile content at: http://www.infoq.com/agile
- Other recent content items in this topic
Comparison with other tools?
by
Vijay Nathani
Posted
Re: Comparison with other tools?
by
Joseph Wilk
Posted
Re: Comparison with other tools?
by
Wes Williams
Posted
-
How would Cucumber compare with Concordion? I think both offer very similar features.
Both are different from tools like Fit / Fitnesse, which (primary use tables and) do not offer description that is totally decoupled from the implementation.
Thanks. -
Cucumber takes the perspective that the specification should just be plain text that can be edited by anyone (non-technical people included). Concordion uses HTML in the specifications along with method calls/test logic. So the specifications require either editor tools or some pre-defined knowledge of HTML and programming. Cucumber keeps this logic out of the specification by using regular expressions to provide mappings to the test logic.
So Cucumbers Gherkin grammar has been built up around expressing specifications and functionality through something everyone can understand, plain text. Concordion hands this task over to programming code and HTML.
That feels like the key difference between the two. -
I have been working on a tool to make FitNesse have a bit more of a Cucumber feel. Cucumber was the inspirations for the tool. It is called GivWenZen and is hosted at google code. I work with a lot of teams that use FitNesse and it is easier to let them stay in that tool then trying to convince them to move to Cucumber.
I agree that Cucumber frees you up to express the specification and functionality better that the more technical type tools. With the GivWenZen tool it is a bit of hybrid. You are still bound to tables but I simplified it a bit.
|give|some sentence that describes your functionality|
With a small CSS change you can make the table borders go away and have it more readable. It is not perfect but it does help. There is another tool with a similar goal called NarrativeFixure.
3 comments
Watch Thread Reply