Individual seed/debugging

[ellierozen]

3.0 Seed, as well as 2.7 Seed requirements

• [x] 92% or better in class
• Finished with 93.9
• [ ] CPT project is deployed
• ishraq (devops) ran into problems but lopez said this is okay
• [x] Teacher markers are removed from your CPT project.
• no more nighthawk pages , toby, etc.

2.7

• [x] Make sure GitHub Pages blog is up to date

• https://ellierozen.github.io/csp3-repo/compsci

• [x] CPT draft of project

• https://ellierozen.github.io/csp3-repo//2024/01/12/cpt-wopo.html

• [x] Personal copy of CPT project. Make sure you have Frontend and Backend for CPT project ready for additional work. Since teams will be split up by registration... you should make team repos a template and everyone should make a personal copy (both frontend an backend)

• [x] Students that are collaborating with other students in achieving 2.7 or higher in seed

• I am very collaborative!!

• Peer graded with nikki for our cpt

DEBUGGING Backend

• This was actually the same breakpoint I had to set during the project because I was having problems with my stats api and i needed to make sure that it was at least receiving the stats i was inputting

I have already stepped in so that I could see what is in body

FRONTEND

1. Start backend using Debugging

2. Set break point at the beginning of endpoint code

3. Start in frontend with split screen loading source for an API fetch using GET.

4. Set break point on fetch, inside .then, inside .fetch

5. Run frontend, screen capture break at fetch while examining Body

6.Press play on frontend, observe stop inside of backend

7.Press step over on backend until you have obtained data from database, screen capture Python Object

8.Press play button to end backend debugging session.

9. Return to frontend debug session

10. Step in until you see data, screen capture capturing break point and Data.