As with any software development project, you must test your code to know if it meets the requirements and design. You should have unit tested your new code as you added course validation functionality. Now you will ensure sufficient coverage and system test PackScheduler.

PackScheduler Coverage

Ensure that all non-UI classes have at least 80% statement coverage. Add any needed tests to cover at least 80% of the statements.

The introduction of the new course name validation functionality shouldn’t lead to the regression of any existing tests unless you specifically tested a string that earlier may have been invalid but is now valid. If so, update the test to reflect the new requirements.

PackSchedulerGUI

The teaching staff has provided three classes that comprise the GUI for PackScheduler. Create classes PackSchedulerGUI, CourseCatalogPanel, and StudentDirectoryPanel in the edu.ncsu.csc216.pack_scheduler.ui package and copy in the provided code. Please update all three GUI classes to ensure you have the latest code.

• PackSchedulerGUI Code
• CourseCatalogPanel Code
• StudentDirectoryPanel Code

System Testing and Debugging

Download a copy of the system tests for PackScheduler. Save the system test plan file in the project_docs folder.

Do the following:

• Run the tests on the PackScheduler project. If the test fails, debug your system until it passes.
• Report the actual results of execution after debugging your system.

The following files are needed for testing. These have been updated for this lab!

• student_records.txt
• course_records.txt
• expected_t19_student_directory.txt
• expected_t39_course_catalog.txt

Push to GitHub

Push your PackScheduler project to GitHub

• Add the unstaged changes to the index.
• Commit and push changes. Remember to use a meaningful commit message describing how you have changed the code.

Check Jenkins and make sure that you have a green ball and are passing your tests AND the teaching staff tests (both unit and system)!