CSC 217 Lab 05: Testing & Debugging
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 integrated and debugged RegistrationManager. 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.
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. Note that there are updates to StudentDirectoryPanel, so you should use the provided code.
System Testing and Debugging
Download a copy of the black box tests for PackScheduler. Save the black box test plan file in the project_docs folder.
Do the following:
- Run the tests on the
PackSchedulerproject. 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 (some you already have):
- 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)!
Reminder: Generating Javadoc
To generate Javadoc, you need to configure and run the Javadoc tool, fix Javadoc errors and warnings, and check the generated Javadoc pages. Make sure you push your changes to GitHub!