Behaviour Driven Development is about writing software that matters. It is an approach to agile software development that takes cues from Test Driven Development, Domain Driven Design, and Acceptance Test Driven Planning.
RSpec and Cucumber are the leading Behaviour Driven Development tools in Ruby. RSpec supports Test Driven Development in Ruby through the BDD lens, keeping yo...
Behaviour Driven Development is about writing software that matters. It is an approach to agile software development that takes cues from Test Driven Development, Domain Driven Design, and Acceptance Test Driven Planning.
RSpec and Cucumber are the leading Behaviour Driven Development tools in Ruby. RSpec supports Test Driven Development in Ruby through the BDD lens, keeping your focus on design and documentation while also supporting thorough testing and quick fault isolation. Cucumber, RSpec's steadfast companion, supports Acceptance Test Driven Planning with business-facing, executable requirements documentation that helps to ensure that you are writing relevant software targeted at real business needs.
The RSpec Book will introduce you to RSpec, Cucumber, and a number of other tools that make up the Ruby BDD family. Replete with tutorials and practical examples, the RSpec Book will help you get your BDD on, taking you from executable requirements to working software that is clean, well tested, well documented, flexible and highly maintainable.
作者简介
· · · · · ·
David Chelimsky is the lead developer/maintainer of RSpec. He has been developing software for nearly a decade, and exploring TDD for over five of those years. After three years training and mentoring agile teams at Object Mentor, David currently leads the software development team at Articulated Man, a Chicago based, interactive design firm. In his spare time, David likes to p...
David Chelimsky is the lead developer/maintainer of RSpec. He has been developing software for nearly a decade, and exploring TDD for over five of those years. After three years training and mentoring agile teams at Object Mentor, David currently leads the software development team at Articulated Man, a Chicago based, interactive design firm. In his spare time, David likes to play guitar, travel, and speak something resembling Portuguese.
Dave Astels is a Software Engineer at Engine Yard and has been involved with software and computing for over 25 years, recently having spent several years working exclusively with Ruby and Rails. Dave wrote the article that prompted Steven Baker to start the RSpec project.
Bryan Helmkamp is the lead maintainer of Webrat, a library to implement acceptance testing of a Ruby web application in a more expressive and maintainable way. Following three years of Ruby on Rails consulting, Bryan is now a software engineer at Weplay, a New York City-based startup building online tools for the youth sports community.
Dan North works with technology consultancy ThoughtWorks where he delivers software, coaches development teams, and hangs out at conferences. In 2003 and 2004 he developed the idea of Behaviour Driven Development and delights in the community that has grown up around RSpec and the enthusiasm and dedication of their core contributors.
Zach Dennis is a lead developer and co-founder of Mutually Human Software, a Grand Rapids, MI based web development consultancy. He has been enjoying Ruby for nearly 7 years and has contributed to several projects such as Ruby's standard library documentation, Ruby on Rails, and RSpec. In his spare time, Zach loves spending time with his wife, reading, listening to music, and running continuousthinking.com.
Aslak Hellesoy is the Chief Scientist of BEKK Consulting, a Norwegian business and technology consulting firm. In 2003, after seven years of Java programming, he fell in love with Ruby. He has contributed to dozens of open source projects and is the founder of the Cucumber project. Aslak likes to cook, ski, and travel.
原文摘录
· · · · · ·
The Code You Wish You Had
In my early days at Object Mentor I attended a TDD class being
taught by James Grenning. As he was talking about refactoring
a Long Method, he wrote a statement that called a method
that didn’t exist yet, saying something like “start by writing the
code you wish you had.”
This was a galvanizing moment for me.
It is common to write the code we wish we had doing TDD. Per-
haps we send a message from the code example to an object
that does not have a corresponding method. We let the Ruby
interpreter tell us that the method does not exist (red), and then
implement that method (green).
Doing the same thing within application code, calling the code
we wish we had in one module from another module, was a
different matter. It was as though an arbitrary boundary was
someh... (查看原文)
So, now you know three ways to identify pending examples, each of
which can be helpful in your process in different ways:
• Add pending examples as you think of new examples that you
want to write.
• Disable examples without losing track of them (rather than commenting
them out).
• Wrap failing examples when you want to be notified that changes
to the system cause them to pass.
Now that you know how to postpone writing examples, let’s talk about
what happens when you actually write some! (查看原文)
码农与厨子
0 有用 xiaohanyu 2016-01-04 23:58:15
扫了一晚上，感觉略复杂呀，解决一个问题的同时又带来了很多别的问题。很怀疑真的有人去看那些 features 代码吗？管理人员应该直接看测试是否通过就 OK ，至于程序员自己，还是怎么方便怎么来比较好吧？先写 scenario ，再 step ，再写 code 很累的呀。看了 http://brandonhilkert.com/blog/7-reasons-why-im-sticking-with-... 扫了一晚上，感觉略复杂呀，解决一个问题的同时又带来了很多别的问题。很怀疑真的有人去看那些 features 代码吗？管理人员应该直接看测试是否通过就 OK ，至于程序员自己，还是怎么方便怎么来比较好吧？先写 scenario ，再 step ，再写 code 很累的呀。看了 http://brandonhilkert.com/blog/7-reasons-why-im-sticking-with-minitest-and-fixtures-in-rails/ ，决定还是不用了，跟随 DHH 大神，守着 minitest 吧。 (展开)
0 有用 WolfLee 2013-12-31 12:16:47
太冗了，留存当参考书吧。
0 有用 微客 2013-06-04 11:25:36
让测试更加贴近实际
0 有用 二把刀程序员 2013-04-05 15:37:10
这本书系统介绍了 cucumber, rspec 的使用。适合用几天时间来阅读而不是去网站上速成
0 有用 机械唯物主义 2013-07-02 22:35:31
用cucumber做BDD的好处，在于清晰地用自然语言描述出来了业务逻辑，然后映射成测试代码。这样解决了TDD业务逻辑混杂在测试代码里面的问题。但是BDD增加了语言映射到代码的层面，显得很繁琐，并不是很适合只有程序员存在的场合。
0 有用 狂气之瞳改 2018-05-18 15:28:07
10年的老书，blog+tutorial+api doc。直接读官网文档就够了。
0 有用 xiaohanyu 2016-01-04 23:58:15
扫了一晚上，感觉略复杂呀，解决一个问题的同时又带来了很多别的问题。很怀疑真的有人去看那些 features 代码吗？管理人员应该直接看测试是否通过就 OK ，至于程序员自己，还是怎么方便怎么来比较好吧？先写 scenario ，再 step ，再写 code 很累的呀。看了 http://brandonhilkert.com/blog/7-reasons-why-im-sticking-with-... 扫了一晚上，感觉略复杂呀，解决一个问题的同时又带来了很多别的问题。很怀疑真的有人去看那些 features 代码吗？管理人员应该直接看测试是否通过就 OK ，至于程序员自己，还是怎么方便怎么来比较好吧？先写 scenario ，再 step ，再写 code 很累的呀。看了 http://brandonhilkert.com/blog/7-reasons-why-im-sticking-with-minitest-and-fixtures-in-rails/ ，决定还是不用了，跟随 DHH 大神，守着 minitest 吧。 (展开)
0 有用 风吹起 2015-07-17 22:05:05
Pragmatic的经典入门系列，如果把技术书分为，入门，中级（偏向性能，优化，实现），高级（主要就是优化，怎么避免坑），总结（语言特性，Design，Pattern），经典（几十年不过时的），暂时把书分为低，中，高，经典，总结，这门书属于TDD的入门书，还需要大量事件才能记住TDD中的技术实现和原理。
0 有用 木易 2015-06-24 08:38:09
BDD 大法好
0 有用 zhaqiang 2015-01-25 22:41:01
嗯，其实看的是 "Everyday Rails Testing with RSpec"，但是豆瓣不能添加那本书，就用这本做记录吧，哈哈。