Skip to content

Commit

Permalink
Merge pull request #355 from turingschool/rancid
Browse files Browse the repository at this point in the history
Rancid
  • Loading branch information
hfaerber authored Nov 5, 2024
2 parents 82dd6a6 + 103a4e8 commit 1154a1b
Show file tree
Hide file tree
Showing 3 changed files with 15 additions and 9 deletions.
2 changes: 1 addition & 1 deletion module1/lessons/chatgpt.md
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ Try the following prompts:
- Can you show me how you would solve the first prompt you wrote?

**Stop and Reflect:**
- What ChatGPT able to create a useful data set for you to practice with?
- Was ChatGPT able to create a useful data set for you to practice with?
- What did you think of the prompts it came up with?
- When might you use this in the future?

Expand Down
18 changes: 12 additions & 6 deletions module3/projects/rancid_tomatillos/evaluation.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ Your presentation should cover the following points:
## Rubric

<section class="dropdown">
### Collaboration and Professionalism
While this is not a scored rubric section, every team member is expected to fully participate, contribute, communicate, and collaborate with the team throughout the entirety of this project. **Failure to do so can result in an individual failing the project, even if the group/project is otherwise passing.**
### Collaboration, Professionalism & Presentation
Every team member is expected to fully participate, contribute, communicate, and collaborate with the team throughout the entirety of this project. **Failure to do so can result in an individual failing the project, even if the group/project is otherwise passing.**

We expect all teammates to:
* Hold daily standups throughout project.
Expand All @@ -46,6 +46,14 @@ We expect all teammates to:
* Screenshots/gifs of your app
* Links to contributors' GitHub profiless
* Collaborate effectively to accomplish the shared goal. Team productively and professionally works through challenges and conflicts to ensure all team members are able to be heard and contribute throughout the project. Instructors are available to offer support and guidance but conversations around what *is* and what *is not* working are expected to be led by the team members themselves.

We expect your video presentation to:
* Cover all the required presentation points
* Clearly and concisely present technical topics
* Use professional and technically accurate vocabulary
* Demonstrate competency and professionalism for each team member

Note: You will not be graded on how high quality or well-edited your video is, only the content and delivery of your presentation.
</section>

<section class="dropdown">
Expand Down Expand Up @@ -78,11 +86,11 @@ We expect all teammates to:
- Tests make specific assertions about the content DOM elements contain
- Network requests are properly stubbed (intercepted)
- Happy path async functionality is stubbed and tested
- Sad path functionality is stubbed and tested

**Exceeds Expectations** can look like:
- Sad path async functionality is stubbed and tested
- Implements Cypress `alias` and `wait()`
- Implements Cypress `fixture`
- Implements Cypress `alias` and `wait()`
- Implements Cypress `command`

</section>
Expand All @@ -94,7 +102,5 @@ We expect all teammates to:
- Application uses Router to display appropriate components based on URL
- The user has access to previous routes via the back/forward buttons
- Code was refactored to remove unnecessary or old code artifacts

**Exceeds Expectations** can look like:
- A 404 page handles unknown routes. *You can check this by going to localhost:3000/nonsense*
</section>
4 changes: 2 additions & 2 deletions module3/projects/rancid_tomatillos/technical_requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -169,8 +169,8 @@ We've also given you some mock data to use for your testing. You can find those
- As a user, when I load the application, I see a collection of movies.
- Note: When testing a collection of elements, it's good practice to check that...
- The number of elements we expect to be there are there (i.e. there are 4 movie posters)
- The first element contains all the information we'd epect (i.e. correct image and vote count)
- The last element contains all the information we'd epect (i.e. correct image and vote count)
- The first element contains all the specific data details we'd expect (correct image, vote count, etc)
- The last element contains all the specific data details we'd expect (correct image, vote count, etc)
- As a user, when I click on a movie, I'm shown additional details about that movie.
- Note: We want to check ALL details. Just checking Title is not enough.
- As a user, when I upvote a movie, I see the movie's votes increase by one.
Expand Down

0 comments on commit 1154a1b

Please sign in to comment.