Selenium automates browsers and allows running tests on different machines against different browsers in parallel. Selenium Hub (also called Selenium Grid) manages this by allowing tests to run on various Selenium WebDrivers including Chrome and Firefox. The document demonstrates running simple tests using Selenium Hub, and discusses enhancing tests by integrating with Angular, Protractor, and Karma to test an actual application. Next steps include upgrading dependencies, focusing on acceptance tests, innovating tests, and keeping tests simple.

1. Selenium
Doron Segal • 03.03.2016

2. whatisSeleinum
What?
Selenium automates browsers.
Selenium Hub
Selenium-Grid (Also called Selenium-Hub) allows
you run tests on different machines against
different browser in parallel.
Selenium web driver
Selenium WebDriver is the machine thats going to
run the test for example Chrome-WebDriver,
Firefox and etc...

3. Let’sstart...
So,
● Let’s think about the components (we have 3 here)
○ Your tests (in our case Javascript tests)
○ Selenium Hub (Running in mesos)
○ Selenium WebDriver firefox and chrome

4. seleniumgridarchitecturediagram(General)

5. seleniumgridarchitecturediagram(OpenTable)
Doron’s
Mac
Selenium
Grid
Selenium WebDriver
Selenium WebDriver
Selenium WebDriver

6. Links
● Selenium Hub:
○ Github: https://github.com/opentable/Selenium-Hub
○ TeamCity Build: http://teamcity.otenv.com/project.html?projectId=Umami_SeleniumHub
○ Mesos Instance: http://selenium-hub.pp-uswest2.otenv.com/grid/console
● Selenium WebDriver
○ Chrome
■ TeamCity: http://teamcity.otenv.com/project.html?projectId=Umami_SeleniumHub_SeleniumNodeChrome
■ Github: https://github.com/opentable/Selenium-Node-Chrome
○ FireFox
■ TeamCity: http://teamcity.otenv.com/project.html?projectId=Umami_SeleniumHub_SeleniumFirefoxNode
■ Github: https://github.com/opentable/Selenium-Node-FireFox

7. Questions?
About
● HowSeleniumGrid/Hubisworking?
● How’sthenodegetthetests?
● howit’srun?
● etc..
Greatlet’scontinue...

8. DemoTime
Part1

9. FirstDemo
● Github:https://github.com/doron2402/webdriver.git
● FirstTest-wiki.js
○ scenario:gotohttp://en.wikipedia.org/wiki/Wiki andfindhowmanylinkswehaveinsidethepage
○ WewillbeusingtheHub:http://selenium-hub.pp-uswest2.otenv.com/wd/hub
○ Wewillberunningtwoinstances`Chrome`and`Firefox`
● SecondTest
○ Scenario:Googlemynamefindmypersonalwebsiteclickonthelinkandgetthetitle
○ WewillbeusingtheHub:http://selenium-hub.pp-uswest2.otenv.com/wd/hub
○ Wewillberunningtwoinstances and`Firefox`
Let’srunit`nodewiki.js`&`nodegoogleSearch.js`

10. ...
varbrowser=newwebdriver.Builder()
.usingServer('http://selenium-hub.pp-uswest2.otenv.com/wd/hub')
.withCapabilities({'browserName':'chrome'})
.build();
browser.get('http://en.wikipedia.org/wiki/Wiki');
browser.findElements(webdriver.By.css('[href^="/wiki/"]')).then(function(links){
console.log('Browser1:Found',links.length,'Wikilinks.')
browser.quit();
});
........
FirstDemo(wiki)

11. ...
varwebdriver=require('selenium-webdriver');
varbrowser=newwebdriver.Builder()
.usingServer('http://selenium-hub.pp-uswest2.otenv.com/wd/hub')
.withCapabilities({'browserName':'firefox'})
.build();
browser.get('https://www.google.com');
browser.findElement(webdriver.By.name('q')).sendKeys('doronsegal');
browser.findElement(webdriver.By.name('btnG')).click();
browser.wait(findTutsPlusLink,2000).then(clickLink).then(logTitle).then(closeBrowser,handleFailure);
........
FirstDemo(Google)

12. DemoTime
part2

13. Let’skickitupanotch
● AngularApp
● Protractor
● Karama
● Github:https://github.com/opentable/angular-tests.git
● `npmstart`toruntheproject(wewillneedtoupdatemyipaddressfortheseleniumnodetoaccessmylocalcomputer)
● `npmrunprotractor`toexecutethetest(weneedtopassmyipaddress)
● Let’saddatest...

14. Code
Write test on
your local
computer
Run
Run tests
against the Hub
Merge
Merge your code
to Master
Test
Run test from
TeamCity
Deploy
When all tests
passed we can
deploy to prod

15. Nextsteps
Upgrade
We should upgrade our protractor version to the latest
Approach
We should always think about acceptance/E2E tests, It’s part of deploying
feature.
Innovate
Tests should always be innovate.
KISS
Tests should be simple to write & run.

16. Thanks
&
QA
1. Links - you can find in
the slideshow
2. I’ll give everyone
access to the slideshow
3. Hope you’ll enjoy