While the testing was in progress, we discovered that we were testing from the cache, so I cleared the caches, and the errors reappeared. <\/p>\n\n\n\n
After clearing the caches and modifying the setup so that the test does not utilise caches, I was unable to render any component, including the LoginView, which was meant to be completed previously.<\/p>\n\n\n\n
The navigation issue continued appearing, and I tried several alternative solutions but none of them worked until we messed up the setup. Fortunately, Mr. Peter reminded me to commit, and I was able to erase the modifications I made using GIT, demonstrating how important it is.<\/p>\n\n\n\n
After several tries and searches, Mr. Peter and I discovered that the navigation library had a flaw. That suggests we have no control over the situation. Someone on Stackoverflow has either encountered the problem or is aware of the flaw, and has offered a workaround in the form of a comment that must be written before the navigation. The comment makes it so that the navigation does not throw an error.<\/p>\n\n\n\n
Finally, we found a solution, and I continued to test the system. The progress was a little faster than the previous unit. After finishing the ItemListView, I moved on to the ItemAdjustmentDetailView. Everything seemed OK until I was testing the update function and discovered a bug in the fireevent when the button was pushed. I’m still looking for a solution to the problem of not being able to locate comparable issue online.<\/p>\n","protected":false},"excerpt":{"rendered":"
While the testing was in progress, we discovered that we were testing from the cache, so I cleared the caches, and the errors reappeared. After clearing the caches and modifying the setup so that the test does not utilise caches, I was unable to render any component, including the LoginView, which was meant to be … <\/p>\n