The RSpec Book

按有用程度 按页码先后 最新笔记

• 

  第56页

  _yuan_ (他们抽烟，不听音乐，是坏人。)

  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... (更多)

  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 somehow lifted and suddenly all of the code was my personal servant, ready and willing to bend to my will. It didn’t matter whether we were starting in a test, or in the code being tested. What mattered was that we started from the view of the code that was going to use the new code we were about to write. Over the years this has permeated my daily practice. It is very, very liberating, and results consistently in more usable APIs than I would have come up with starting with the object receiving the message. In retrospect, this also aligns closely with the Outside-In philos- ophy of BDD, perhaps taking it a step further. If the goal is to provide great APIs then the best place to design them is from their consumers.

  (收起)

  2012-01-12 16:49:25   回应

  收藏

  推荐
• 

  第34页

  无常之花盛开 (铜号吹响末人时代最后的黄金之阳)

  Chapter 3 Describe Features with Cucumber ======================================== Write software matters. And what matters depends on the context. User stories as planning tool: - have business value - be testable - be small enough to implement in one iteration Triad of BDD: - Acceptance Test Driven Planning - Domain Driven Design - Test Driven Development (更多)

  Chapter 3 Describe Features with Cucumber

  ========================================

  Write software matters. And what matters depends on the context.

  User stories as planning tool:

  - have business value

  - be testable

  - be small enough to implement in one iteration

  Triad of BDD:

  - Acceptance Test Driven Planning

  - Domain Driven Design

  - Test Driven Development (收起)

  2011-02-08 02:44:38   回应

  收藏

  推荐

• 

  第34页

  无常之花盛开 (铜号吹响末人时代最后的黄金之阳)

  Chapter 3 Describe Features with Cucumber ======================================== Write software matters. And what matters depends on the context. User stories as planning tool: - have business value - be testable - be small enough to implement in one iteration Triad of BDD: - Acceptance Test Driven Planning - Domain Driven Design - Test Driven Development (更多)

  Chapter 3 Describe Features with Cucumber

  ========================================

  Write software matters. And what matters depends on the context.

  User stories as planning tool:

  - have business value

  - be testable

  - be small enough to implement in one iteration

  Triad of BDD:

  - Acceptance Test Driven Planning

  - Domain Driven Design

  - Test Driven Development (收起)

  2011-02-08 02:44:38   回应

  收藏

  推荐
• 

  第56页

  _yuan_ (他们抽烟，不听音乐，是坏人。)

  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... (更多)

  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 somehow lifted and suddenly all of the code was my personal servant, ready and willing to bend to my will. It didn’t matter whether we were starting in a test, or in the code being tested. What mattered was that we started from the view of the code that was going to use the new code we were about to write. Over the years this has permeated my daily practice. It is very, very liberating, and results consistently in more usable APIs than I would have come up with starting with the object receiving the message. In retrospect, this also aligns closely with the Outside-In philos- ophy of BDD, perhaps taking it a step further. If the goal is to provide great APIs then the best place to design them is from their consumers.

  (收起)

  2012-01-12 16:49:25   回应

  收藏

  推荐

• 

  第56页

  _yuan_ (他们抽烟，不听音乐，是坏人。)

  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... (更多)

  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 somehow lifted and suddenly all of the code was my personal servant, ready and willing to bend to my will. It didn’t matter whether we were starting in a test, or in the code being tested. What mattered was that we started from the view of the code that was going to use the new code we were about to write. Over the years this has permeated my daily practice. It is very, very liberating, and results consistently in more usable APIs than I would have come up with starting with the object receiving the message. In retrospect, this also aligns closely with the Outside-In philos- ophy of BDD, perhaps taking it a step further. If the goal is to provide great APIs then the best place to design them is from their consumers.

  (收起)

  2012-01-12 16:49:25   回应

  收藏

  推荐
• 

  第34页

  无常之花盛开 (铜号吹响末人时代最后的黄金之阳)

  Chapter 3 Describe Features with Cucumber ======================================== Write software matters. And what matters depends on the context. User stories as planning tool: - have business value - be testable - be small enough to implement in one iteration Triad of BDD: - Acceptance Test Driven Planning - Domain Driven Design - Test Driven Development (更多)

  Chapter 3 Describe Features with Cucumber

  ========================================

  Write software matters. And what matters depends on the context.

  User stories as planning tool:

  - have business value

  - be testable

  - be small enough to implement in one iteration

  Triad of BDD:

  - Acceptance Test Driven Planning

  - Domain Driven Design

  - Test Driven Development (收起)

  2011-02-08 02:44:38   回应

  收藏

  推荐