Back-End Tests Not Evident but a Simple Way to Improve Your Testing
summary
Shows how teams running Selenium + Jenkins on Kubernetes (AWS) can cut cost and time by converting many UI Selenium tests into API tests using Unirest/REST with Java and JUnit. Describes a three‑module project (model, web UI tests, service/API tests) running on Firefox/Linux, keeping only a few negative UI validation checks, and reports regression runtime reduced from 14 to 4 days and overall test speedups of tens-to-hundreds×.
AI-written summary · about
chapters (8)
- 0:00Backend testing problems
- 4:43Testing pyramid issues
- 8:16UI vs service trade-offs
- 11:10UI vs API testing
- 13:00Optimizing lower-level tests
- 15:53Understanding product
- 18:41Building test coverage
- 21:36Q&A
related talks
36m3 ways not to use Selenium
38mFreeing up Selenium
53mModern Web Testing: Going Beyond Selenium
41mFunctional Tests (Selenium) in Practice
37mSelenium In the Enterprise: What went right, what went wrong (so far)
54mShould You Be Doing More API Testing?
23mAdaptive Testing
40mUI automation – it’s not free