You are using an outdated browser. For a faster, safer browsing experience, upgrade for free today.

Loading...

Testing Strategy


To ensure that our application works as expected, we have tried to test the application for a limited period of time. We first carried out manual testing to check that the front-end, which uses virtual data and back-end displays, was working correctly. We then tested the integration of the back-end with the front-end H5 App, the back-end with the Admin Dashboard and the back-end with the database through integration testing. Also, integration tests were used to test the integration of the APIs connecting the front and back ends. We then tested the website and App for compatibility. Afterwards, we tested our website for responsive design testing. Finally, we found several testers to experience our app and give us feedback, as shown in the image below.

Features we tested for H5 App
  1. AR Visibility
  2. Login and Registration
  3. Template Post
  4. Search Templates
Features we tested for Admin Dashboard
  1. Login and Registration
  2. User, Comments, Articles, Saved, Likes, Category Management
  3. Add and delete models
Features we tested in backend application
  1. Get request and handel request
  2. Generate viewable files and API files
  3. File Upload
  4. Authentication system

Backend Server Testing


Tools & Dependencies

  • The tool we used to test APIs
  • Apifox = Postman + Swagger + Mock + JMeter, with functions such as API document management, API debugging, API Mock, and API automated testing.

    In order to test the backend, we set up a development environment and a test database to be separated from the production environment, and our production environment database will be automatically backed up once a day to ensure data security. The test database is based on a simulated version of the production environment database

    We wrote a total of 23 Test cases, defined 6 groups of Test Suites, and defined 6 Data Schemas to generate mock data test backends. By using Apifox, we completed automatic testing.

    This is a group in Test Suites, which contains 5 test cases to test APIs for User. It uses data schema and Regex to generate test data, which is sent to our testing backend which connects to the testing database

    Overall, we passed all test cases and generated a test report


    Non-Functional test

    Not only functional tests are performed, but the results are judged based on the results of the front-end and database. We also perform non-funtional tests to predict possible situations that may affect user usage

    We tested

    1. Response Times: if APIs are not working quickly then our application will appear to be slow. Identifying when a back-end server is taking too long to respond can help increase the quality of our application.
    2. Response Data: Whether the user can find the problem based on the returned code or text

    Compatibility Testing


    To check whether the H5 app is capable of running on different devices, operating systems or software, We tested our H5 app to make sure that it works in different Mobile systems and different browsers. We have found the app working ok on all of our available IOS and Android devices.

    For the admin dashboard, we tested it on three browsers across three operating systems with "BrowserStack" - a compatibility and responsive testing platform for web applications and mobile applications The results show that the web application is compatible with all the browsers that comply with the requirements. The results show that the web application is compatible with all ES5 compliant browsers.

    Responsive Design Testing


    For responsive design testing, we can use Chrome Developer Tools to test on different screen sizes on mobile and PC. Our website application has passed all tests on different screen sizes. Here are some screenshots from when we tested different sized website applications.

    Performance & Stress Testing


    To determine how responsive and stable the application performed under a specific workload, we performed load testing using the open source load testing tool https://k6.io/, the simplest form of performance testing our API . All API tests passed, here is one of the screenshots while testing our API.

    User Acceptance Testing


    To see how we did with our work, we decided to go back to 3 users that previously gave us our inputs and see how we managed. For the sake of anonymity, we replaced their names and stories with that of similar personas we’ve made or thought of.

  • Test case 1 : view a greeting
  • Test case 2 : search for specific greetings
  • Test case 3: send a greeting
  • Test case 4: edit a greeting on plugXR and post it
  • Test Users
  • Test case 1 : view a greeting
  • Yuni S. Tudent 19 year old university student
  • Maple Hopkins, 46 year old lawyer
  • Dyne O’saur, 22 year old University Student
  • Acceptance requirement Heavily disagree disagree neutral agree heavily agree comments
    Greetings are easily viewable 1 2
  • The instructions on screen make it easy
  • The models sometime come out a bit large and need to be adjusted
  • The search function is efficient 3
  • could find the templates I’d want to use easily
  • Sending greetings is simple 3
  • It's either just a link or a QR code to send, anyone can do that
  • Greetings are easy to edit on PlugXR 3
  • it's easy to upload your own models and convert them to the right format
  • the pre-made models are very useful
  • Posting models is simple 3
  • comes up on the find section as soon as I go there
  • Is the UI nice to use 1 2
  • looks a bit weird on large screens but perfect on phone
  • Conclusion

    We are quite happy that users seem to enjoy their experience with the app, and their comments have given us ways to further improve the app’s user experience.