Documentation of User Testing and Unit Testing

[freddychenyouren2]

Started on 18 July 2023

Start Documenting result of User Testing, interpret and write any actions taken in terms of code implementation improvement. Bugs squashed, UI/UX enhancement, and so on.

For Unit Testing, we shall present it similar to User Testing, where we provide the results for every screen and write test descriptions, test objectives, steps taken, and other test details in a table format.

[freddychenyouren2]

Progress as of 19 July 10.40am:

• User Testing: Collated and updated in ReadMe

• Unit Testing: Authentication side (Handled by both Freddy and Cedric). Done with LoginScreen and SignupScreen. OnboardingScreen still working on it.

• Unit Testing: Customer Screens (Mainly handled by Freddy). Done with Activity, Personal ID, and Account Screen. Customer Homescreen still working on it.

• Unit Testing: Seller Screens (Mainly handled by Cedric). Done with Activity Screen. Homescreen, Scan QR screen, and Account screen still working on it.

• Unit Testing: Others. AppStack (Customer) is done by Freddy. AppStackSeller is being worked on by Cedric.

Progress: 7 / 13 files complete

[freddychenyouren2]

Update from Freddy as of 23 July 4.30pm:

• Automated Testing on the Customer Home Screen has included as many tests as possible. Conducted further testing on app behaviour due to some refactored code implementation to ensure the app still runs well. Tested on 22 July 11pm.
• Onboarding Screen test is flagged as marginally acceptable as minimum testing is done. We are focusing on testing more crucial app functionalities in other files first for MS3 submission.
• Solved more jest mock issues with Cedric on Cedric's test files. Cedric is completing Seller Home Screen and Account screen. Left with Scan QR Screen.

Progress: 12 / 13 files complete