From 26b570c8531392979bc21cb71a7decb7c7b8173b Mon Sep 17 00:00:00 2001 From: bkleinen Date: Fri, 18 Oct 2024 06:50:08 +0000 Subject: [PATCH] refs/tags/v2.5 misc 8558c2ebfde9e94378b04d6108061e99541da191 --- classes/ws2024/m1/labs/kata/index.html | 5 ++++- index.html | 2 +- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/classes/ws2024/m1/labs/kata/index.html b/classes/ws2024/m1/labs/kata/index.html index dbb53994e..835a11e06 100644 --- a/classes/ws2024/m1/labs/kata/index.html +++ b/classes/ws2024/m1/labs/kata/index.html @@ -16,7 +16,10 @@ the tests in an extra shell window outside the ide most useful for that - see the testloop.sh script in my python-kata scaffold: https://github.com/htw-imi-media-programming/kata-scaffold

The Kata is described here: https://codingdojo.org/kata/FizzBuzz/

If you are new to automated testing, just do TDD. If you feel slightly bored, -add the Baby Steps constraint: https://kata-log.rocks/baby-steps.

Start with the Requirement for Stage 1:

Write a program that prints the numbers from 1 to 100. But for multiples of three print “Fizz” instead of the number and for the multiples of five print “Buzz”. For numbers which are multiples of both three and five print “FizzBuzz “.

Work Test Driven: Write a failing test, implement it in the most simple way, then refactor if necessary. Avoid unnecessary abstractions and generalizations, though.

Add Stage 2 Functionality:

Refactor.

Add new Requirements

We will define a new Requirement in Class. Write a Test. Implement it. Refactor.