Independent Task: Update WolfSchedulerGUI

WolfSchedulerGUI should be updated to interact with the updated Event functionality.

Learning Outcomes

• Update WolfSchedulerGUI

Update WolfSchedulerGUI

Copy the code from WolfSchedulerGUI.java into your Eclipse file. Overwrite the entirety of the old file.

Run Unit Tests

Run your tests! If any are still failing, use the debugger to help you find the problem.

The tests and resources files are listed below if you would like to ensure that you have the correct versions.

Test Classes (in test/ directory):

• CourseTest.java
• ExtendedCourseTest.java
• EventTest.java
• CourseRecordIOTest.java
• ActivityRecordIOTest.java
• WolfSchedulerTest.java

Test Files (in test-files/ directory):

• course_records.txt
• expected_activity_records.txt
• expected_course_records.txt
• expected_empty_export.txt
• expected_schedule_export.txt
• invalid_course_records.txt
• starter_course_records.txt
• README.txt

Run System Tests

Run WolfSchedulerGUI and ensure that you pass the new and updated suite of system tests for the WolfScheduler project. As part of running your tests, you must report the actual results of execution. Download the document as a Word document by select File > Download > Microsoft Word in Google Drive. Create a new folder in your WolfScheduler project called project_docs by right clicking on WolfScheduler and selecting New > Folder. Save your black box test plan as a Word document (*.doc or *.docx) in the project_docs folder. As you run each test, report the results of execution in the black box test plan in the actual results column. DO NOT record, “Passed” or “Failed.” Instead, describe the results, similar to the provided Expected Results.

Make sure all your black box tests pass! However, if you run out of time, report the actual results of execution - EVEN IF THEY ARE FAILING! You’ll earn some points on the system test portion of the grading rubric for reporting actual, failing results.

Check GitHub for System Test Plan

Check that your System Test Plan is actually pushed to the remote GitHub. If you saved the file to your project via the file system and pushed using Eclipse, Eclipse likely did not know about the new file. Refresh your project in Eclipse by right-clicking on the project and selecting Refresh. You should then see the *.docx file in your project_docs directory and in the Git Staging view.

Also, make sure you have the System Test Plan in the correct loction so the PTFs can find it quickly during grading!

Check Your Progress

Complete the following tasks before pushing your work to GitHub.

• Make sure that all fields, methods, and constructors are commented.
• Resolve all static analysis notifications.
• Fix test failures.
• Commit and push your code changes with a meaningful commit message. Label your commit with “[GUI]” and “[Test]” for future you!
• Check Jenkins results for a green ball! Fix any Jenkins issues.