This project demonstrates:
✅ Browser testing on desktop
✅ Browser testing on mobile
✅ Visual testing
✅ CICD pipeline executed on push and PR
| Expected Behavior | Tested? | Test Type | Rationale | Tech |
|---|---|---|---|---|
| Every web page of the app looks correct on desktop | ✅ | Visual test | A visual test efficiently validates app rendering | Selenium |
| Every web page of the app looks correct on mobile | ✅ | Visual test | A visual test efficiently validates app rendering | Selenium |
| A user can successfully check out on desktop | ✅ | Functional web test | Functional testing of the most critical functionality is important | Selenium |
| A user can successfully check out on mobile | ✅ | Functional mobile test | Although redundant to a functional web test, it's relatively easy to test this on a mobile device as well | Appium |
| App is accessibility friendly | 🙅♂️ | Selenium web test | Accessibility in applications is becoming extremely important | Selenium, axe-core |
| Front-end performance is at least an A | 🙅♂️ | Front-end performance test | Front-end performance is an important aspect of any digital quality effort | Selenium, Sauce Labs |
| Test code runs on every commit in under 5 minutes | 🙅♂️ | CICD | Slow feedback makes it hard to iterate | Github Actions |
| App is secure | 🙅♂️ | Not covered here, but something to consider for testing strategy |
- For full instructions on getting tests up and running, see the main README file
- Run all the tests inside the
best-practicedirectory
cd best-practice
mvn clean test