Selenium Security Scanner
summary
Salesforce describes a dual approach: push JavaScript unit tests with xUnit.js running different engines so thousands of tests execute under 10 milliseconds each, reducing heavy Selenium load, and reuse Selenium runs to drive a recording proxy that saves every HTTP request so a scanner replays and fuzzes inputs. At scale (about 1,000 engineers, ~2,000 pages) this halves manual coverage gaps but doubles Selenium runtime during active scans and needs proxy licensing.
AI-written summary · about
chapters (6)
- 0:00Intro
- 2:02JavaScript Unit Tests
- 5:44JavaScript Mocking
- 12:10Common Vulnerabilities
- 14:36How it Works
- 16:15Challenges
related talks
37mSelenium In the Enterprise: What went right, what went wrong (so far)
34mUsing Selenium to Improve a Team's Development Cycle
42mTesting Salesforce at Cloud Scale
36m3 ways not to use Selenium
40mScaling Selenium to infinity using AWS Lambda
38mFreeing up Selenium
01h 14mContinuous Testing
05mTaming the Testing Beast