CS342: Software Design

CS342: Software DesignSeptember 26, 2017

AgendaProject 1 discussion: OverviewCode examplesClass designsTesting for Project 1Different levels of testing

Card Game: Poker - 5 Card Draw

Class dependencyGameComputerPlayerUserPlayerCardCardPile

You may get this when building large scale software.

Player Base class:common fields andmethods for user andcomputer- Add a card to hand- Discard a card- Has flus, has four suit,has etc- Calculate rank- Cal # of cards u candiscard- Get handCard Pile- Shuffle- Deal a cardCard- Number, suit, stringGame Session: mainlogic and workflow- Set up pile- Instantiate Players- Deal to Players- Players replace cards- Decide results andwinnersUser Player- Interactive selectionFive CardDraw (Main):UI and orchestration- Prompt # of players- Trigger dealing- User's turn- AI's turn- Display resultsComputer Player- AI functionCleaner class design

Main function class: orchestration

Main function class: UI

GameSession class: game level logic and workflow

Player classes

Card ClassGood job with the enum!What test cases do we needhere?

Let’s take another look: Class dependencyGameComputerPlayerUserPlayerCardCardPile

Player Base class:common fields andmethods for user andcomputer- Add a card to hand- Discard a card- Has flus, has four suit,has etc- Calculate rank- Calculate # of cards ucan discard- Get handCard Pile- Shuffle- Deal a cardCard- Number, suit, stringGame Session: mainlogic and workflow- Set up pile- Instantiate Players- Deal to Players- Players replace cards- Decide results andwinnersUser Player- Interactive selectionFive CardDraw (Main):UI and orchestration- Prompt # of players- Trigger dealing- User's turn- AI's turn- Display resultsComputer Player- AI functionAnd Cleaner class design

DiscussionsCreate Loosely coupled, self-contained classes Less dependent on other classCan perform its own domain of businessRespect other’s boundary. Don’t overreachSeparate UI vs. logic, and logic vs. data accessOne direction dependency.Layer: lower layer shouldn’t be aware of higher layer. High layer shouldn’t carehow lower layer does its jobWhy separate frontend and backend classes?Easier to debug, read, maintain, and scale.What could have been done differently? Player show hands: move display part out of Player class“Hand” class?

CardPile ClassWhat are we missing here?

CardPile testcontinuesHow do we test the drawncard should match themissing card from pile?How do we access privatemethods and fields ofCardPile?

BasePlayer TestTest “hasAce”: Both positive and negativecaseshow many times do we needto runSame for hasFourSuit,ResolveReplaceChances:need to test path hasAceand not haveAceHint: use @Before, @Afterto set up handsaddCard() hasAce() ResolveReplaceChances()

Different levels of testing UAT: real users System testing: QA Integration:Developers, maybeQA Unite testing:developers

More about testing System testing vs. functional testingRegression testingSmoke testingContinuous testingLoad/performance testingEdge case (what happen to GameSession if two players havesame hand rank? What if someone’s birthday is right at0:00AM? What if )

- Add a card to hand - Discard a card - Has flus, has four suit, has etc - Calculate rank - Calculate # of cards u can discard - Get hand And Cleaner class design Five CardDraw (Main): UI and orchestration - Prompt # of players - Trigger dealing - User's turn - AI's turn - Display result