Throughout this assignment, you may find the following resources helpful. Refer to them BEFORE posting questions on Piazza.
- Connecting to the lab machines remotely
- running bash on Windows
- Unix reference sheet
- JUnit testing tutorial
- Counter.java
- CounterTest.java
- RockPaperScissors.java
- RockPaperScissorsTest.java
- Counter.java
- CounterTest.java
- RockPaperScissors.java
The goal of this assignment is to re-familarize yourself with the command line, IDEs/text editors, and Java. Additionally, you will gain familiarity with the course turn-in procedures, learn basics of unit testing with JUnit, and implement a few modest-sized programming problems using Arrays and ArrayLists from the Java Collections Framework.
In EACH AND EVERY FILE that you turn in, we need the following in comments at the top of each file. These are essential so that we can more easily process your submissions and ensure that you receive proper credit. This is a very large class with about 700 students when combining both lectures. No name, no points.
NAME:
ID:
EMAIL:
Instructions on how to submit your assignment will be posted on Piazza on #TODO (updated date) Wednesday (10/3).
We strongly recommend that you work on the lab machines (for remote access--see instructions here), but if you choose to work on your own machine, make sure your code runs correctly on ieng6, as that is where we will be testing it. Instructions below assume you are using the lab machines.
Create a subdirectory call “pa1” in your class account. All of your files for this assignment should be placed in that subdirectory. If you cannot remember how to create directories, refer to a unix tutorial or reference sheet.
Read and sign the Integrity of Scholarship agreement for CSE 12 here. You cannot earn any credit in CSE 12 until you have done so.
The purpose of this problem is to get you comfortable with JUnit 4 on the command line. You may use any program you like to edit your java files (e.g., Dr. Java, vim, Notepad++, or even Eclipse), but we would like you to compile the program and run the JUnit tests from the command line.
Clone/download the files from this GitHub repository.
- For more information on how to use GitHub to retrieve the files refer to this documentation.
For this problem, you will write JUnit tests and run them from the command line. If you are working on your own machine, follow the instructions here to install JUnit 4 (NOT JUnit 5) on your own machine. Note: that these instructions omit the step where you need to add the hamcrest-core file to your CLASSPATH (you need to do this or you will get a compile error).
Now, open the CounterTest.java file in an editor. Most of this file is already complete, and you should be able to compile and run it (see below). However, there are some ‘TODO:’ marked in comments where you are to complete the code. These completions include adding comments at the top of the file and completing the code to properly run some of the unit tests against the Counter class. When you run the unit tests, they should make reasonable tests and print out the following when running the JUnitCore TestRunner.
.Checking Default Counter Value is Zero
.Checking Proper Increment
.Checking Multiple Increments
.Checking Reset
.Checking Decrement
Time: 0.002
OK (5 tests)
Steps to complete for this problem:
- First, complete the TODO items in CounterTest.java.
- Next, run all of the tests from the command line. You will need to figure out the proper sequence of commands to do this. Feel free to talk to a tutor/TA or to use Google for help.
- Finally, modify Counter.java so that your Reset test fails. The version of Counter.java that does not pass the Reset test is the version you should turn in. To be clear, Counter.java must compile but it should fail a reasonable Reset test. We will run your tests against an error-free version of Counter.java to ensure that all tests pass. Then we will run your tests against your turned in version of Counter.java to see the failed Reset test.
In this problem you will create a computer game to play the game of Rock-Paper-Scissors with a user. If you are unfamiliar with this game, you can read about it on Wikipedia here.
We have provided starter code for this problem. Copy the following from the the public GitHub repository:
RockPaperScissors.java
RockPaperScissorsTest.java
(Note: this problem also uses Counter.java)
When the user starts your game, it should play the game of Rock Paper Scissors with the user until the user types ‘q’. Here is an example run. User input is after the "(r=rock, p=paper, s=scissors or q to quit)".
Let's play! What's your move? (r=rock, p=paper, s=scissors or q to quit)
r
I chose rock. It's a tie.
Let's play! What's your move? (r=rock, p=paper, s=scissors or q to quit)
p
I chose rock. You win.
Let's play! What's your move? (r=rock, p=paper, s=scissors or q to quit)
g
That is not a valid move. Please try again.
Let's play! What's your move? (r=rock, p=paper, s=scissors or q to quit)
p
I chose paper. It's a tie.
Let's play! What's your move? (r=rock, p=paper, s=scissors or q to quit)
s
I chose rock. I win!
Let's play! What's your move? (r=rock, p=paper, s=scissors or q to quit)
r
I chose paper. I win!
Let's play! What's your move? (r=rock, p=paper, s=scissors or q to quit)
s
I chose rock. I win!
Let's play! What's your move? (r=rock, p=paper, s=scissors or q to quit)
q
Thanks for playing!
Our most recent games were:
Me: r, You: s
Me: p, You: r
Me: r, You: s
Me: p, You: p
Me: r, You: p
Me: r, You: r
Our overall stats are:
I won: 50.00%
You won: 16.67%
We tied: 33.33%
Do not change the starter code. However, you may add additional helper methods. Your task is to implment the following methods:
public RockPaperScissors()- constructor for the class, initializes the member
static String genCPUMove()- generates a random String ("r", "s", or "p")
public void expandCapacity()- doubles the size of the systemMoves array
public void addSystemMove(String myMove)- adds myMove to the end of the systemMoves array
public void play(String playerMove, String compMove)- determines game outcome and increments variables accordingly
We have given you the main() method as well as end(). Do not modify end(). You are, however, welcome to change main() while testing. Make sure before you submit that your code runs with the original main() method given.
main(): while playing is true, get the user's move and the computer's move and calls theplaymethod.end(): displays the game results
Tip: look at the end() method to see what variables you will need to keep track of and increment during the game.
Here are some detailed requirements of the game play and specifics about the program:
-
You will write your code for the methods described above. Please do not alter the provided variable names in the starter code, we will test your code using these variable. Additonally, do not delete variables or change the number of arguments in the methods. Doing so will result in incorrect auto-graded results.
-
In the starter code, we have proivded the necessary Strings for when you need to print. Use these for consistency for when we test your output.
-
The game should track the full move history for both players. It should store the move history of the system in an array of Strings (
systemMoves) and the move history of the user in a ArrayList of Strings (userMoves). These variables are already set up in the starter code. You just need to use them. -
The array that stores the system’s moves should be initialized to a capacity of 5 in the constructor. As the system enters more moves than the array can hold, use
expandCapacity()to make a new array and copy over the contents of the old one. The new array should always be twice the size of the old array. E.g. on the 6th move, the array becomes size 10, on the 11th move it becomes size 20, etc. You must do this resizing and copying “from scratch”. That is, you have to write the code yourself, and may NOT use any method in Java’s Arrays class. You will only receive half credit if you do. In youraddSystemMovemethod you will need to check when the capacity is reached before you add the computer's move to the array. -
Your program should gracefully handle incorrect input by re-prompting the user until they enter valid input. You should look for the letters r, s and p exactly.
-
The game should repeat until the user enters "q"
-
At the end of the game, the system should print out up to the last 10 games, in reverse order. If there has not been 10 games, it should print out as many as has been played. It should also print the win and tie statistics as in the example. Use the provided
end()method to achieve this. -
In
genCPUMove(), it’s up to you on how the computer player chooses its moves, but there are two rules 1) the moves can not be the same every time, 2) it cannot cheat. That is, it cannot look at the user’s move and then decide how to move. It can, however, look at the user’s move history as well as its own history. You can do something as simple as having it choose a random move every time. But if you’d like to get more sophisticated, you should try to make the best player out there by taking into account what you know about how the user plays. It’s amazing how “smart” you can make your program with just a little information. If you do get creative here, make sure you document your approach in your header comment at the top of your RockPaperScissors.java file. -
Your program should generate no exceptions under (almost) any circumstances. Try to break it with bad input.