Skip to content

Conversation

@JavierGelatti
Copy link

This is my submission for the challenge. It was my first time using FitNesse, but I enjoyed using it and learned a lot while doing it.
This month I started reading the Refactoring book, so I did the changes in little steps (and always running the tests in between).

A summary of the changes:

  • Implemented a missing test (see commit 9678d82)
  • Introduced functional style for traversing collections
  • Tested that if the Wumpus stops the arrow, the player is not killed by shooting in circle
  • Added all direction cases to some tests
  • Extracted some methods
  • Untracked some FitNesse files

I discovered an implemented feature that was not tested.
Then, I had to choose between two paths:
    1. Deleting the feature (if it's not in the requirements, then it
       should not be in the code), or
    2. Adding a test, to justify the existence of the feature.

I chose to add a new test (2), because I wanted to practice with FitNesse,
but in a real project I would consider the other option a little more (an
arrow can travel at most 103 caverns? and it isn't in the requirements?
sounds suspicious...)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant