Basics of Performance, Security, and Accessibility Testing
summary
Run Lighthouse from Chrome DevTools to get client‑side performance metrics and prioritized fixes while doing functional flows; connect a phone to Apptim to capture mobile traces and CPU/network data during exploration; proxy the browser through ZAP and use manual exploration mode with alerts to surface security issues as pages are exercised; install aXe DevTools and run scans or keyboard/screen‑reader sessions to find accessibility barriers that block real users.
AI-written summary · about
chapters (6)
- 0:00Introduction to nonfunctional testing
- 1:55Performance testing with Lighthouse
- 6:31Security testing with OWASP ZAP
- 9:40Accessibility testing with axe DevTools
- 12:12Keyboard and screen reader testing
- 13:17Final thoughts and Q&A
related talks
31mAutomated Performance Testing With WebDriver
43mAutomated Performance Testing With WebDriver
37mAutomated Performance Testing With WebDriver
19mWorking Well: The Future of Web Testing
46mTesting frontend in 2019
25mAutomated Performance Testing With WebDriver
30mTesting Web Accessibility
40mAutomated Performance Testing In Preproduction