CSC 217 Lab 10 Implement and Test Faculty
The Faculty class represents an individual faculty record. The Faculty class is a “plain old java object” (POJO) consisting mostly of getters and setters. Faculty extends User and its implementation is similar to the implementation of Student. The main difference is that Faculty objects have a number of courses they can teach in a given semester (between 1 and 3 inclusive) rather keeping track of credits as Students do.
Create FacultyTest
Create FacultyTest in the edu.ncsu.csc216.pack_scheduler.user package of the test/ source folder. Start by creating tests for the Faculty class as defined in the design. Since Faculty is so similar to Student, use StudentTest as a model for your FacultyTest class.
Implement Faculty
Implement Faculty to pass your tests. Since Faculty is so similar to Student, use Student as a model for implementing Faculty.
Javadoc your Code
Javadoc the Faculty class, state, and methods. For the overridden methods equals(), hashCode(), and toString(), remove the green comments and Javadoc them to describe how the methods work in Faculty. Do NOT delete the @Override annotation.
Run CheckStyle to ensure that your Javadoc has all elements.
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.
Reminder: Staging and Pushing to GitHub
GitHub Resources:
Check Jenkins
Ensure that your Jenkins job is reflecting the results that you expect for the level of completion of your lab assignment.
Reminder: Interpreting Jenkins
Check the following items on Jenkins for your last build and use the results to estimate your grade: