Merge branch 'code-differently:main' into Lesson_16

Author: haldanek

.github/workflows/check_push.yml

@@ -18,6 +18,9 @@ on:
       - "lesson_13/maps_java/**"
       - "lesson_13/maps_ts/**"
       - "lesson_14/exceptions/**"
+      - "lesson_15/tdd/**"
+      - "lesson_16/objects/**"
+      - "lesson_17/bank/**"
 
 jobs:
   build:
@@ -125,4 +128,14 @@ jobs:
 
     - name: Build Lesson 15 with Java
       working-directory: ./lesson_15/tdd
+      run: |
+        ./gradlew assemble
+        ./gradlew spotlessCheck
+
+    - name: Build Lesson 16 with Java
+      working-directory: ./lesson_16/objects
+      run: ./gradlew check
+
+    - name: Build Lesson 17 with Java
+      working-directory: ./lesson_17/bank
       run: ./gradlew check

project_oop/README.md

@@ -3,7 +3,7 @@
 
 ## Introduction
 
-For this project, you and your teammates are tasked with modeling a real-world problem using object-oriented and SOLID design principles, from ideation to implementation.
+For this project, you and your teammates are tasked with modeling a solution to a real-world problem using object-oriented and SOLID design principles, from ideation to implementation.
 
 ## Prerequisites
 
@@ -17,7 +17,7 @@ Before starting work on your project, you will need to submit three user stories
 * One of your objects must be a custom data structure that provides for adding, removing, and updating items in a collection.
 * Implement at least two custom exceptions.
 * Write unit tests achieving 90% code coverage (using JaCoCo for Java or Jest for Typescript).
-* Must include an integration test.
+* Must include an integration test for each user story that demonstrates how your code implements the desired feature.
 * Your solution must illustrate each of the SOLID principles.
 * Each team member must contribute *at least one* submitted pull request containing working code and tests.
 * Include a README for your repo describing the problem you're solving, the solution, and how you would improve your solution.
@@ -38,10 +38,10 @@ Design a CLI that allows users to interact with your application. Check out the
 
 ## Timeline
 
-* Submit three user stories (Monday, 11/4 5PM ET)
-* Receive approval for your user stories (Tuesday, 11/5 1PM ET)
-* Finish code commits (11/8, 1PM ET)
-* Give presentation (11/11, 1PM ET)
+* Submit three user stories (Monday, 11/4, 5PM ET)
+* Receive approval for your user stories (Tuesday, 11/5, 1PM ET)
+* Finish code commits (Friday, 11/8, 1PM ET)
+* Give presentation (Monday, 11/11, 1PM ET)
 
 ## Grading