Recyclone
Testing
Our main focus of testing was user-acceptance test. Ultimate goal of our project is to service well working app to users, so we concentrated on user's satisfaction and unexpected errors. Before acceptance test, our test was basically held step by step following the order of development.
Testing for UI performance was basically held by simulator provided by Xcode and Android Studio. During this period, test of back-end and front-end was carried out seperately. When overall front-end and back-end developments were finished, we tested connection between back-end and front-end by deploying application to mobile devices due to camera function and GPS system. After connetion is fully made, we checked accuracy of our application checking if it is returing wrong value or showing errors.
Finally, user-acceptance test was held with fully-working application. In order to collect reliable data, testers were selected from diverse background and assigned to use expected mode of app based on their background.
Flutter supports both iOS and Android, however each platform requires additional process to optimise the performance. So we had to check compatibility for each OS. Our version of Flutter app supports Android(API 16 & above) and iOS(iOS 8 & above) supporting majority of smartphone users. Compatibility test was held with four different devices with different softwares.
Android app was built on device through Android Studio using Window desktop. iOS app was built on device through Xcode using MacBook.
| Installation | Result | |
| iphone 8+ (iOS 14.4.1) | Success | Cannot enter the app |
| iphone 11 (iOS 14.3) | Success | Avaiable at beginning, but the app was constantly lagging or stopping |
| Galaxy S10 (Android 10) | Success | Fully working |
| Galaxy S20 (Android 11) | Success | Fully working, Very smooth |
Table. Result of Compatibility Test
The result was different due to gap between Android and iOS such as system permission policy. Mostly our work was based on Android studio and Android devices because it was our first main targetting platform (Android is in leading position of OS market containing 71.93% of market share), so our app caused some issues to iphone. Also, we had limited time for small members to debug another OS, so we decided to leave our app having potential to easily expand. This task is discussed with our client, and we received the reply that he is satisfied enough with current state.
As we mentioned, user-acceptance test was held with various testers based on the profile. Due to our decision from Compatibility test, the test is held with Android phones.
| Test Case | Pros | Feedback for Improvements | |
| Junho (University Student) Customer Mode |
Beginner case: Login, Intro, Choose your fate, Diffculty check |
*Nice Intro Screen *Good idea to set customer's preference in the beginning. *Not difficult to use after knowing manual. |
*Hope there is some tutorial to guide each features in app. *Hard to take photo until app recognise product. *It will be good if you add other signing method. |
| James (Office Worker) Customer Mode |
Normal customer case: Performing quest |
*Clear info of each quest *Like the incentive system *Managable amount of quests |
*Think location of QR ID might need to be changed *Diverse requirement to reach each level. |
| Isabel (Ual Student) Customer Mode |
Overall review of views | *Nice and slick UI *Smooth and nice animating graphic |
*Support light mode |
| Min (Engineer) Manufacturer Mode |
Verification Process | *Fast QR ID recognision *Handling unmanagable verification |
*Verification to check if the quest is what I requested |
| Jason (Working in Manufacture Company) Manufacturer Mode |
Requesting Process | *Easy to request the items. | *Type of material is too roughly categorised *Hope there is system to consider quality of materials. |
created with
Website Builder Software .