Debugging Review

[jplip]

Debugging/Tracing code...

Build a code debugging blog using this as a guideline. Be sure to read canvas to optimize opportunities for points.

1. Start backend using Debugging

2. Set break point at the beginning of endpoint code

Looking for why my login doesn't work and can't sign in.

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

Set break points in the frontend as well to catch the fetch issues.

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

Looking at the user data that is inputed from the frontend to the backend.

8. Press play button to end backend debugging session.

The problem is the user or password.

9. Return to frontend debug session

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

Knowing the problem, I figure out the name or password is wrong and change the username.

It works and problem was user id. This then redirects to the update page of all accounts in the database.

[jm1021]

Good sequence of steps. Good illustrations at showing data. Perhaps a little more clarity on which line you were at when you shared the data.

[iKAN2025]

1.85 Sequence of Steps/Everything Completed Had stuff working

[Lin-cT]

I like that it clearly shows the images and body, and I am able to follow through the steps. Very concise, but I feel like some extra comments talking about the code would have been nice.

1.85/2.0