辅导CSCI 2134程序、写作Java编程设计

” 辅导CSCI 2134程序、写作Java编程设计CSCI 2134 Assignment 3Due date: 11:59pm, Friday, March 19, 2021, submitted via GitObjectivesPractice debugging code, using a symbolic debugger, and fixing errors.Preparation:Clone the Assignment 3 Repository httpss://git.cs.dal.ca/courses/2021-winter/csci-2134/assignment3/.gitwhere is your CSID.Problem StatementTake a piece of buggy code, debug it, and fix it.BackgroundYou have inherited some buggy code for computing shortest path solutions to the board gameTicket to Ride. Your boss has fired the previous developer because they did not do any testingand did not fix the bugs! She has hired you to debug and fix the code. She will provide you withsome unit tests (some of which fail), sample input and sample output of what should be produced.Your job is to fix the bugs: Both the bugs exhibited by the unit tests and the ones by theinput. Good luck!You will be provided with a full buggy codebase for JSON comparison, a specification, a set of unittests using JUnit5, sample input and expected output. Your job is to identify and fix all the bugs.Given a game board of rail segments and a list of routes (pairs of cities), the code is supposed tocompute the total cost of building a network between the given routes, assuming that the shortestdistance for each route is chosen. This can be computed by computing shortest paths for eachroute using Dijkstras shortest path algorithm.You will be provided with a full buggy codebase for distance computation, a specification, a setof unit tests using JUnit5, Sample input and expected output. Your job is to identify and fix allthe bugs.Task1. Review the specification (specification.pdf) in the docs directory. You will absolutelyneed to understand it and the code you are debugging. The main method for the programis in RouteCost.java. Note that your boss finally got the buggy makeTree method inCity.java from the previous developer. Spend some time tracing through the code and creatinga diagram of how the classes and code are put together. This will help you a lot later on!2. Fix all bugs that are identified by the tests generated by the unit tests in the following classes: City.java CityComparator.java Link.java3. See buglist.txt file in the docs directory. One sample entry is included. For each bugthat you fix add an entry to this file that includes:a. The file/class Name where the bug was.b. The method where the bug wasc. The line number(s) where the buggy code wasd. A description of what the bug wase. A description of what the fix was.4. The previous developer made a set of example input and expected output in the input_testsdirectory. These tests will likely not pass yet even after fixing the bugs identifiedby the unit tests. See the README.txt in this directory for help running the tests. The easiest method is tocopy your .java files from src to this directory and run the test.sh script in a terminal or gitbash command line shell. Compare the output in the .out files with the expected .gold files. For each output that differs from the expected output, debug the code and determinethe reason for the mismatch. Fix any identified bugs missed by the unit tests.5. Record any new bugs found and fixed from Step 4 in the previously created buglist.txt6. Commit and push Back the bug fixes and the buglist.txt file to the remote repository.SubmissionAll fixes and files must be committed and pushed back to the remote Git repository.GradingThe following grading scheme will be used:Task 4/4 3/4 2/4 1/4 0/4Bugs found[unit tests](20%)4 to 5 bugs arecorrectly identifiedand documented.Three (3) bugsare correctlyidentified anddocumented.Two (2) bugsare correctlyidentified anddocumented.One (1) bug is correctlyidentifiedand documented.Zero (0) bugsare correctlyidentified anddocumented.Bugs fixed[unit tests](20%)4 to 5 bugs arecorrectly fixed.All unit testspass.Three (3) bugsare correctlyfixed.Two (2) bugsare correctlyfixed.One (1) bug is correctlyfixed.Zero (0) bugsare correctlyfixed.Bugs found[input tests](20%)2 to 3 bugs areCorrectly identifiedand documented.N/A One (1) bug iscorrectly identifiedand documented.N/A Zero (0) bugsare correctlyidentified anddocumented.Bugs fixed[input tests](30%)2 to 3 bugs arecorrectly fixed.All input testspass.2 to 3 bugs arecorrectly fixed.One (1) bug iscorrectly fixed.Some inputTests passN/A Zero (0) bugsare correctlyfixed.Document[buglist.txt]Clarity(10%)Documentlooks professional,includesall information,and easy toreadDocument looksok. May behard to read ormissing someinformation.Document issloppy, inconsistent,and hasMissing informationDocument is verysloppy with significantmissing informationDocument isillegible or notprovided.Hints1. You will need to use a symbolic debugger to make headway. Using print-statements will bepossible but extremely painful.2. You will need to step through the code to find the bugs.3. There are about 2-3 bugs in the code (in addition to the ones identified by the unit tests). TheSingle bug report should cover all of them.如有需要，请加QQ：99515681 或WX：codehelp

“