CSC 217 Lab 04: Testing
As with any software development project, you must test your code to know if it meets the requirements and design. You should have been running your tests cases as you integrated the two systems together. Now, you will focus on unit testing for coverage.
PackScheduler Coverage
Ensure that all non-UI classes have at least 80% statement coverage. Add any needed high quality tests to cover at least 80% of the statements in non-UI classes.
System Testing
For the moment, you will forgo system testing. Since there were no changes to Student, StudentRecordIO, and StudentDirectory, we do expect that your StudentDirectoryPanel tests will continue to pass (and you’re welcome to run them to make sure they still do). However, the GUI for the Course side of the project has not yet been provided so we will not be evaluating your application at a system test level for Lab 04.
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.
Since we can’t automate black box tests, you won’t need to check Jenkins. But you should make sure that your Black Box Test Plan was submitted!
Reminder: Staging and Pushing to GitHub
GitHub Resources: