=== Debrief ===

This is my first solution for the GildedRose kata. We had discussed this at svruby meetup and I got a chance to see how other people approached the problem. I feel that my solution is clunkier than what most people did which was to subclass the items. I had thought of that but was under the impression that the constraints only allowed for us to modify the update_quality method based on the skeleton gilded_rose.rb. Because I'm a stickler for rules I didn't want to change the initializer and recreate the items as a subclass.

Item.new("Sulfuras", 0, 80) to Legendary.new("Sulfuras", 0, 80)

Anyways that aside it was a good chance to figure out rspec2 a little more since I'm not too knowledgable on it. I struggled with the interface because I knew what I wanted to do but wasn't familiar with the rspec2 way of doing it. I liked the whole idea of setting up context and the output of it is pretty. Probably the coolest thing in this project for me is my use of watchr which allow for autotesting on change since I had played with autotester before and that was horrible.

=== Original Problem Statement === If you want to get cracking on the ruby source then do this: git clone [email protected]:professor/GildedRose.git

Hi and welcome to team Gilded Rose. As you know, we are a small inn with a prime location in a prominent city ran 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.

Source: http://www.iamnotmyself.com/2011/02/13/RefactorThisTheGildedRoseKata.aspx