Update README.md

README.md

@@ -4,27 +4,27 @@ For [this assignment](https://education.launchcode.org/java-web-development/assi
 
 Assignment Requirements:
 
-* finishing portions of a few classes
-* writing unit tests in a TDD fashion
-* using abstraction and inheritance strategically by refactoring the classes.
+1. Review Sally’s code in the Employer class to learn how to assign a unique ID.
+2. Add getters, setters, and custom methods as needed to the Location, CoreCompetency, and PositionType classes.
+3. Complete the Job class using what you learned in steps 1 and 2.
+4. Use unit testing to verify the constructors and equals methods for the Job class.
+5. Use TDD to design and code a custom toString method for the Job class.
+6. Use inheritance to DRY the code within Employer, Location, CoreCompetency, and PositionType
 
 ## Unit Tests
 
 The starter code contains 6 unit test classes.  Each class contains tests for each main task of the assignment.  This allows students to run tests upon completion of a task before moving on to the next one.
 
-`TestTaskTwo` verifies that students completed the `Location`, `CoreCompetency`, and `PositionType` classes.
+1. `TestTaskTwo` verifies that students completed the `Location`, `CoreCompetency`, and `PositionType` classes.
+2. `TestTaskThree` verifies that students created the `jobClass` and that it uses the other classes correctly to create `job` objects.  
+3. `TestTaskFour` verifies students' unit tests exist within the application.  
+4. `TestTaskFive` tests the unit tests the students created for their custom `ToString` method.  
+5. `TestTaskSix` verifies that students used proper inheritance between `Location`, `Employer`, `CoreCompetency`, `PositionType` and `JobField`.  For example, `Employer` should extend `JobField`.  These tests focus on the existance of the extension rather than the behavior of the extension. 
+6. `AbstractTest` verifies the behavior of the DRY code.  
 
-`TestTaskThree` verifies that students created the `jobClass` and that it uses the other classes correctly to create `job` objects.  
+As you work on the components of the given tasks, continually re-run the tests to see the failing tests gradually turn to passing. When all tests within the file pass, you’re ready to move onto the next task.
 
-`TestTaskFour` verifies students' unit tests exist within the application.  
-
-`TestTaskFive` tests the unit tests the students created for their custom `ToString` method.  
-
-`TestTaskSix` verifies that students used proper inheritance between `Location`, `Employer`, `CoreCompetency`, `PositionType` and `JobField`.  For example, `Employer` should extend `JobField`.  These tests focus on the existance of the extension rather than the behavior of the extension. 
-
-`AbstractTest` verifies the behavior of the DRY code.  
-
-Submission cannot be graded on unit tests alone.  The tests will provide answers to the code checks below, but should not replace a live demo.  Use the section below as a guide for what to look for before submitting your assignment.
+Once you have completed the assignment, please follow the submission instructions at the bottom of this ReadMe.md
 
 ### Appearance and Output:
 
@@ -58,8 +58,4 @@ Core Competency: Tasting ability
 ## Submitting Your Work
 
 To submit your work please follow the [Submission Instructions](https://education.launchcode.org/java-web-dev-curriculum/assignments/hello-world/index.html#submitting-your-work-on-canvas).
-
-Does the hardcoded job data in `Main` print when the application is run?
-
-Will an additional job be printed with a unique ID? Ask the student to create a new
-`Job` object in Main. Verify that it gets printed with a unique ID.
+