Skip to content

Commit

Permalink
Merge pull request #41 from tpenn/ga2-edits
Browse files Browse the repository at this point in the history
Ga2 edits
  • Loading branch information
jwoolbright23 authored Oct 3, 2023
2 parents d91e8ab + bf3d23a commit f721750
Show file tree
Hide file tree
Showing 3 changed files with 16 additions and 12 deletions.
10 changes: 5 additions & 5 deletions content/assignments/techjobs-oo/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ originalAuthor: Courtney Frey # to be set by page creator
originalAuthorGitHub: speudusa # to be set by page creator
reviewer: Kimberly Horan # to be set by the page reviewer
reviewerGitHub: codinglikeagirl42 # to be set by the page reviewer
lastEditor: # update any time edits are made after review
lastEditorGitHub: # update any time edits are made after review
lastMod: # UPDATE ANY TIME CHANGES ARE MADE
lastEditor: Terri Penn # update any time edits are made after review
lastEditorGitHub: tpenn # update any time edits are made after review
lastMod: 2023-09-01T12:52:10-05:00 # UPDATE ANY TIME CHANGES ARE MADE
---

## Assignment #2: Tech Jobs (Object-Oriented Edition)
Expand Down Expand Up @@ -52,7 +52,7 @@ In Canvas, **Graded Assignment #2: Object-Oriented Edition** contains a GitHub s
## Introduction
Sally has gotten the ball rolling by adding a `Job` class, along with classes to represent the individual properties of a job: `Employer`, `Location`, `PositionType`, and `CoreCompetency`. She completed the Employer class, and she left you the task of filling in the others.

As the team gets closer to deploying the app—and abandoning the test data they’ve been using—they’ll want an easy way to add and remove jobs via a user interface. Before that, however, you need to finish shifting the project to an object-oriented design.
As the team gets closer to deploying the app—and abandoning the test data they’ve been using—they’ll want an easy way to add and remove jobs via a user interface(UI). Before that, however, you need to finish shifting the project to an object-oriented design.

## Why Change to Object-Oriented?
Working with data stored as strings in HashMaps and ArrayLists isn’t a good long-term solution, for reasons that we point out below.
Expand Down Expand Up @@ -85,7 +85,7 @@ Additionally, the `toString()` method of the `Employer` class is set up to retur

```java
// Prints the name of the employer
System.out.println(job.getEmployer);
System.out.println(job.getEmployer());
```

Why do we go to all of this trouble when we could store this job-related data as strings? There are a couple of reasons.
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
18 changes: 11 additions & 7 deletions content/assignments/techjobs-oo/task4/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ originalAuthor: Courtney Frey # to be set by page creator
originalAuthorGitHub: speudusa # to be set by page creator
reviewer: Kimberly Horan # to be set by the page reviewer
reviewerGitHub: codinglikeagirl42 # to be set by the page reviewer
lastEditor: Courtney Frey # update any time edits are made after review
lastEditorGitHub: speudusa # update any time edits are made after review
lastMod: 2023-06-26T10:20:54-05:00 # UPDATE ANY TIME CHANGES ARE MADE
lastEditor: Terri Penn # update any time edits are made after review
lastEditorGitHub: tpenn # update any time edits are made after review
lastMod: 2023-09-12T13:54:20-05:00 # UPDATE ANY TIME CHANGES ARE MADE
---

Instead of manually creating sample `Job` objects to verify that your class works correctly, you will use unit tests instead.
Expand Down Expand Up @@ -42,10 +42,14 @@ Fill out the resulting form using the values:

1. **Name:** JobTest
1. **Java version:** Java 17
1. **Module:** `techjobs-oo.test`
1. **Class:** `org.launchcode.techjobs.oo.test.JobTest` (Click on the icon at the right side of this field and select the `JobTest` class from the modal that opens.)
1. **Module:** `techjobs-oo-java17-graded.test`
1. **Class:** `org.launchcode.techjobs.oo.JobTest` (You will need to type or paste this. If the class contained a test, you could also click the icon at the right of this field and select the class from the window that opens.)

Then hit _Apply_ and _OK_.
{{< rawhtml >}}
<img src="../figures/jobtest-junit-configuration.png" alt="JobTest Configuration Settings">
{{< /rawhtml >}}

Ignore the message that says _Class 'org.launchcode.techjobs.oo.JobTest' is not a test_ since you haven't written any yet. Then hit _Apply_ and _OK_.

To run the tests, select the _JobTest_ configuration from the configurations menu and hit the green _Run_ button.

Expand All @@ -67,7 +71,7 @@ Each `Job` object should have a unique ID that is an integer.
1. “Drat! I need to fix my `Job()` constructor code.”

{{% notice orange "Warning" "rocket" %}}
The answer is NOT “a”.
The answer is NOT “1”.

Your test code might be incorrect, but that should not be your FIRST thought. TDD begins with writing tests for desired behaviors. If the tests fail, that indicates errors in the methods trying to produce the behavior rather than in the tests that define that behavior.
{{% /notice %}}
Expand Down

0 comments on commit f721750

Please sign in to comment.