Author: Mohammedi Khalil

I finished testing the app the week before and began designing the new system’s prototype.

I was able to continue testing the App after having found a solution to the issues that I had encountered last week.

Except for the ImageItemView, I finished testing all of the navigation components. The testing was not tough for the ItemListView, which was 100% tested, but I couldn’t test the image Picker for the ItemAdjustmentDetailView, which turned out to be difficult to test after I attempted several methods to mock and test the function. However, the attempts were in vain. After many attempts, Peter advised me to ignore it.

My next task after the testing is to add some additional screens to the software that was tested. To begin, I must design the interface for that screen, which I will accomplish using other tools because I am familiar with it and have previously used it, as well as creating a prototype of how the app would work.

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 completed previously.

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.

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.

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.

On the previous week I completed the testing for the LoginView component.

I examined all of the scenarios on the LoginView testing unit, starting with the components’ UI. Then the alert comes when an unknown user tries to l. Lastly, the successful login.

The Axios mock adapter, which performs such magic work with the endpoints callback, was a new mocking technique I learnt that was really handy in mocking the promises and providing false responses to make the fetch work.

Finally, I tested the next unit’s UI, which was the ItemListView, as well as the searching function, using the same approach that I did on the LoginView with different HTTP request methods.

In my second week, I was trying to solve the problem that I had faced during the testing. I spent most of my time trying to solve the problem that I have faced in the testing. So I have tried many types of mocking to reach the solution, but unfortunately, all the tries still couldn’t solve it.

However, this problem helped me a lot in understanding the concept of testing, where it gave me the opportunity to deal with many different types of mocking or rendering. I became more confident with testing .

I made my first commit and pushed it into the project file, after I opened a branch called “Testbranch” , I committed to the settings that I had made in the testing setup.
Finally, I used the breakpoint for the first time, where I did the setup and made it useful in the Visual Studio Code. After that I started using it to keep track of the problems that I have faced .

My first week is like any new student who starts a new job in a new environment where things start to blur. However, I started learning a new thing to make the fog fade away. 

On the first day and second, I started learning about Git. It was my first experience with it since I used to only know about it. I was able to create a repository and I played around with it, learning how to add taggs, files and commit to it. I also used the clone where I cloned Peter’s project to my desktop and learnt about the git-flow and how to push the feature.

In the next days, I was trying to fix the configuration of the project (testing confusion and also visual studio code configuration), and I also learned about I also started learning how to deal with testing since my first task is to test the company’s system, so I took my first step and I understood the concept of testing and saw some of the examples.

Besides that, I learned about asynchronous and synchronous programming and the differences between the two programming styles, and I referred to some exercises online.