"Color Coded Race Track" by Simpsons contributor is licenced under is licenced under Wikimedia Commons
Available here
Bottom-up style is when you build a brick outside your main acceptance test flow and only later integrate it with the rest of the program. On the contrary, Top-down style is when you only work on the code that is covered by the acceptance or high level tests.
In order to experiment full bottom-up style start the kata with 10 minutes of up-front design and come up with the different 'bricks' you will need to solve the problem. Then use the bottom-up way to solve the kata:
- Write an acceptance test, and comment it
- Test drive the implementation of each brick
- Using all the bricks, test drive the implementation of the main function
- Uncomment and pass your acceptance test
Note: Bottom-up / Top-down are also known as Inside-out / Outside-in
- It lets you work in small steps
- It tends to result in more reusable and robust bricks
- There is a risk that the brick does not integrate well with the main code, leading to a lot of rework. Then a good recommendation is to integrate the brick as soon as possible in the main code.
- Creating a robust brick is often more work than necessary for the current acceptance test
You can fill it from here
- Wikipedia - Conway's Game of Life
- Conway's Game of Life online editor
- TDD - From the Inside Out or the Outside In? by Georgina McFadyen
- TCR (Test && Commit || Revert) wrapper utility
- Collaborative timer for pairing or mobbing: mobti.me or agility timer
- 2-hour Randori Kata
- Bottom-up TDD
- Test readability
- Teamwork
- ⚠ YAGNI
Kata-GameOfLife and the accompanying materials are made available
under the terms of the MIT License which accompanies this
distribution, and is available at the Open Source site
See ACKNOWLEDGEMENTS.md for more information.
Damien Menanteau |
Ahmad Atwi |
Philippe Bourgau |
AntoineMx |