$24
HW: Unit Testing Solved
Homework Objective:
Demonstrate the ability to:
Write effective unit tests
Use tests to verify that new code works as specified
Part 2: Unit Testing (80 points)
Deliverables and Submission Process:
For the main assignment, modify the test file hw5_test.py to test hw5_cards.py and submit to canvas
Background:
In order to complete this assignment, you will need to familiarize yourself with the Card class covered in the lecture and the discussion. You will also want to review the Lecture Notes on Unit Testing in Python.
Then you will include tests for the cases described below. There are a few notes though:
You may create as many or few unittest methods as you like.
You may assume that other programmers will NOT invoke these functions with unacceptable inputs (e.g. no one will try to create a card with rank 0). You just need to ensure that the code works as intended.
Instructions:
Main assignment: Basic Unit Testing (80 points) UnitTesting
Note: Each test case will be written in a different method. (You need to write 8 methods in total.)
. Test that if you create a card with rank 12, its rank_name will be "Queen"
. Test that if you create a card instance with suit 1, its suit_name will be "Clubs"
. Test that if you invoke the __str__ method of a card instance that is created with suit=3, rank=13, it returns the string "King of Spades"
. Test that if you create a deck instance, it will have 52 cards in its cards instance variable
. Test that if you invoke the deal_card method on a deck, it will return a card instance.
. Test that if you invoke the deal_card method on a deck, the deck has one fewer cards in it afterwards.
. Test that if you invoke the replace_card method, the deck has one more card in it afterwards. (Please note that you want to use deal_card function first to remove a card from the deck and then add the same card back in)
. Test that if you invoke the replace_card method with a card that is already in the deck, the deck size is not affected.(The function must silently ignore it if you try to add a card that’s already in the deck)
What to turn in:
Add your name and uniqname to the file name and the head of hwUnitTest_uniqname.py. This is an example.
#########################################
##### Name: <write your name> #####
##### Uniqname:<write your uniqname>#####
#########################################
Extra Credit 1: Writing your own class/tests (2 points)
In this part, you will implement the class Hand and create tests to verify that it works as specified. You will need to create a new testing class called TestHand that subclasses unittest.TestCase, and implement 3 test functions.
create the Hand with an initial set of cards class Hand:
'''a hand for playing card
Class Attributes
----------------
None
Instance Attributes
-------------------
init_card: list
a list of cards
'''
def __init__(self, init_cards):
pass
def add_card(self, card):
'''add a card
add a card to the hand
silently fails if the card is already in the hand
Parameters
-------------------
card: instance
a card to add
Returns
-------
None
'''
pass
def remove_card(self, card):
'''remove a card from the hand
Parameters
-------------------
card: instance
a card to remove
Returns
-------
the card, or None if the card was not in the Hand
'''
pass
def draw(self, deck):
'''draw a card
draw a card from a deck and add it to the hand side effect: the deck will be depleted by one card
Parameters
-------------------
deck: instance
a deck from which to draw
Returns
-------
None
'''
pass
These tests are less specified than those in part 1, so you will have to think about writing good tests for each of these functions.
You do not need to worry about testing for invalid inputs. For example, you can assume that Hand will be initialized with a valid list of valid Cards, and that draw( ) will be called with a valid non-empty Deck.
. Test that a hand is initialized properly.
. Test that add_card( ) and remove_card( ) behave as specified (you can write one test for this, called testAddAndRemove.
. Test that draw( ) works as specified. Be sure to test side effects as well.
What to turn in:
Create a new file called hw5_cards_ec1.py and hw5_test_ec1.py, and submit on canvas. This needs to be named separately from the hw5_cards.py you turn in for Parts 1, even though it will be based on it.
Extra Credit 2 (2 points):
Implement two new pieces of functionality:
. Add a function “remove_pairs” to Hand that looks for pairs of cards in a hand and removes them. Note that if there are three of a kind, only two should be removed (it doesn’t matter which two). Write a docstring and tests to verify that the function works as specified.
. Add a function “deal” to Deck that takes two parameters representing the number of hands and the number of cards per hand and returns a list of Hands. If the number of cards per hand is set to -1, all of the cards should be dealt, even if
this results in an uneven number of cards per hand. Write a docstring and tests to verify that the function works as specified.
What to turn in:
Create a new file called hw5_cards_ec2.py and hw5_test_ec2.py, and submit to canvas. This needs to be named separately from the hw5_cards.py you turn in for Parts 1, even though it will be based on it.
Grading
Part 2: UnitTesting
We are not providing sample output, so you are encouraged to exercise reasonable judgment in following the instructions above to meet the requirements listed here.
Req
Description
Category
Point Value
1
free
free
24
2
is updated.
Behavior
4
hw5
_test.py
3
runs without syntax error.
Behavior
4
hw5
_test.py
4
Eight test methods are made.
Code
4
5
Test 1 creates an instance of Card.
Code
4
6
Test 1 correctly compare the values.
Code
4
7
Test 2 creates an instance of Card.
Code
4
8
Test 2 correctly compare the values.
Code
4
9
Test 3 creates an instance of Card.
Code
4
10
Test 3 correctly compare the values.
Code
4
11
Test 4 creates an instance of Deck.
Code
4
12
Test 4 correctly compare the values.
Code
4
13
Test 5 invokes
and receive an
Code
4
instance.
deal_card
14
Test 5 correctly compare the types.
Code
4
15
Test 6 invokes
.
Code
4
deal_card
16
Test 6 correctly compare before and after.
Code
4
17
Test 7 invokes
.
Code
4
deal_card
18
Test 7 correctly compare before and after.
Code
4
19
Test 8 obtains an existing card from Deck.
Code
4
20
Test 8 correctly compare before and after.
Code
4
Total
100
Extra Credit #1
We are not providing sample output, so you are encouraged to exercise reasonable judgment in following the instructions above to meet the requirements listed here.
Req
Description
Category
Point Value
1
Implement test cases that test
,
Code
1
, and
add_card
remove_card
draw
2
,
, and
work as
Behavior
1
add_card remove_card
draw
specified
Total
2
Extra Credit #2
We are not providing sample output, so you are encouraged to exercise reasonable judgment in following the instructions above to meet the requirements listed here.
Req
Description
Category
Point Value
1
Implement test cases to test
remove_pairs
Code
1
2
and
deal
and
work as specified Behavior
1
remove_pairs
deal
Total
2
