Task
1. Review the specification (specification.pdf) in the docs directory. You will absolutely need to understand it and the code you are debugging. The main method for the program is in RouteCost.java. Note that your boss finally got the buggy makeTree method in City.java from the previous developer. Spend some time tracing through the code and creating a 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.java
3. See buglist.txt file in the docs directory. One sample entry is included. For each bug
that 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 was
c. The line number(s) where the buggy code was
d. A description of what the bug was
e. A description of what the fix was.
4. The previous developer made a set of example input and expected output in the input_tests directory. These tests will likely not pass yet even after fixing the bugs identified by the unit tests.
• See the README.txt in this directory for help running the tests. The easiest method is to copy your .java files from src to this directory and run the test.sh script in a terminal or git
bash 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 determine the 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.txt
6. Commit and push back the bug fixes and the buglist.txt file to the remote repository.

DETAILED ASSIGNMENT

20210315165752csci_2134_assignment_3