🏷️ backlog for sprint 3

Full-Stack-Project-Assessment 🔗

Enable frontend unit tests on pull request 🔗 Clone

Acceptance criteria

  • Frontend unit tests run on every new pull request

Guidance 🧭

Check Testing guide for steps to make your frontend unit tests run on every pull request.

  • 📅 Week 3
  • 🎯 Topic Testing
  • 🏝️ Priority Stretch
  • :framed_picture: Frontend
Frontend unit tests 🔗 Clone

Acceptance criteria

  • All frontend unit tests are passing

Useful links 🔗

Check the Testing guide to set up your frontend tests

  • 📅 Week 3
  • 🎯 Topic Testing
  • 🏝️ Priority Stretch
  • 🔌 Backend
Backend unit tests 🔗 Clone

Acceptance criteria

  • All backend tests in api.test.js are passing

Guidance 🧭

Check out the testing guide to setup your backend unit tests

  • 📅 Week 3
  • 🎯 Topic Testing
  • 🏝️ Priority Stretch
  • 🔌 Backend
Video voting buttons 🔗 Clone

Acceptance Criteria

  • Each video displays its current rating in a visually clear manner (e.g., thumbs up /thumbs down icons, numeric display).
  • Users can increase the rating of a video (“thumbs up”).
  • Users can decrease the rating of a video (“thumbs down”).
  • A user’s rating actions are recorded and persist across sessions.

Example

Check this example Video voter example to see how this issue could be implemented.

  • 📅 Week 3
  • 🧩 Feature
  • :framed_picture: Frontend
Update videos endpoint 🔗 Clone

Acceptance criteria

  • There is an endpoint available for updating video ratings
  • The endpoint accepts an appropriate HTTP method
  • The endpoint has an appropriate URL
  • The endpoint updates the ratings of videos in the database
  • 📅 Week 3
  • 🔌 Backend
User story: Allow rating of videos 👍 👎 🔗 Clone

Description

You pass around your project among your friends, and they like it better than the first version you showed them last week. They are enthusiastic and want to let you know which videos they also liked, and which they didn’t! Implement ratings - allowing other users to give your videos a thumbs up or a thumbs down!

User story 👩🏽‍💻

Required issues 🎫

  • #473
  • #474
  • #475
  • 📅 Week 3
  • 📅 Databases
  • 👩🏽‍💻 User story
[TECH ED] Levels 400 🔗 Clone

https://github.com/CodeYourFuture/Full-Stack-Project-Assessment

Why are we doing this?

Find the levels 400 (all 400 levels) and break down the work into tickets. Plan out your approach and get cracking.

Maximum time in hours

4

How to get help

Open draft PRs and ask for review, stating clearly where your blocker is.

Work on your project in Study Group class time and get live help from mentors.

How to submit

Find the submission steps and follow them.

  • 📅 Week 3
  • 📅 Databases
  • 🎯 Topic Delivery
  • 🎯 Topic Iteration
  • 🎯 Topic Problem-Solving
  • 🎯 Topic Requirements
  • 🔑 Priority Key
  • 🦑 Size Large
[TECH ED] Levels 300 🔗 Clone

https://github.com/CodeYourFuture/Full-Stack-Project-Assessment

Why are we doing this?

This project requires you to do a lot of reading and finding out where docs are. You will have to do this all the time in your job as a developer. It’s a daily task.

Find the levels 300 (all 300 levels) and break down the work into tickets. Plan out your approach and get cracking.

Work on your project during the week, during class day, and in study sessions. Ask for online study sessions with mentors on Slack.

Maximum time in hours

6

How to get help

Open draft PRs and ask for review, stating clearly where your blocker is.

Work on your project in Study Group class time and get live help from mentors.

How to submit

Find the submission steps and follow them.

  • 📅 Week 3
  • 📅 Databases
  • 🎯 Topic Delivery
  • 🎯 Topic Iteration
  • 🎯 Topic Problem-Solving
  • 🎯 Topic Requirements
  • 🔑 Priority Key
  • 🦑 Size Large