CSC 217 Lab 07 - Integrate into Student

CSC 217 Lab 07 Testing

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 and non-test classes each have at least 80% statement coverage as measured on Jenkins. Add any needed tests to cover at least 80% of the statements.

The introduction of the Student Schedule functionality shouldn’t lead to the regression of any existing tests. But if there is a regression, update the test to reflect the new requirements.

`PackSchedulerGUI`

The teaching staff has provided four classes that comprise the GUI for PackScheduler. Create classes PackSchedulerGUI, CourseCatalogPanel, StudentDirectoryPanel, and StudentRegistrationPanel in the edu.ncsu.csc216.pack_scheduler.ui package and copy in the provided code. Note that there are updates to PackScheduleGUI and StudentRegistrationPanel, so you should use the provided code.

System Testing and Debugging

Since the new functionality shouldn’t impact earlier functionality, start your system testing with the tests from Lab 05 & Lab 06. A copy of the black box test plan labeled for Lab 07 is available for download. The tests are the same as Lab 05 and Lab 06 black box tests.. Save the black box test plan file in the project_docs folder. You are welcome to update the tests as appropriate for your implementation (i.e., error messages may be in a slightly different order depending on how you implemented your system).

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.
Create tests for the new functionality related to scheduling. You can modify tests from the Guided Projects.

The following files are needed for testing (some you already have):

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: Staging and Pushing to GitHub

GitHub Resources:

CSC 217 Lab 07 - Integrate into Student

CSC 217 Lab 07 - Deployment

CSC 217 Lab 07 - ArrayLists