From 0201d9ab7db8c519710094f6cdd3eb57b1bc9c44 Mon Sep 17 00:00:00 2001 From: Pietro Di Bello Date: Sun, 24 Jan 2016 22:58:21 +0100 Subject: [PATCH 1/2] Update URL for a blogpost linked in the README Update URL for the "Writing Good Tests for the Gilded Rose Kata" post --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 423c33da..2621bb30 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ As Bobby Johnson points out in his article ["Why Most Solutions to Gilded Rose M better practice at handling a legacy code situation if you do this Kata in the original C#. However, I think this kata is also really useful for practicing writing good tests using different frameworks and approaches, and the small changes I've made help with that. I think it's also interesting to compare what the refactored code and tests look like in different programming languages. -I wrote this article ["Writing Good Tests for the Gilded Rose Kata"](http://emilybache.blogspot.se/2013/03/writing-good-tests-for-gilded-rose-kata.html) about how you could use this kata in a [coding dojo](https://leanpub.com/codingdojohandbook). +I wrote this article ["Writing Good Tests for the Gilded Rose Kata"](http://coding-is-like-cooking.info/2013/03/writing-good-tests-for-the-gilded-rose-kata/) about how you could use this kata in a [coding dojo](https://leanpub.com/codingdojohandbook). ## How to use this Kata From 1599d45f689334d26541e7d4a97998bb80b4ecab Mon Sep 17 00:00:00 2001 From: Pietro Di Bello Date: Mon, 25 Jan 2016 20:42:55 +0100 Subject: [PATCH 2/2] fix typo in requirements --- GildedRoseRequirements.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/GildedRoseRequirements.txt b/GildedRoseRequirements.txt index e2bfd98a..2e74aae6 100644 --- a/GildedRoseRequirements.txt +++ b/GildedRoseRequirements.txt @@ -20,7 +20,7 @@ Pretty simple, right? Well this is where it gets interesting: - "Aged Brie" actually increases in Quality the older it gets - The Quality of an item is never more than 50 - "Sulfuras", being a legendary item, never has to be sold or decreases in Quality - - "Backstage passes", like aged brie, increases in Quality as it's SellIn value approaches; + - "Backstage passes", like aged brie, increases in Quality as its SellIn value approaches; Quality increases by 2 when there are 10 days or less and by 3 when there are 5 days or less but Quality drops to 0 after the concert @@ -35,4 +35,4 @@ ownership (you can make the UpdateQuality method and Items property static if yo for you). Just for clarification, an item can never have its Quality increase above 50, however "Sulfuras" is a -legendary item and as such its Quality is 80 and it never alters. \ No newline at end of file +legendary item and as such its Quality is 80 and it never alters.