• Refactor and improve the code after all tests pass
• Remove areas of code duplication

A Player object has the following properties:

• name
• health
• strength
• agility

A Player object has the following methods:

• getStats()
• getInventory()
• getHealth()
• getAttackValue()
• isAlive()
• addPotion()
• reduceHealth()
• Write appropriate tests for the Player() constructor and methods.

An Enemy object has the following properties:

• name
• weapon
• health
• strength
• agility
• potion

An Enemy object has the following methods

• getDescription()
• getHealth()
• getAttackValue()
• isAlive()
• reduceHealth()
• Write appropriate tests for the Enemy() constructor and methods

• All game logic is encompassed by a Game() constructor function.

A Game object has the following properties:

• roundNumber
• isPlayerTurn
• enemies
• currentEnemy
• player

A Game object has the following methods:

• initializingGame()
• battle()
• checkEndOfBattle()
• startNewBattle()
• Consolidate the code. We don't yet know exactly what this step entails, but we do know that we'll need to refactor our code after the tests pass, so we'll create this issue as a placeholder.

• Create tests for the Potion object
• The Potion object will be used to give the player stat boosts.
• If no stat is provided, the stat should be randomly selected.