A Medley of Frontend and Backend Performance Testing?
summary
Argues that both frontend and backend testing matter and shows a working demo: install via go and build custom k6 binary, run real Chromium sessions with xk6-browser, collect browser metrics (FCP, FMP, p99) alongside HTTP protocol metrics, and mix scenarios—example runs 1 browser VU + 20 protocol VUs. Notes current limits: Chromium only, Playwright-like API compatibility, async handling, slo‑mo/headless flags, and that xk6‑browser is early but produces combined metrics successfully.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:31What is performance testing
- 3:56Front-end vs back-end
- 7:26xk6 browser tool
- 9:11xk6 browser basics
- 11:00Login automation demo
- 12:47Combining test types
- 14:32Conclusion
related talks
45mDistributed load testing with k6
26mTo see what others can not... You must climb the mountain, A Introduction to Load Testing
21mWorking Well, The Future of JavaScript Testing
01h 13mThe multi-year quest for the best web test in the west
57mOpen Forum on Performance Testing
21mState of Performance
19mWorking Well: The Future of Web Testing
52mTalk with the Experts