Running Automation tests twice as faster
summary
Describes replacing a Selenium Grid-based CI/node architecture for a large healthcare web app to eliminate grid and reduce network latency, aiming to double test execution speed. Explains how automation runs were restructured and integrated into enterprise constraints to run large numbers of browser test suites faster without changing overall architecture.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:43About me
- 2:32Outline
- 3:40Current Practices
- 6:43LifeCycle: MsBuild
- 8:06LifeCycle: NUnit Runner And Parser
- 10:38NUnit Parser
- 10:52Problems with Our Practice
- 12:07Advantages of Selenium Grid
- 13:54Problems with Selenium Grid
- 16:52Architectural Constraint
- 18:37Proposed Alternative
- 22:12Advantage Over SG
related talks
17mParallel Execution of Auto-Tests with Selenium Grid
09mTest Time Execution! Why it Can't be Ignored?
23mAdaptive Testing
05mTaming the Testing Beast
21mScaling Test Automation: Building Reusability for 10x Speed and Efficiency
53mTransforming testing methodologies: From manual to robust strategies
35mElevate your testing: testing smarter, not harder, in the cloud!
40mSelenium Grid
