The Selenium   Cloud
me: Michael Wowro●   History: database developer, test lead at    mmw AG●   Test Automation Engineer (freelancer)●   Blog:...
terminology●   Cloud●   Selenium●   „Selenium Cloud“
advantages●   Focus on test-automation = app coverage    (not setting up and maintaining grid)●   Sophisticated reports su...
challanges●   Delay with waiting for free node (rare case)●   Delay by latency (little: compared to    browser start/drivi...
For completeness ...●   TestingBot: http://testingbot.com/ - no    mature company yet (rising star?)●   „Website Load Test...
Sauce Labs●   History: EC2●   Staff: Jason Huggins, Santiago Suarez    Ordoñez●   Based in: CA, USA●   OS/browser combos: ...
Documentation●   test = job (in Sauce vocabulary)●   overview of tests = SauceLabs HOME●   test report = job info (in Sauc...
SauceLabs HOME
Test Reporthttp://bit.ly/UZVo9b
Integration I●   RemoteWebDriver●   Named tests:    caps.setCapability("name",    Thread.currentThread().getStackTrace()  ...
Integration II●   Code: https://gist.github.com/4170183●   Test report: http://bit.ly/Yuf8q2
@manual tests●   SauceLabs supports them, too:       –   Choose the OS/browser combo on which            the customer repo...
Contract    http://saucelabs.com/pricing●   Minute-based service●   Freemium (in total 170 minutes/month free)●   minute d...
Questions?      http://icant.co.uk/talks/h5/pictures/smashingconf/okay.gif
Upcoming SlideShare
Loading in …5
×

Selenium cloud

1,408 views

Published on

State of the art about cloud-computing in the Selenium ecosystem

Published in: Technology
1 Comment
2 Likes
Statistics
Notes
  • On slide 5 about challenges and company politics. I may disagre on test data sensitivity. For an e-commerce application/website, if you test on production, sensitive data would include user logins, and credit card information, etc. Granted one might not test financial transactions with automation on live system. As for logins, they might be dummy test user accounts, but any account login could potentially be a source of network/app intrusion by a hacker should they be able to hack the account. And for testing against internal test environments usually via proxy from cloud service to internal network, it is more secure, but that is also placing trust in the SLA of the cloud testing vendor you're working with. So while not a major concern, I don't think it is exactly 'unproblematic' at all.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
1,408
On SlideShare
0
From Embeds
0
Number of Embeds
209
Actions
Shares
0
Downloads
29
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide
  • Selenium Grid in the cloud
  • Selenium cloud

    1. 1. The Selenium Cloud
    2. 2. me: Michael Wowro● History: database developer, test lead at mmw AG● Test Automation Engineer (freelancer)● Blog: IT KOSMOPOLIT ( www.it-kosmopolit.de)● Latest contribution to Selenium Project: blog list (http://bit.ly/UZVbRf)
    3. 3. terminology● Cloud● Selenium● „Selenium Cloud“
    4. 4. advantages● Focus on test-automation = app coverage (not setting up and maintaining grid)● Sophisticated reports support bugtracking● Usage fee versus fix costs● Add browser/OS combo easily
    5. 5. challanges● Delay with waiting for free node (rare case)● Delay by latency (little: compared to browser start/driving)● Company politics (for WebApps unproblematic, as test data shouldnt be sensitive)● Trust in foreign quality (THE issue about cloud computing)● Integration
    6. 6. For completeness ...● TestingBot: http://testingbot.com/ - no mature company yet (rising star?)● „Website Load Testing“ – History: BrowserMob – Neustar – Using BrowserMob Proxy (close but not in Selenium Project) – Intro for BrowserMob Proxy: http://bit.ly/V5JYPj
    7. 7. Sauce Labs● History: EC2● Staff: Jason Huggins, Santiago Suarez Ordoñez● Based in: CA, USA● OS/browser combos: 59 Windows, 19 Mac, 18 Linux (https://saucelabs.com/docs/browsers)
    8. 8. Documentation● test = job (in Sauce vocabulary)● overview of tests = SauceLabs HOME● test report = job info (in Sauce vocabulary)● test report: protokoll, screenshots, video, log
    9. 9. SauceLabs HOME
    10. 10. Test Reporthttp://bit.ly/UZVo9b
    11. 11. Integration I● RemoteWebDriver● Named tests: caps.setCapability("name", Thread.currentThread().getStackTrace() [1].getMethodName());● Behavior of testing framework (Junit, TestNG) not different from Selenium Grid● REST-API: http://saucelabs.com/docs/rest● Result integration: http://bit.ly/QP3Xq3
    12. 12. Integration II● Code: https://gist.github.com/4170183● Test report: http://bit.ly/Yuf8q2
    13. 13. @manual tests● SauceLabs supports them, too: – Choose the OS/browser combo on which the customer reported the bug. – Have video documentation of the way to the bug. – Integration with JIRA
    14. 14. Contract http://saucelabs.com/pricing● Minute-based service● Freemium (in total 170 minutes/month free)● minute differentiation – Win, Linux, Android – Mac, iOS – Manual testing● Key to performance = #parallel instances
    15. 15. Questions? http://icant.co.uk/talks/h5/pictures/smashingconf/okay.gif

    ×