ta taking your selenium te tests for we web and mobile
play

Ta Taking your Selenium Te Tests for we web and mobile ile - PowerPoint PPT Presentation

Ta Taking your Selenium Te Tests for we web and mobile ile beyond your lo local l Fir Firefox Brows wser Michael Palotas, Francois Reynaud Element34 Solutions GmbH


  1. Ta Taking your Selenium Te Tests for we web and mobile ile beyond your lo local l Fir Firefox Brows wser Michael Palotas, Francois Reynaud Element34 Solutions GmbH ___________________________________________________________________________________________________________________________________________________

  2. Element34 Solutions GmbH “W “We co co-cr created Selenium an and in invented the Sel Seleni enium um Box” Gerbiweg 2 8853 Lachen, Switzerland http://www.element34.net We are a boutique consulting firm specialized in agile engineering practices and test automation solutions with Selenium. The company founders are key contributors and thought leaders to open source projects such as Selenium, Selendroid and ios-driver. Michael Palotas and Francois Reynaud spent more than a decade working for eBay and were instrumental in bringing software development and test Michael Palotas: michael.palotas@element34.net engineering at eBay into the agile age. Francois Reynaud: francois.reynaud@element34.net ___________________________________________________________________________________________________________________________________________________ 2

  3. AGENDA ______________________________________________________________________________________________________ • Introduction • Where is Selenium? • What is Selenium? • The problem • The solutions • The problems with the solutions ___________________________________________________________________________________________________________________________________________________ 3

  4. Test automation is… software development ___________________________________________________________________________________________________________________________________________________ 4

  5. A little history ______________________________________________________________________________________________________ Seleniumwas so named because Huggins, dissatisfiedwith testing tools on the market, was seeking a name that wouldpositionthe productas an alternative to Mercury Interactive QuickTestProfessional commercial testingsoftware. The name, Selenium, was selected because seleniummineral supplementsserve as a cure for mercury poisoning, Huggins explained. ___________________________________________________________________________________________________________________________________________________

  6. Selenium – what is it? ______________________________________________________________________________________________________ Selenium automates browsers – that’s it Selenium is a HTTP protocol describing user interactions Selenium is becoming a W3C standard: http://www.w3.org/TR/webdriver Supports most browsers Supports most programming languages ___________________________________________________________________________________________________________________________________________________ 6

  7. Selenium – where is it? ______________________________________________________________________________________________________ ___________________________________________________________________________________________________________________________________________________ 7

  8. Selenium„flavors“ ______________________________________________________________________________________________________ Selenium IDE Selenium Selenium GRID ___________________________________________________________________________________________________________________________________________________

  9. The problem ______________________________________________________________________________________________________ ___________________________________________________________________________________________________________________________________________________ 9

  10. The solution - Selenium Grid ______________________________________________________________________________________________________ TestNG Maven CI SELENIUM GRID HUB CLI ___________________________________________________________________________________________________________________________________________________ 10

  11. The problems with the solution Inhouse Cloud • Setup • Security • Operation • Price • Maintenance • Performance • Open source version is missing • Control lots of features for enterprise usage ___________________________________________________________________________________________________________________________________________________ 11

  12. Selenium Grid - inhouse or cloud? ___________________________________________________________________________________________________________________________________________________ 12

  13. Thoughts to consider ______________________________________________________________________________________________________ Inhouse or cloud? • Security • Scalability • Performance • Pricing • Reporting and monitoring • Target applications ___________________________________________________________________________________________________________________________________________________ 13

  14. Security ______________________________________________________________________________________________________ • Inhouse: secure • Cloud: potential security concerns. No-go for CH banks J . ___________________________________________________________________________________________________________________________________________________ 14

  15. Scalability ______________________________________________________________________________________________________ • Inhousesolutions scale much better • More tests != more expensive • More parallel tests != more expensive ___________________________________________________________________________________________________________________________________________________ 15

  16. Performance ______________________________________________________________________________________________________ • Widely reported performance issues with cloud providers • No control over performance with cloud solutions • Inhousesolutions should be close to the CI and the application under test ___________________________________________________________________________________________________________________________________________________ 16

  17. Price ______________________________________________________________________________________________________ • Cloud seems cheap at first BUT • Becomes very expensive when scaling • Self built in-house solutions require 1-2 very good engineers full time to operate and manage an enterprise grade Selenium Grid + the initial setup cost (6-12 person months) ___________________________________________________________________________________________________________________________________________________ 17

  18. Financials (in-house / self-built Selenium Grid) ______________________________________________________________________________________________________ - Building your own Enterprise Scale Selenium Grid: 3-6 months (1-2 “good” engineers) - Does not include features like video reporting, live view, extended logging etc.) - Operating costs: 150 – 180K / year Assumptions: - Cost for building the Selenium Grid are not included - Internal cost / hour: CHF 150 - “advanced” customer: Grid nodes don’t need to be configured seprarately - Browser: Firefox, Chrome, IE/Edge, Safari Mac - Parallel slots: 50 ___________________________________________________________________________________________________________________________________________________ 18

  19. Reporting & Monitoring ______________________________________________________________________________________________________ • Out of the box Selenium Grid does not provide any reporting & monitoring capabilities • Cloud solutions leave the reporting to the user • Inhousesolutions can be built with custom reporting tailored to the organization’s needs ___________________________________________________________________________________________________________________________________________________ 19

  20. Keeping things up to date ______________________________________________________________________________________________________ • Cloud: no problem • In-house: problem ___________________________________________________________________________________________________________________________________________________ 20

  21. Target applications ______________________________________________________________________________________________________ Web… probably Mobile … very likely ___________________________________________________________________________________________________________________________________________________ 21

  22. Summary Inhouse Cloud • Fast • Easy access • Secure • Security concerns • Scalable • Does not scale well • Full control • No control • Management + maintenance • Low commitment effort • $$$$$ • Big commitment • $$$$$$$$$ ___________________________________________________________________________________________________________________________________________________ 22

  23. One last thing… SELENIUM BOX ___________________________________________________________________________________________________________________________________________________ 23

Recommend


More recommend