In the last week, I produced a new screen, which now completes the new navigator.<\/p>\n\n\n\n
My new objective was to construct a new screen after linking the API with the navigator last week. as the prior wasn’t too difficult to make
This screen is connected to create API, and it has two API queries, just like last week. The first is a GET request, followed by a POST request.<\/p>\n\n\n\n
Following that, I began creating databases to test if there were any bugs. After experimenting with several cases, I discovered that there is something wrong with the answers, as the server provides a 200 status response and accepts the request when it should be an error. Mr. Peter saw the bag and is now repairing it. <\/p>\n\n\n\n
Mr. Peter was really concerned about it, so I saw the benefit of the automation testing that I had done previously. By adopting a variety of scenarios, automation testing aids in the detection of any issues.<\/p>\n\n\n\n
Add pagination to the two list view screens, and this time the page number and size are provided with the request, rather than dividing the pages as I obtain the data as before.<\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
In the last week, I produced a new screen, which now completes the new navigator. My new objective was to construct a new screen after linking the API with the navigator last week. as the prior wasn’t too difficult to makeThis screen is connected to create API, and it has two API queries, just like … <\/p>\n