public
Description:
Homepage:
Clone URL: git://github.com/coreyhaines/kata-codebreaker-marker.git
name age message
file .document Sun Nov 01 08:09:46 -0800 2009 Initial commit to codebreaker_marker. [coreyhaines]
file .gitignore Sun Nov 01 08:09:46 -0800 2009 Initial commit to codebreaker_marker. [coreyhaines]
file LICENSE Sun Nov 01 08:09:46 -0800 2009 Initial commit to codebreaker_marker. [coreyhaines]
file README.rdoc Sun Nov 01 14:24:50 -0800 2009 README [coreyhaines]
file Rakefile Sun Nov 01 08:09:46 -0800 2009 Initial commit to codebreaker_marker. [coreyhaines]
directory features/ Sun Nov 01 14:17:44 -0800 2009 Added feature/scenarios for code breaker commi... [coreyhaines]
directory lib/ Sun Nov 01 14:17:44 -0800 2009 Added feature/scenarios for code breaker commi... [coreyhaines]
directory spec/ Sun Nov 01 08:16:17 -0800 2009 update names [coreyhaines]
README.rdoc

Kata repository for Codebreaker Marker

This is a repository that can be used as a starting point for doing the Codebreaker Marker code that is outlined in the RSpec book (pragprog.com/titles/achbd/the-rspec-book).

There are 4 main branches:

  • master This is a set of cucumber features
  • spec_list This is a list of pending rspec examples
  • specs This is a list of implemented rspec examples
  • reference_implementation This is a reference implementation of the algorithm.

How to use this

Please fork this repository and work on this kata as a way to practice. There are 3 different ways that I recommend using this repository:

  • Writing implementation code Create a branch based on the existing ‘specs’ branch, add your own implementation for the given specs.
  • Writing examples Create a branch based on the existing ‘spec_list’ branch, add your own examples for the given descriptions.
  • Writing example descriptions Create a branch based on the existing ‘master’ branch, add your own examples for the given cucumber scenarios.

Note on Patches/Pull Requests

If you notice anything wrong, please follow the instructions below to contribute your ideas / fixes:

  • Fork the project.
  • Make your feature addition or bug fix.
  • Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Send me a pull request.

Copyright

Copyright © 2009 Corey Haines. See LICENSE for details.