Europython2016, Selenium components

2016-07-22 at Europython Spain

Transcript

1. Selenium components and utils https://si.linkedin.com/in/jmakov Jernej Makovšek jernej@defact.to https://angel.co/jernej-makovsek https://github.com/jmakov https://twitter.com/jmakov
2. Problems • The front end guy replaces a component because of UX or stuff. Of course it breaks the tests... Nicer... Too complex for our users...
3. Problems • Modelling elements is not always trivial ◦ Most of the elements on SPA e.g. widgets ◦ Rich text editors and other iframe acrobatics ◦ Infinite lists ◦ Async stuff
4. And more problems... • Design decisions ◦ Get all elements upon class initialization? ◦ Get element only when needed? ◦ Do we want to measure how flaky the app is and see in what ways UX is compromised?
5. Selenium elements
6. Selenium elements
7. Selenium elements
8. Selenium elements
9. Selenium utils
10. Selenium utils
11. Where we’re going • Models for ◦ Material-UI ◦ Angular-UI ◦ etc.
12. https://speakerdeck.com/jmakov https://github.com/defactto opensource@defact.to