The original idea for the kata was created by Krzysztof Jelski at 'Session on the Software Craftsmanship UK 2011 conference' (How Object-Oriented Are You Feeling Today?). This version is done by obbeying as much [calisthenics rules] (http://www.cs.helsinki.fi/u/luontola/tdd-2009/ext/ObjectCalisthenics.pdf) as possible.

Acceptance test is created with [SpecFlow] (http://www.specflow.org/), [NSubstitute] (http://nsubstitute.github.io/) was used for mocking, and MSTest for unit tests.

Below is the description from [Sandro's Git repository] (https://github.com/sandromancuso/Bank-kata):

Think of your personal bank account experience When in doubt, go for the simplest solution

Deposit and Withdrawal
Transfer
Account statement (date, amount, balance)
Statement printing
Statement filters (just deposits, withdrawal, date)

1. One level of indentation per method
2. Don’t use the ELSE keyword
3. Wrap all primitives and Strings
4. First class collections
5. One dot per line
6. Don’t abbreviate
7. Keep all entities small (50 lines)
8. No classes with more than two instance variables
9. No getters/setters/properties

• Object Calisthenics pdf
• Object Calisthenics (full book), Jeff Bay in: The ThoughtWorks Anthology. Pragmatic Bookshelf 2008
• Original idea for the kata: How Object-Oriented Are You Feeling Today? - Krzysztof Jelski (Session on the Software Craftsmanship UK 2011 conference)

Started from defining an acceptance test:

Given a client makes a deposit of 1000 on 10-01-2012
And a deposit of 2000 on 13-01-2012
And a withdrawal of 500 on 14-01-2012
When she prints her bank statement
Then she would see
date || credit || debit || balance
14/01/2012 || || 500.00 || 2500.00
13/01/2012 || 2000.00 || || 3000.00
10/01/2012 || 1000.00 || || 1000.00