Group Evaluation for Lab 4 – PlayingCardDeck Class
Your name:
(Your lab is the one being evaluated)		
Names of group members participating in the evaluation, including yourself:		
Date:

Instructions
You should have already completed Lab 4 and uploaded a copy to moodle. After you and your group have evaluated your work, you will submit this evaluation along with any revisions of your lab work to moodle using the Lab 4 Evaluation and Revision link. You will be graded on your revised lab work and the quality of this evaluation.
Criteria	Yes/no	
PlayingCardDeck.h	
Are all class members that are not part of the public interface private?		
Is there an array of pointers to PlayingCards that is a private member of PlayingCardDeck? 		
Is a constant used for the array size allocator?		
Are the only member functions that are defined in-line two lines or less?		
Are there comments describing the purpose of each member variable or function?		
	
BlackJackHand.cpp	
Are constants used for any number that is used more than once with the same meaning?		
Are there comments that explain the use of literal constants where their purpose is not obvious?		
Do the constructors initialize all the array elements with pointers to PlayingCard objects?		
Is all duplicated code eliminated by using a member function for repeated operations?		
Does the sort function sort the deck the number of times indicated by the function parameter?		
Is there a seed for the random number generator?		
Is there some mechanism in place to prevent dereferencing of NULL or invalid pointers?		
Are all objects created by this class also deleted in the desecrator? (with the exception of PlayingCard objects that were dealt out of the class. These will be deleted by the test driver. Note that the driver was not designed according to best practices.)		
	
CardDeck01Driver2.cpp	
List the name of any PlayingCardDeck functions gave an incorrect result, and what was incorrect.
(See page two for a listing of correct results.)	

		

Original Deck:
AD 2D 3D 4D 5D 6D 7D 8D 9D TD JD QD KD
AC 2C 3C 4C 5C 6C 7C 8C 9C TC JC QC KC
AH 2H 3H 4H 5H 6H 7H 8H 9H TH JH QH KH
AS 2S 3S 4S 5S 6S 7S 8S 9S TS JS QS KS
Dealing some cards:
AD 2D 3D 4D 5D 6D 7D 8D 9D TD JD QD KD
AC 2C 3C 4C 5C 6C 7C 8C 9C
Rest of deck

TC JC QC KC
AH 2H 3H 4H 5H 6H 7H 8H 9H TH JH QH KH
AS 2S 3S 4S 5S 6S 7S 8S 9S TS JS QS KS
Should get shuffle error, 22 cards used, 30 cards remaining:
Warning: deck could not be shuffled!
Used: 22 Remaining: 30

Testing overloaded constructor. Should get shuffled deck:

KS JC 8C 2H QH 4S TC 2D 7S TH KC 8S 5S
QD 4H JH QS 7H 6H 2S 6D KH 3S 2C TD 6S
9D TS 5C AC 8D KD 4D 5D 3C JS 9H JD 7D
AH 9S AD 3D 4C 7C 8H 3H 6C QC 9C AS 5H
Reset deck:

AD 2D 3D 4D 5D 6D 7D 8D 9D TD JD QD KD
AC 2C 3C 4C 5C 6C 7C 8C 9C TC JC QC KC
AH 2H 3H 4H 5H 6H 7H 8H 9H TH JH QH KH
AS 2S 3S 4S 5S 6S 7S 8S 9S TS JS QS KS
Testing empty deck:
Should get 2 deal errors, 1 empty display msg,
52 cards used, 0 cardes remaining
myCard is null
Warning: No cards left to deal!
Warning: No cards left to deal!
Used: 52 Remaining: 0
myCard is null
Shuffle test. Should see unshuffled, shuffled, Array of 52 1's:

AD 2D 3D 4D 5D 6D 7D 8D 9D TD JD QD KD
AC 2C 3C 4C 5C 6C 7C 8C 9C TC JC QC KC
AH 2H 3H 4H 5H 6H 7H 8H 9H TH JH QH KH
AS 2S 3S 4S 5S 6S 7S 8S 9S TS JS QS KS
3C TD 9D 4S TS 2H 2S 5D JC 9C 6C KS 6D
8D AD QS JS 3S 7S 4C 3D 2C KC JD TC 4H
AS 6H 8S 5C JH KD 8H KH 5S QC QD 7C 7H
AH TH 6S 9H 5H 7D QH 3H 9S 2D 4D 8C AC
1  1  1  1  1  1  1  1  1  1  1  1  1
1  1  1  1  1  1  1  1  1  1  1  1  1
1  1  1  1  1  1  1  1  1  1  1  1  1
1  1  1  1  1  1  1  1  1  1  1  1  1
reset() memory leak test. This may take a while
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
Passed
destructor memory leak test. This may take a while
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
Passed
Testing Complete!