For the past week I have worked on integration tests as well as checking the creation of modules for errors. <\/p>\n\n\n\n
The checking involved checking whether a Tax, Supplier, PurchaseOrder, GoodsReceived and PurchaseInvoice can be created successfully without any errors, as well as checking the content inserted into the views. <\/p>\n\n\n\n
When using tab navigation, the tests created will not be able to mock the NavigationContext, which will always lead the test being run to use the default value instead of navigating to the wanted and requested view of PurchaseInvoice, either from PurchaseOrder or GoodsReceived. Hence, to solve this problem another method is creating which includes parameters that carry the designated values, which will then be called from the method which includes the NavigationContext. <\/p>\n\n\n\n
Next, when adding LineItems using the Add button in PurchaseInvoice from GoodsReceived, only 1 line item is updated and the errors lied because I did not map the LineItemId. <\/p>\n\n\n\n
Lastly, I started working on displaying a dialogue box when a PurchaseInvoice already exists. The test has been created with the help of my supervisor. <\/p>\n\n\n\n
See you all on my last blog Next week \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
For the past week I have worked on integration tests as well as checking the creation of modules for errors. The checking involved checking whether a Tax, Supplier, PurchaseOrder, GoodsReceived and PurchaseInvoice can be created successfully without any errors, as well as checking the content inserted into the views. When using tab navigation, the tests … <\/p>\n