Testing Web Pages and Mobile Applications With Locust.io
summary
Claims Locust wins over JMeter when tests need Python debugging, data generation and post‑run analysis; actual setup uses HAR-to-Python transformer plus requests, lxml and cssselect libraries; recorded a UI scenario that presses B2 three times, converts response to JSON and asserts the result contains a "trail" : "good answer"; mobile recording uses mitmproxy/fiddler proxy setup to produce HARs; load run ramps from 10 to 100 users with live charts, downloadable HTML reports, and recorded cases that reproduce and debug failures.
AI-written summary · about
chapters (14)
- 0:00Locust.io introduction
- 1:07Locust vs JMeter
- 3:43Locust in test automation
- 5:17Web vs API testing
- 8:09Python skills impact
- 9:12Recording scripts with HAR
- 12:10HAR to Python code
- 17:24HAR conversion tools
- 20:01Editing generated code
- 23:17Debugging Locust scripts
- 25:54Main test file setup
- 26:38Running tests in web UI
- 29:50Analyzing results
- 31:17Mobile app testing
related talks
26mLoad testing websites following the steps of a user journey
45mBeat the rush! Designing effective load tests for your web application
43mRelease the locusts - distributed performance tests
30mBeat the rush! Designing effective load tests for your web application
29mAzure Load Testing in action
37mAutomated Performance Testing With WebDriver
41mLeverage Your Load Tests With JMeter And Selenium Grid
33mRun the load down your mobile app