A good testing strategy doesn't only focus on web testing. Instead, it tackles risks at all levels of the system.
In this repository, you will find a cohesive Greybox (we have some insight into the app code) testing strategy using:
✅ Browser testing on desktop
✅ Browser testing on mobile
✅ Visual testing
✅ CICD pipeline executed on push and PR
✅ Sauce Labs cloud infrastructure
| 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, Screener.io |
| Every web page of the app looks correct on mobile | ✅ | Visual test | A visual test efficiently validates app rendering | Selenium, Screener.io |
| 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 |
| Front-end performance is at least an A | 🙅♂️ | Front-end performance test | Front-end perf 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 |
- See main README
- Run all the tests inside of the
best-practicedirectory
cd best-practice
mvn clean test
cd best-practice
mvn clean test -Dtest=Visual