Independent Task: Update WolfSchedulerGUI
Black box test the WolfScheduler system to ensure that the conflict functionality is working correctly from end-to-end.
Learning Outcomes
- Run (and revise) black box tests
WolfSchedulerGUI
WolfSchedulerGUI did not require any changes from GP2. But if you need a new copy, copy the code from WolfSchedulerGUI.java into your Eclipse file. Overwrite the entirety of the old file.
Run System Tests
Run your system tests! If any are still failing, use the debugger to help you find the problem. Report the actual results of your tests.
If you need to revise your tests to more correctly describe the inputs or outputs, you may do so.
Record the actual results of execution for your tests. If you run low on time, remember it is better to record the actual test failure; you’ll get credit for reporting what’s actually happening.
Make sure that you successfully push your System Test Plan to the remote GitHub repository! Check the website to make sure it’s there!
Reference: Staging and Pushing to GitHub
GitHub Resources:
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.