hnsz/poker

poker's Issues

Write tests in pure groovy

Response object

Write a request/response object that presents to the client and matches with the client responses.
Let it execute

Merge Subpots

if subpots' shareholders are equal then merge them

Immutables

Divide the app into components

Make clearer divide of concerns and create components with single points of access
Which objects state needs to be presentable at the boundary. Eg. Table, seat, player, dealer, history

History/logger

History object should log:
-player status change
-Seat occupation/ change
-Hand history: bets deals payouts

UPDATE
Half implemented. Simple string entries that go into a queue.
Later string objects must be replaced with data objects. That will have various uses.

E.g.
Reviewing of hand history in the client.
Cients that disconnect and reconnect during hand can receive list of events that happened during their dosconnected status.

Assert and contracts

Write contracts and implement preconditions in assert within code
Check postconditions in tests