Need Help Writing the JAVA code for YAHTZEE.
We have to do an Automated Testing. Please provide the Requirements and the Test Cases First.
After that provide the Java Code that covers all the test cases and shows a single output after the test cases are run.
PROJECT 3-Automated Testing I. Project Introduction For this assignment, you will write (and testl) software for a game that plays Yahtzee, a 5-dice game. The rules to this game can be found in Appendix A, along with a score sheet of the paper version in Appendix B You are not expected to write an entire game for your assignment! Rather, you are to write the software which fills in a virtual, one-game, one-player scoresheet during a game, and which tracks a player's score as the play progresses. However, you do not need to handle giving the user three dice rolls per turn This means, given The face values of five dice The category that the user wants to use the program will correctly calculate the proper score to be added into that place on the scoresheet. This means that, essentially, the expected output is the changes to the scoresheet. For example, if the dice were 6-6-3-3-3, then that would score 9 in the 3s category 12 in the 6s category 21 in the 3-of-a-kind category 25 in the Full House category 21 in the Chance category and a 0 in all the other categories II. Important! You MUST complete the project using the following guidance 1. In the spirit of TDD and the V-Model, you should write your requirements and test cases before proceeding to write your software. You need not adhere strictly to TDD guidance, but your code should be written using your test plan to help write the code. This will be done iteratively and incrementally, with small bits of functionality being added with each iteration. 2. Remember, the start of a good test plan is well-written requirements particularly requirements written at the right level of abstraction. "The program will implement scoring for a Yahtzee game" is not a requirement specific enough for writing test cases. Neither is "The program will score 30 points for a small straight. (Those may be good introductory or supplemental sentences in a requirements document, but they are not necessarily testable requirements in and of themselves.) IIl. Test Cases and Automated Testing A test case for this project might look something like this Test Case 1: Testing Full House Input: 6-3-6-3-3, Full House Expected Output: 25 points scored in Full House category Actual Output Pass/Fail: [ ] Pass Fail PROJECT 3-Automated Testing I. Project Introduction For this assignment, you will write (and testl) software for a game that plays Yahtzee, a 5-dice game. The rules to this game can be found in Appendix A, along with a score sheet of the paper version in Appendix B You are not expected to write an entire game for your assignment! Rather, you are to write the software which fills in a virtual, one-game, one-player scoresheet during a game, and which tracks a player's score as the play progresses. However, you do not need to handle giving the user three dice rolls per turn This means, given The face values of five dice The category that the user wants to use the program will correctly calculate the proper score to be added into that place on the scoresheet. This means that, essentially, the expected output is the changes to the scoresheet. For example, if the dice were 6-6-3-3-3, then that would score 9 in the 3s category 12 in the 6s category 21 in the 3-of-a-kind category 25 in the Full House category 21 in the Chance category and a 0 in all the other categories II. Important! You MUST complete the project using the following guidance 1. In the spirit of TDD and the V-Model, you should write your requirements and test cases before proceeding to write your software. You need not adhere strictly to TDD guidance, but your code should be written using your test plan to help write the code. This will be done iteratively and incrementally, with small bits of functionality being added with each iteration. 2. Remember, the start of a good test plan is well-written requirements particularly requirements written at the right level of abstraction. "The program will implement scoring for a Yahtzee game" is not a requirement specific enough for writing test cases. Neither is "The program will score 30 points for a small straight. (Those may be good introductory or supplemental sentences in a requirements document, but they are not necessarily testable requirements in and of themselves.) IIl. Test Cases and Automated Testing A test case for this project might look something like this Test Case 1: Testing Full House Input: 6-3-6-3-3, Full House Expected Output: 25 points scored in Full House category Actual Output Pass/Fail: [ ] Pass Fail
