testing plans - amanda-zambrana/What2Wear GitHub Wiki
Testing Plans
Performance Testing
Main Goal: Ensure the app performs well under various conditions.
- Speed Testing: Ensure smooth and fast transitions between screens and minimal delay touching user images and data.
- Tasks include: measure time to load wardrobe inventory, outfits, style boards. Measure time to load items from firestore into outfit shuffle as well as the time taken to shuffle a new style.
- Tools: Firebase performance monitoring
- Metrics include: page load time, screen to screen transition time
Usability Testing
Main Goal: Evaluate user satisfaction and ease of navigation through the app.
- UI/UX Navigation Testing: verify that the app's main features are easy to locate and use; gather user feedback and make implementations to the application based on them to achieve better user satisfaction
- Testing scenarios may include (but are not limited to): sign up/login, add new items, create outfits, browse outfits, create style boards, browse and edit style boards, schedule an outfit in calendar, interact with smart shuffle, and smart weather suggestions.
- Tools: UserTesting, new user human testers
- Metrics include: success rate of tasks, time taken to complete tasks
Reliability Testing
Main Goal: Ensure consistent and error-free performance over time, establishing reliability
-
Compatibility Testing: test the application on multiple different devices to ensure that it runs smoothly and has portability
-
Crash/Bug Testing: identifying mitigate causes of app crashes and app bugs.
- Tools: Firebase Crashlytics
- Unit Testing
- Tools: JUnit for frontend unit testing and Jest for backend unit testing
Security Testing
Main Goal: Ensure protection of user data including account information, clothing, item, images, and outfits/boards created.
- Authentication and authorization Testing: ensure that user account information and user data is protected