{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

eecs280.discussion.week7 - EECS 280 Discussion Project 3...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
EECS 280 Discussion
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Project 3 Due Wednesday, November 3 rd , 11:59 PM
Background image of page 2
Test case: p3t1 Tests initGame() % g++ -o p3t1 -Wall -Werror p3.cpp p3t1.cpp % ./p3t1 sample.board sample.deck 2 10 yes > p3t1.out % diff p3t1.out p3t1.answer Do not use printGame() in your final code version to print out anything!
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Test case: p3t2 Tests eval() Uses a “standard” board and reads a scenario from standard input Contents of evalStart.in: (test eval() 's treatment of a START card) 1 (number of players) -1 -2 -1 -1 (4 pawn locations: -1 startable, -2 home) 0 (number of the player who will start playing (blue)) 0 0 (curCard (Start))
Background image of page 4
Test case: p3t2 % g++ -Wall -Werror m32 p3.cpp p3t2.cpp -o p3t2 % ./p3t2 < evalStart.in > myEvalStart.out % diff myEvalStart.out evalStart.out Test passed if diff reports no differences Similarly, check out evalBack.in Feel free to create your own eval test cases using this format.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Test case: p3t3 Similar to p3t2, but checks the apply() function Uses a “standard” board and reads a scenario from standard input Contents of applyStart.in: (test
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}