I spend my third week mostly working on a complex command Update and fixing bugs in my code.<\/p>\n\n\n\n
I started off the week by adding more test cases in the Repository test file, the purpose behind this was to test if my repository is correctly performing the CRUD operations. After this, I realized that I\u2019m yet to write test cases for data which should have been done once the entities were created as these test cases help ensure the data type of each field is consistent.<\/p>\n\n\n\n
Next, I shifted my focus to correctly format my API test cases, of Create and Delete, according to the norms of 3 A\u2019s which are Arrange, Act and Assert. Moreover, I improved my test cases by adding more assertions. <\/p>\n\n\n\n
Finally, I started on coding the logic of the Update command which was challenging because Updating every field can have multiple possibilities.<\/p>\n\n\n\n
After coding the logic I realized there was a bug which was occurring when an existing line item was removed and a completely new one was added. Once the bug in the UpdateHandler was fixed, I added the controller which handles the whole PUT request.<\/p>\n\n\n\n
Lastly, I moved my focus on testing the Update Command. On running the test case gave me an error report ‘database operation expected to affect 1 row(s) but actually affected 0 row(s)’ error. <\/em>After a lot of unsuccessful debugging I finally sought help from my supervisor who helped me find the bug and explain to me the root cause of it. This error was due to the primary key which I was hardcoding inside my update logic. We are not supposed to set the primary key as the database does it for us automatically.<\/p>\n","protected":false},"excerpt":{"rendered":" I spend my third week mostly working on a complex command Update and fixing bugs in my code. I started off the week by adding more test cases in the Repository test file, the purpose behind this was to test if my repository is correctly performing the CRUD operations. After this, I realized that I\u2019m … <\/p>\n