Debugging Event

[parkib]

Debugging ! Prakruti Bhatt Period 2 Mortenson March 4th

• [X] Start backend using Debugging The picture below showcases the backend, enabled by debugging

• [X] Set break point at the beginning of endpoint code The picture below indicates the beginning of the endpoint code and the cherry red dot on line 15 is representative of the added breakpoint

• [X] Start in frontend with split screen loading source for an API fetch using GET. I have started the frontend and then split-screened to see the API fetch to the port 8923

• [X] Set break point on fetch, inside .then, inside .fetch In the picture below, I have set breakpoints on fetch, the body, .then, and .catch

• [x] Run frontend, screen capture break at fetch while examining Body Here I inserted inputs into the frontend to run it, then captured the break at fetch. This has paused at the fetch breakpoint (highlighted in yellow)

• [x] Press play on frontend, observe stop inside of backend When I press play on the frontend, I get a message from the localhost saying that the quote failed to submit (there is an error). When I view the backend, we can see that there is a stop on line 15.

• [X] Press step over on backend until you have obtained data from database, screen capture Python Object Step over in backend

• [X] Press play button to end backend debugging session.

Ended backend debugging session

• [X] Return to frontend debug session when pressed play on frontend the quote is now submitted succesfully

• [X] Step in until you see data, screen capture capturing break point and Data.** quote stored now on backend-- data

[vibha-yganji]

0.86; shows good understanding of how to use the breakpoints to fix the errors, but could show a bit more on the Python object in the backend instead of the schema table.

[jm1021]

The run at the beginning is loading wrong file. Not sure data screen are show key data from database read.