Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You definitely want to look at Extreme Programing (XP), take a look at Kent Beck's <em><a href="http://rads.stackoverflow.com/amzn/click/0321278658" rel="nofollow">Extreme Programming Explained: Embrace Change, 2nd Edition</a></em> </p> <p>The most useful thing you can do though is to do some research on <a href="http://behaviour-driven.org/" rel="nofollow">Behaviour-Driven Development</a> which is basically Test-Driven Development done right. It takes the focus off of tests and back onto specifications. You don't worry about what classes do so much as what behavior your program exhibits.</p> <p>So saying you aren't going to use TDD, or BDD, is just plain crazy talk. One of the core concepts of Agile development is developing your software from your tests/specs. You have to get out of the mindset that tests/specs are testing your classes. That's not really what they're for. They are for describing the behaviors your application should exhibit then using that test/spec to write the behavior into your application.</p> <p>You might write something like this</p> <pre><code>Describe Startup it "should display a welcome screen" do game = Game.new game.start game.output_buffer.should match("Welcome") end end </code></pre> <p>Then you go write the code to make it happen. You describe the code you want, then you go write it. It allows you to write your code in little, bite sized chunks and best of all when someone else picks up your code they can run the tests and see that everything works. When they want to add new functionality they use the same process so now when you go back to the code you can have faith that their code works too.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload