Surviving UI Automation Armageddon with BELLATRIX
summary
Bellatrix proves to be a practical framework: C# plus Selenium-based controls, Jenkins and Azure DevOps pipelines, and a Bellatrix performance plugin enable converting and running an automation suite against a full SPA rewrite. The team extracts controls into a separate project, keeps page objects and component metadata models stable, supports both legacy and SPA renderings, and migrates roughly 2,500 pages and about 7,000 system tests. Full daily execution runs about 20 hours, defects drop and testing stays ahead of development.
AI-written summary · about
chapters (34)
- 0:00UI automation Armageddon intro
- 1:19Speaker & agenda
- 2:24Large-scale automation context
- 3:48UI test structure
- 6:40Test execution setup
- 7:03Framework & Bellatrix overview
- 9:56Selenium vs Bellatrix tests
- 15:35Pure Selenium challenges
- 15:56Bellatrix test class setup
- 17:46Element mappings & controls
- 20:58Lazy loading & waits
- 21:22Component assertions
- 22:03Framework enhancements
- 22:47Page objects intro
- 24:34Locators & fragility
- 25:17Visual form locators
- 27:25Visual locator limits
- 27:45Form metadata objects
- 30:16Generic form filling
- 31:01Tables & grids
- 31:43Tests after metadata
- 33:29Base form page
- 33:52Announcement of single page application
- 36:20SPA migration plan
- 36:41SPA refactoring
- 37:24Legacy & SPA coexistence
- 37:46Implementation & testing
- 38:28Page objects unchanged
- 39:09Models & controls adaptation
- 39:30Success metrics & defects
- 40:36Performance testing
- 41:20Demo & GitHub
- 41:42Key takeaways
- 43:05Q&A
related talks
37mTest Automation: From Zero To Hero
05mTaming the Testing Beast
53mTransforming testing methodologies: From manual to robust strategies
35mBuild an automation framework... with a developer mindset
37mFrom Rigidity to Resiliency: An Evolutionary Tale of Selenium-Based Frameworks
39mMake .Net Automation Great Again
35mScrewing up. The automated way!
23mAdaptive Testing