Taming Dinosaur Frameworks Using NSelene
summary
NSelene adapts Selenide-style tools (a .NET port of Selenide) to work alongside legacy, home-grown test frameworks so existing tests don’t need to be rewritten. The talk explains practical integration patterns to wrap or interoperate with old unstable frameworks, allowing new tests to use a concise, stable Selenide-like API while keeping the original test suite intact.
AI-written summary · about
chapters (22)
- 0:00NSelene introduction
- 1:45Legacy Selenium issues
- 3:31Existing framework demo
- 5:17Code structure analysis
- 9:10Selenium drawbacks
- 9:51NSelene integration
- 12:04Implicit waits with NSelene
- 13:07Writing new NSelene test
- 16:26Readable test rules
- 17:50KISS optimization
- 19:17Reusing elements in NSelene
- 20:19NSelene vs Selenium benefits
- 22:57Fixing flaky tests
- 23:39Legacy code migration
- 27:00Avoiding OOP in tests
- 28:26Automatic driver usage
- 31:02Procedural approach
- 31:46Page Module with NSelene
- 33:11Java example with Selenide
- 36:48How NSelene works
- 38:35NSelene Selenium compatibility
- 39:17Informative error messages
related talks
47mSelenide101 – Getting up and running with real web tests (Alexei Vinogradov, Germany), part 2
45mSelenide & KISS-Driven-Development – UI Test Automation Made Simple
43mSelenide for Pros
37mFrom Rigidity to Resiliency: An Evolutionary Tale of Selenium-Based Frameworks
01h 01mBOF: Glorious Past and Promising Future of Selenide
40mExtending open-source libraries on the example of Selenide & Selenium
56mThreesome: Selenide for Web, Android and iOS
44mSelenoid: Ditch Selenium Server! Part 2
