QA Livecoding Battle “JDI VS Selenide”
summary
A live-coding showdown compares JDI’s typed UI elements with Selenide’s non-typed approach by implementing concrete tasks: add a three-film watchlist, sort/filter by rating and genre, verify year/type, and delete an entry. Both frameworks are exercised against a buggy web site during on-stage coding (not all code is executed), several real bugs are found, and the audience vote ends nearly tied on which yields clearer, more maintainable tests.
AI-written summary · about
chapters (9)
- 0:00Intro
- 4:00Battle rules
- 7:18Round 1: test scenario
- 16:32JDI code
- 25:16Selenide code
- 35:01Round 1 results
- 36:09Round 2: approaches
- 42:36Flexibility demo
- 47:31Final results
related talks
42mJDI 2.0 in examples, part 1
39mSelenide: Make Java UI Tests Great Again!
43mJDI 2.0 in examples, part 2
45mUI, Api and Accessibility Frameworks Live Coding: Quick Set-Up and First Tests in Java
45mSelenide & KISS-Driven-Development – UI Test Automation Made Simple
46mHow to write UI tests from A to Z, part 2
49mHow to write UI tests from A to Z, part 1
26mCodeless Visual Testing