https://github.com/piru72/swin-adventure

A simple console based game application to practice the concepts of OOP , Unit Test and TDD
https://github.com/piru72/swin-adventure

c-sharp oop-principles tdd unit-testing

Last synced: about 2 months ago
JSON representation

A simple console based game application to practice the concepts of OOP , Unit Test and TDD

• Host: GitHub
• URL: https://github.com/piru72/swin-adventure
• Owner: piru72
• License: agpl-3.0
• Created: 2024-01-01T15:30:06.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-12-12T18:52:12.000Z (2 months ago)
• Last Synced: 2024-12-12T19:39:47.730Z (2 months ago)
• Topics: c-sharp, oop-principles, tdd, unit-testing
• Language: C#
• Homepage:
• Size: 924 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md
  • License: LICENSE

Awesome Lists containing this project

README

        
## 1. Identifiable Object

- Create an Identifiable Object 

- This will become a foundation for many of 

the objects in the Swin-Adventure.

- Identifiable objects have a list of identifiers, and know ifthey are identified by a certain identifier

## 2 Player , Item and Inventory

- Create the Player, Item, and Inventory classes 

- the ability to locate things within these objects. 

- It should be possible to add items into the Player's inventory and then get the player to locate the item for us.

## 3. Bag Class

The **Bag** abstraction is a special kind of item, one that contains other items in its own Inventory. This is a version of the **composite pattern**, which allows flexible arrangements of bags and 

items, for example a bag to contain another bag.

## 4. Looking Command

As there will be a number of Commands, an abstract Command class has also been added.

- This class inherits from Identifiable Object, as each of the commands needs to be identifiable. 

- When data is entered by the user, each Command object will be asked “Are You” and the 

first work of the command.

- For example, with “look at pen” each Command would be asked 

“Are You ‘look’ ” to locate the Command to process the text. As a result the Look Command 

should be identified by “look”.

## 5. All of them Together

It compiles the steps above into a single program to be run from the command line.

## 6. Locations

This will change the look command to also include "look" to look at the player's location.

- identifiable and have a name, and description.

- Can contain items.

- Players have a location.

    - Players "locate" items by checking three things (in order):

    - First checking if they are what is to be located (locate "inventory")

    - Second, checking if they have what is being located ( _inventory fetch "gem")

    - Lastly, checking if the item can be located where they are ( _location, locate "gem")

## 7. Path Direction and Move Command

Notes:

- Have the Path objects move the player to the new location. This will allow for flexibility 

like lockable paths etc.

- Make Path's identifiable. The identifiers indicate the direction, and can be used to locate 

the path from the location.

- The Move Command is identified by the words "move", "go", "head", "leave", ...

Here are some hints for things you will need to test for:

- Path can move player to the Path’s destination

- You can get a Path from a Location given one of the path's identifiers

- Players can leave a location, when given a valid path identifier

- Players remain in the same location when they leave with an invalid path identifier

##

The final project has not been extensively tested.