The Gilded Rose Code Kata

This is a Ruby version of the original Gilded Rose Kata, based on a version of Jim Weirich (see below), prepared to be used as an exercise on characterization tests and legacy code refactoring in the Info3 class at HTW Berlin.

This is a refactoring kata, so you will be starting with a legacy code base, add characterization tests to be able to safely refactor and add the new functionality.

Getting Started

To work the Kata, clone this git repository with

git clone https://github.com/htw-imi-info3/gilded-rose-kata.git

-- please to not fork this repository to a public github repository to share it within your team, but rather push it to a private repo.

Read the description below for the "rules" involving this kata.

The easiest way to install the dependencies is by using bundler. To do so, you need to install the bundler gem (if you haven't already done so) with

gem install bundler

and then run bundler

bundle

and you should be ready to go. Alternatively, you can install the dependencies one by one using gem install, e.g.

gem install rspec-given

Have a look at the Gemfile for all dependencies.

Original Description of the Gilded Rose

Hi and welcome to team Gilded Rose. As you know, we are a small inn with a prime location in a prominent city run by a friendly innkeeper named Allison. We also buy and sell only the finest goods. Unfortunately, our goods are constantly degrading in quality as they approach their sell by date. We have a system in place that updates our inventory for us. It was developed by a no-nonsense type named Leeroy, who has moved on to new adventures. Your task is to add the new feature to our system so that we can begin selling a new category of items. First an introduction to our system:

• All items have a SellIn value which denotes the number of days we have to sell the item
• All items have a Quality value which denotes how valuable the item is
• At the end of each day our system lowers both values for every item

Pretty simple, right? Well this is where it gets interesting:

• Once the sell by date has passed, Quality degrades twice as fast
• The Quality of an item is never negative
• "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; 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

We have recently signed a supplier of conjured items. This requires an update to our system:

• "Conjured" items degrade in Quality twice as fast as normal items

Feel free to make any changes to the UpdateQuality method and add any new code as long as everything still works correctly. However, do not alter the Item class or Items property as those belong to the goblin in the corner who will insta-rage and one-shot you as he doesn't believe in shared code ownership (you can make the UpdateQuality method and Items property static if you like, we'll cover 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.

Changes from the original

(by Jim Weirich )

This Ruby version follows the original code very closely, but has the following changes:

• The original had no tests. Since this is a refactoring kata, I feel the tests are important and provide a fairly complete test suite. Just delete the tests if you wish to "go it alone".

• The original used a hard coded set of "items", presumably for testing the code. Since I added a test suite, the hard coded values were not of much use. I also changed the interface to accept a list of items as a parameter rather than a hard coded constant.

You can read the original kata article for more details.