Review code additions since Journal Entry 09

[artfuldev]

Issues discovered while reviewing the code additions are documented here till completion of the Rules of Chess Integration milestone.

• [x] #71 Adhere to Enumeration Guidelines
• [x] #74 Castling Move is missing implementation
• [ ] #85 Increase code coverage
• [x] #89 Illegal Move: King moves into square controlled by the enemy King
• [x] #90 Illegal Move: King is captured
• [x] #94 Notation for Castling Moves is wrong in LAN and SAN
• [x] #100 Add Initial Setup Tests
• [x] #101 Add Gameplay Tests

[artfuldev]

Initial Setup

In Journal Entry 07 - The Chess Pieces, we covered the initial setup of the chess pieces on the board. It is now created by an IPosition initialized with a FenString.

100 Tests required to see if FenString piece placement, etc., work.

[artfuldev]

Gameplay

The player controlling the white pieces is named "White"(IGame has an IPlayer named White whose side is SIde.White); the player controlling the black pieces is named "Black"(IGame has an IPlayer named Black whose side is Side.Black). White moves first, then players alternate moves (IGame.SideToPlay is calculated). Making a move is required; it is not legal to skip a move. Play continues until a king is checkmated, a player resigns, or a draw is declared (IGame has IStatusUpdaters which update the Status and StatusReason. When play is not possible, calling IGame.Play() throws.

101 Gameplay Tests