Scenarios for different types of win patterns (horizontal, vertical, diagonal)
Game #win? method tests
Game #win? method implementation
Updated expectations for Game #receive_data method. Game #over and #announce_winner method tests
Updated Game #receive_data behavior. Game #over and #announce_winner methods implementation
Basic UI implementation of Game #over and #announce_winner implementation
Add breaks to end of cases in switch to prevent subsequent code execution once a case is matched
Add missing semicolon
Refactor - combine turn and result messages as player messages
No need to check display message text since there are no current plans to hide the board again
Refactor - use 'status' <p> tag for 'Game Over' message. No need for 'game-message' <p> tag.
Rename #receive_data method to #fill_space. Remove test context for checking data type
Refactor - add #occupied? method for clarity
Extract data parsing activities to #receive_data method. Yep, it's back
Refactor - extract row, column, and diagonal calculations to their respective methods
Keep variable naming consistent throughout tests
Refactor - extract calculation of number of clients to a separate method
Refactor - #win? method now checks for all win conditions and does not take a player parameter
Change descriptions to be more succint and reflect the changes to the #win? method
Scenario for game ending in a draw