joppiesaus / unit_test_battle_job_wouter

epic win

Table of Contents

• Kata Description
• Examples
• Win Conditions
• Rules
• Setup
• Usage
• Credits
• Resources
• License

A Codam Coding College unit battle session

Kata Description

Write a program that can calculate the score of a bowlingame.

The game consists of 10 frames. In each frame the player has two opportunities to knock down 10 pins. The score for the frame is the total number of pins knocked down, plus bonuses for strikes and spares.

A spare is when the player knocks down all 10 pins in two tries. The bonus for that frame is the number of pins knocked down by the next roll. So in frame 3 above, the score is 10 (the total number knocked down) plus a bonus of 5 (the number of pins knocked down on the next roll.)

A strike is when the player knocks down all 10 pins on his first try. The bonus for that frame is the value of the next two balls rolled.

In the tenth frame a player who rolls a spare or strike is allowed to roll the extra balls to complete the frame. However no more than three balls can be rolled in tenth frame.

There can be one or two rolls in a Frame. If the first roll makes all the pins fall, then there is no second roll. There is a Mark for each Frame that depends on the number of rolls and the total pins.

Examples

./bowling_game 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0; @echo All Gutter Balls
0
All Gutter Balls

./bowling_game 10 10 10 10 10 10 10 10 10 10 10 10; @echo Perfect Game
300
Perfect Game

./bowling_game 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9 1 9; @echo All Spares
190
All Spares

./bowling_game 9 0 9 0 9 0 9 0 9 0 9 0 9 0 9 0 9 0 9 0; @echo Nothing Special
90
Nothing Special

./bowling_game 10 10 10 10 10 10 10 10 10 10 9 1; @echo Almost Perfect
289
Almost Perfect

Invalid input should display Error

./bowling_game a 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 
Error

./bowling_game -1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 
Error

./bowling_game 11 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 
Error

Win Conditions

The code has to take in 0-21 valid bowling scores and calculate the appropiate scores

The code will be graded on a mix of the amount of % of coverage of your unit test, the amount of unit tests, the speed you completed the project and the cleanliness of your code base

The projects with the best scores will be graded by nicolas and a winner will be picked

The solution must be turned in before 4:30!

After which we'll return to the auitorium

Rules

Abide the rules of TDD at all times:

You are not allowed to write any production code until you have first written a failing unit test.

You are not allowed to write more of a unit test than is sufficient to fail– and not compiling is failing.

You are not allowed to write more production code that is sufficient to pass the currently failing unit test.

You will work in a team of 4 people in which you will first decide how you are going to split the project into multiple components, after which you'll split the team into two pairs. Divide the components between the two pairs. You will alternate between navigating, writing a test case, and driving, making the test pass in the following cycle:

• The first person will write a test case
• The second person will make the test pass
• The second person will make the next test case
• The first person will make the test case pass
• repeat! Good communication will be of utmost importance!

Setup

Run the following command before starting your project or add these commands to your .zsh or .bashrc

export LIBRARY_PATH=/sgoinfre/criterion_test/.brew/lib:${LIBRARY_PATH}
export C_INCLUDE_PATH=/sgoinfre/criterion_test/.brew/include:${C_INCLUDE_PATH}

Alternatively run the bash script inside the folder

bash environment.sh

Usage

Compile the project

make

Recompile the project

make re

Run all of the tests.

make tests_run

Recompile your tests.

make re_tests

Find leaks in your program

make fsan

Compile a debuggable executable

make debug

Debug your program

lldb bowling_game
b main
r
gui

Credits

• @PanoramixDeDruide - for creating the acceptance test and the criterion installation
• @lgutter - for helping setting up the boiler plate code and thinking of the concept
• @FreekBes - for trying to make criterion available throught the software manage center
• Kenpugh
• Uncle Bob
• Code Wars

Resources

• Eptiech 2022 Technical Doc
• Code Wars Criterion Docs
• Criterion
• Criterion Docs

License

The MIT License (MIT)

Copyright (c) 2021 Saladin Lorenzo Afoh

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.