SlideShare a Scribd company logo
1 of 37
Download to read offline
Full-stack webapp testing with Selenium and Rails

• Alex Chaffee

• Brian Takita
Abstract

• Want to test your entire Web 2.0 app, from AJAX and DHTML through browser-rendered
  HTML into a live instance of your application and database? Most web testing frameworks
  have gaps in their coverage: JUnit and Test::Unit miss the client frontend; JSUnit misses the
  server backend; web testing frameworks miss some or all of the JavaScript. With Selenium
  we have a framework that can test the whole application, from browser-executed JavaScript,
  through a live application backend, then back to assertions on browser-rendered DOM code.
  Selenium RC takes this further: since you write your tests in your application language, your
  tests can do data setup and assertions based directly on server-side domain objects that
  may be inaccessible or only partially accessible from the client side. On our teams we have
  used and developed a series of helper methods and assertions that allow testing of AJAX
  and DHTML functions as well.

  In this tutorial we outline the architecture of Selenium RC and walk through code and
  examples illustrating how to do full-stack testing against a Ruby on Rails application.
Selenium Features

• Selenium runs in the browser

• Executes your app in a frame

• Simulates user actions via JavaScript

• Goes all the way to the server and back

• Complementary to JSUnit

   • JSUnit tests JS pages only, not interaction with server

• Fun to watch
First Example

• Basic example (login_test.rb)

   •   def test_login
          open "/"
          assert_text_present("Please sign in")

         type "username", "jdoe"
         type "password", "password"
         click "submit"
         assert_text_present("Welcome, John Doe")

         open "/"
         assert_text_present("Welcome, John Doe")
       end

• Sort of a DSL ("Selenese")

• Written in Ruby

   • Can also use Java, .NET, Python, Perl, etc.
Accessing Your World

• Can access database and/or domain objects

  • def test_signup
      open "/signup"
      assert_text_present("Please sign up")
      type "username", "noob"
      type "fullname", "New Bie"
      type "password", "secret"
      type "password_verify", "secret"
      click "submit"
      assert_text_present("Welcome, New Bie")

      user = User.find_by_username("noob")
      assert user.authenticate("secret")
    end
Or even email!

 • def test_signup_via_email
     open "/signup"
     assert_text_present("Please sign up")
     type "email", "noob@example.com"
     click "submit"
     assert_text_present("An email has been sent to noob@example.com")
     wait_for { !ActionMailer::Base.deliveries.empty? }
     user = User.find_by_email("noob@example.com”)
     assert !user.verified?
     link = extract_link(ActionMailer::Base.deliveries[0].body)
     open link
     wait_for do
       user.reload
       user.verified?
     end
   end

   def extract_link(s)
    /http://S*/.match(s)[0]
   end
Or even email!

 • def test_signup_via_email
     open "/signup"
     assert_text_present("Please sign up")
     type "email", "noob@example.com"
     click "submit"
     assert_text_present("An email has been sent to noob@example.com")
     wait_for { !ActionMailer::Base.deliveries.empty? }
     user = User.find_by_email("noob@example.com”)
     assert !user.verified?
     link = extract_link(ActionMailer::Base.deliveries[0].body)
     open link
     wait_for do
       user.reload
       user.verified?
     end
   end

   def extract_link(s)
    /http://S*/.match(s)[0]
   end
Or even email!

 • def test_signup_via_email
     open "/signup"
     assert_text_present("Please sign up")
     type "email", "noob@example.com"
     click "submit"
     assert_text_present("An email has been sent to noob@example.com")
     wait_for { !ActionMailer::Base.deliveries.empty? }
     user = User.find_by_email("noob@example.com”)
     assert !user.verified?
     link = extract_link(ActionMailer::Base.deliveries[0].body)
     open link
     wait_for do
       user.reload
       user.verified?
     end
   end

   def extract_link(s)
    /http://S*/.match(s)[0]
   end
Or even email!

 • def test_signup_via_email
     open "/signup"
     assert_text_present("Please sign up")
     type "email", "noob@example.com"
     click "submit"
     assert_text_present("An email has been sent to noob@example.com")
     wait_for { !ActionMailer::Base.deliveries.empty? }
     user = User.find_by_email("noob@example.com”)
     assert !user.verified?
     link = extract_link(ActionMailer::Base.deliveries[0].body)
     open link
     wait_for do
       user.reload
       user.verified?
     end
   end

   def extract_link(s)
    /http://S*/.match(s)[0]
   end
Or even email!

 • def test_signup_via_email
     open "/signup"
     assert_text_present("Please sign up")
     type "email", "noob@example.com"
     click "submit"
     assert_text_present("An email has been sent to noob@example.com")
     wait_for { !ActionMailer::Base.deliveries.empty? }
     user = User.find_by_email("noob@example.com”)
     assert !user.verified?
     link = extract_link(ActionMailer::Base.deliveries[0].body)
     open link
     wait_for do
       user.reload
       user.verified?
     end
   end

   def extract_link(s)
    /http://S*/.match(s)[0]
   end
And don’t forget to extract a DSL

    def login(user_name,password)
      open('/login')
      type "id=login", user_name
      type "id=password", password
      click_and_wait "commit"
    end

    def logout
      open('/logout')
    end
Selenium RC Architecture: launch

       rake selenium:test                 rake selenium:server




               Launch                           Launch


        Selenium Test Suite                  Selenium Server                         Browser
                                Launch
                                Browser
                                                                 Launch
                                                                 Browser



                                                                                     DOM/JS

          Webrick running app
           (in "test" mode)




    Database
                                                                 Remote (possibly)
Selenium RC Architecture: run test

        rake selenium:test                         rake selenium:server




                Launch                                   Launch


         Selenium Test Suite                          Selenium Server                         Browser


    def test_foo
                                   click
     click "submit"
                                 'submit'
    end                                                    Selenese
                                                          Interpreter       click
                                                                          'submit'
                                                                                              DOM/JS
                                                                             HTTP
           Webrick running app
                                            HTTP            Proxy
            (in "test" mode)




     Database

                                                                          Remote (possibly)
Multiple Platform Support

• OS (Unix, Windows, Mac)

• Browser (IE, Firefox, Safari)

• The Selenium Farm (Continuous Integration)
Good Things Come To Those Who Wait

• Web 2.0 is Asynchronous and Dynamic

  • The “A” in "AJAX"

  • The "D" in "DHTML"

• The problem:

  • Since they happen unpredicatably, and inside the context of a single page,
    they’re harder to test
Good Things Come To Those Who Wait

• wait_for function

   • executes in Ruby

• wait_for_condition action

   • takes a JavaScript expression, evals it in browser

• wait_for_condition is complementary to wait_for

   • JavaScript can't poll DB or domain objects

   • Write your conditions in the language you prefer
More examples

• Tracker

  • project_page_editing_test



• Peer2Patent

  • create_prior_art_test

  • registration_mode_test
What kind of tests?

• Integration Tests

   • Test multiple layers of your app working together

• Acceptance Tests

   • Test specific customer features and/or scenarios

• UI tests

   • Test complicated or detailed UI widgets

• Smoke Tests

   • Special case of Integration Tests

   • Make sure your app doesn’t blow up
Wait, do you mean Integration Tests or
Integration Tests?

• Selenium tests are integration tests in the abstract

• Not derived from Rails Integration Tests

• Rails ITs are faster

• Selenium tests are better for testing AJAX, DHTML, widgets, full-stack
  integration



• Where you can do a test in Ruby instead of Selenium... you should.
When to use Selenium?

• Test full stack

• Test JS->server interaction

• Test emails

• Smoke testing

• Testing in multiple browsers
Particular Strengths of Selenium Tests

• AJAX/RJS tests

  • Test what state the browser is in after the RJS/AJAX call

• JS tests

  • Test JavaScript interacting with your DOM

  • Not just functional/behavioral JS (which JSUnit is great for)
When not to use Selenium?

• For every edge case

   • Want to test happy path, and one or two error paths

• When speed is of the essence

   • e.g. in a suite you run a lot, or when your tests start taking more than a few minutes

   • see next slide...

• When you’re testing fine-grained features

   • Selenium tests tend to sprawl out

      • setup/teardown are more expensive, so you want to test more things per test

   • Unit tests should be small and isolated
Slow-lenium

• Selenium is much faster than a human, but still much slower than unit tests.
  How do we deal with that?

• Fast Suite / Slow Suite

   • Run Fast suite before checkin

   • Run Slow suite in Continuous Integration

• When appropriate, convert Selenium tests into unit tests

   • Consider bootstrapping with Selenium tests, then replacing them with
     isolated tests once your app is up and running
Locators

• Specify how to locate an HTML element

  • id

     • "id" attribute

     • e.g. id=userName

  • name

     • "name" attribute

     • followed by optional "value" or "index" filter

     • e.g. name=flavor value=chocolate
Locators (cont.)

• identifier

   • first id, then name

• dom

   • JavaScript expression

   • e.g. dom=document.forms['icecreamForm'].flavorDropdown

• xpath

   • e.g. xpath=//a[contains(@href,'#id1')]/@class
Locators (cont.)

• link

   • selects the <A>` element whose Text content matches the given text

   • e.g. link=Click Here To Continue

• css

   • css selector

   • e.g. css=a[href="#id3"]

• Custom Locators

• By default, it's "identifier",

   • or "xpath" if it starts with "//"

   • or "dom" if it starts with "document."
Tips

• use ids when possible

  • XPath makes your tests brittle and dependent on page structure

• use slow mode for debugging

• user_extensions.js
Gotchas

• Disable Transactional Fixtures for Selenium tests

• Reload all fixtures before every test

   • consistent state

   • order-independent

• set allow_concurrency=true

• cookies stay between tests

   • can lead to tests passing when run alone, failing when run together

   • you can eval JS to clear cookies between tests

• Firefox profiles
Test-driving from Selenium

• Some people like it, some don't

• Pro:

   • Top-down

   • When test passes, feature is done

   • Stay close to well-defined customer requirements

• Con:

   • Still vulnerable to edge cases

   • Brittle in the face of UI changes

• You usually iterate through all layers of tests, several times over
Pivotal rake integration

• launches server locally

• runs tests locally and/or remotely
Pivotal Ruby Classes

• selenium_suite.rb

• selenium_helper.rb
Selenium On Rails

• Generates HTML (FIT-style)

• Can't go into your DB or domain

• Any custom test code has to be JavaScript

• Does it work remotely?
Q&A
Experimentation
References

• www.openqa.org—selenium-rc <http://www.openqa.org/selenium-rc/>
Timeline

• 90 minutes with Q&A interspersed
Full-stack webapp testing with Selenium and Rails

More Related Content

Viewers also liked

Groovy for Java Developers
Groovy for Java DevelopersGroovy for Java Developers
Groovy for Java DevelopersPeter Ledbrook
 
Building domain-specific languages with Groovy
Building domain-specific languages with GroovyBuilding domain-specific languages with Groovy
Building domain-specific languages with GroovyYaroslav Yermilov
 
Behat в PHP с использованием Behat и Mink
Behat в PHP с использованием Behat и MinkBehat в PHP с использованием Behat и Mink
Behat в PHP с использованием Behat и Minktyomo4ka
 
Behat-trick: как мы внедряли BDD на наших проектах
Behat-trick: как мы внедряли BDD на наших проектахBehat-trick: как мы внедряли BDD на наших проектах
Behat-trick: как мы внедряли BDD на наших проектахSQALab
 
Concurrency and Multithreading Demistified - Reversim Summit 2014
Concurrency and Multithreading Demistified - Reversim Summit 2014Concurrency and Multithreading Demistified - Reversim Summit 2014
Concurrency and Multithreading Demistified - Reversim Summit 2014Haim Yadid
 
Автоматизация для ленивых тестировщиков. Selenium + Python + Behave (BDD)
Автоматизация для ленивых тестировщиков. Selenium + Python + Behave (BDD)Автоматизация для ленивых тестировщиков. Selenium + Python + Behave (BDD)
Автоматизация для ленивых тестировщиков. Selenium + Python + Behave (BDD)SQALab
 
Continuous Delivery in Ruby
Continuous Delivery in RubyContinuous Delivery in Ruby
Continuous Delivery in RubyBrian Guthrie
 
Selenium 2 - PyCon 2011
Selenium 2 - PyCon 2011Selenium 2 - PyCon 2011
Selenium 2 - PyCon 2011hugs
 
Automated Web Testing With Selenium
Automated Web Testing With SeleniumAutomated Web Testing With Selenium
Automated Web Testing With SeleniumDeepak Mittal
 
What Mr. Spock would possibly say about modern unit testing: pragmatic and em...
What Mr. Spock would possibly say about modern unit testing: pragmatic and em...What Mr. Spock would possibly say about modern unit testing: pragmatic and em...
What Mr. Spock would possibly say about modern unit testing: pragmatic and em...Yaroslav Yermilov
 
Browser Automated Testing Frameworks - Nightwatch.js
Browser Automated Testing Frameworks - Nightwatch.jsBrowser Automated Testing Frameworks - Nightwatch.js
Browser Automated Testing Frameworks - Nightwatch.jsLuís Bastião Silva
 
Reactive Thinking in Java
Reactive Thinking in JavaReactive Thinking in Java
Reactive Thinking in JavaYakov Fain
 
From One to Many: Evolving VPC Design (ARC401) | AWS re:Invent 2013
From One to Many:  Evolving VPC Design (ARC401) | AWS re:Invent 2013From One to Many:  Evolving VPC Design (ARC401) | AWS re:Invent 2013
From One to Many: Evolving VPC Design (ARC401) | AWS re:Invent 2013Amazon Web Services
 
CIS13: Bootcamp: Ping Identity OAuth and OpenID Connect In Action with PingFe...
CIS13: Bootcamp: Ping Identity OAuth and OpenID Connect In Action with PingFe...CIS13: Bootcamp: Ping Identity OAuth and OpenID Connect In Action with PingFe...
CIS13: Bootcamp: Ping Identity OAuth and OpenID Connect In Action with PingFe...CloudIDSummit
 

Viewers also liked (18)

Groovy for Java Developers
Groovy for Java DevelopersGroovy for Java Developers
Groovy for Java Developers
 
Building domain-specific languages with Groovy
Building domain-specific languages with GroovyBuilding domain-specific languages with Groovy
Building domain-specific languages with Groovy
 
A Case Study of Using Selenium IDE and WebDriver_Word Doc
A Case Study of Using Selenium IDE and WebDriver_Word DocA Case Study of Using Selenium IDE and WebDriver_Word Doc
A Case Study of Using Selenium IDE and WebDriver_Word Doc
 
Behat в PHP с использованием Behat и Mink
Behat в PHP с использованием Behat и MinkBehat в PHP с использованием Behat и Mink
Behat в PHP с использованием Behat и Mink
 
Behat-trick: как мы внедряли BDD на наших проектах
Behat-trick: как мы внедряли BDD на наших проектахBehat-trick: как мы внедряли BDD на наших проектах
Behat-trick: как мы внедряли BDD на наших проектах
 
Selenium
SeleniumSelenium
Selenium
 
Concurrency and Multithreading Demistified - Reversim Summit 2014
Concurrency and Multithreading Demistified - Reversim Summit 2014Concurrency and Multithreading Demistified - Reversim Summit 2014
Concurrency and Multithreading Demistified - Reversim Summit 2014
 
Автоматизация для ленивых тестировщиков. Selenium + Python + Behave (BDD)
Автоматизация для ленивых тестировщиков. Selenium + Python + Behave (BDD)Автоматизация для ленивых тестировщиков. Selenium + Python + Behave (BDD)
Автоматизация для ленивых тестировщиков. Selenium + Python + Behave (BDD)
 
Continuous Delivery in Ruby
Continuous Delivery in RubyContinuous Delivery in Ruby
Continuous Delivery in Ruby
 
Selenium 2 - PyCon 2011
Selenium 2 - PyCon 2011Selenium 2 - PyCon 2011
Selenium 2 - PyCon 2011
 
Automated Web Testing With Selenium
Automated Web Testing With SeleniumAutomated Web Testing With Selenium
Automated Web Testing With Selenium
 
What Mr. Spock would possibly say about modern unit testing: pragmatic and em...
What Mr. Spock would possibly say about modern unit testing: pragmatic and em...What Mr. Spock would possibly say about modern unit testing: pragmatic and em...
What Mr. Spock would possibly say about modern unit testing: pragmatic and em...
 
Browser Automated Testing Frameworks - Nightwatch.js
Browser Automated Testing Frameworks - Nightwatch.jsBrowser Automated Testing Frameworks - Nightwatch.js
Browser Automated Testing Frameworks - Nightwatch.js
 
Reactive Thinking in Java
Reactive Thinking in JavaReactive Thinking in Java
Reactive Thinking in Java
 
From One to Many: Evolving VPC Design (ARC401) | AWS re:Invent 2013
From One to Many:  Evolving VPC Design (ARC401) | AWS re:Invent 2013From One to Many:  Evolving VPC Design (ARC401) | AWS re:Invent 2013
From One to Many: Evolving VPC Design (ARC401) | AWS re:Invent 2013
 
XPATH
XPATHXPATH
XPATH
 
CIS13: Bootcamp: Ping Identity OAuth and OpenID Connect In Action with PingFe...
CIS13: Bootcamp: Ping Identity OAuth and OpenID Connect In Action with PingFe...CIS13: Bootcamp: Ping Identity OAuth and OpenID Connect In Action with PingFe...
CIS13: Bootcamp: Ping Identity OAuth and OpenID Connect In Action with PingFe...
 
Jmeter
JmeterJmeter
Jmeter
 

Recently uploaded

UiPath Studio Web workshop series - Day 1
UiPath Studio Web workshop series  - Day 1UiPath Studio Web workshop series  - Day 1
UiPath Studio Web workshop series - Day 1DianaGray10
 
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptxEmil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptxNeo4j
 
Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...DianaGray10
 
20140402 - Smart house demo kit
20140402 - Smart house demo kit20140402 - Smart house demo kit
20140402 - Smart house demo kitJamie (Taka) Wang
 
March Patch Tuesday
March Patch TuesdayMarch Patch Tuesday
March Patch TuesdayIvanti
 
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveKeep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveIES VE
 
Novo Nordisk's journey in developing an open-source application on Neo4j
Novo Nordisk's journey in developing an open-source application on Neo4jNovo Nordisk's journey in developing an open-source application on Neo4j
Novo Nordisk's journey in developing an open-source application on Neo4jNeo4j
 
2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdfThe Good Food Institute
 
Extra-120324-Visite-Entreprise-icare.pdf
Extra-120324-Visite-Entreprise-icare.pdfExtra-120324-Visite-Entreprise-icare.pdf
Extra-120324-Visite-Entreprise-icare.pdfInfopole1
 
SIM INFORMATION SYSTEM: REVOLUTIONIZING DATA MANAGEMENT
SIM INFORMATION SYSTEM: REVOLUTIONIZING DATA MANAGEMENTSIM INFORMATION SYSTEM: REVOLUTIONIZING DATA MANAGEMENT
SIM INFORMATION SYSTEM: REVOLUTIONIZING DATA MANAGEMENTxtailishbaloch
 
Scenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosScenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosErol GIRAUDY
 
Automation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsAutomation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsDianaGray10
 
.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptxHansamali Gamage
 
Technical SEO for Improved Accessibility WTS FEST
Technical SEO for Improved Accessibility  WTS FESTTechnical SEO for Improved Accessibility  WTS FEST
Technical SEO for Improved Accessibility WTS FESTBillieHyde
 
From the origin to the future of Open Source model and business
From the origin to the future of  Open Source model and businessFrom the origin to the future of  Open Source model and business
From the origin to the future of Open Source model and businessFrancesco Corti
 
The New Cloud World Order Is FinOps (Slideshow)
The New Cloud World Order Is FinOps (Slideshow)The New Cloud World Order Is FinOps (Slideshow)
The New Cloud World Order Is FinOps (Slideshow)codyslingerland1
 
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxGraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxNeo4j
 
Oracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxOracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxSatishbabu Gunukula
 
AI Workshops at Computers In Libraries 2024
AI Workshops at Computers In Libraries 2024AI Workshops at Computers In Libraries 2024
AI Workshops at Computers In Libraries 2024Brian Pichman
 

Recently uploaded (20)

UiPath Studio Web workshop series - Day 1
UiPath Studio Web workshop series  - Day 1UiPath Studio Web workshop series  - Day 1
UiPath Studio Web workshop series - Day 1
 
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptxEmil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
 
Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...
 
20140402 - Smart house demo kit
20140402 - Smart house demo kit20140402 - Smart house demo kit
20140402 - Smart house demo kit
 
SheDev 2024
SheDev 2024SheDev 2024
SheDev 2024
 
March Patch Tuesday
March Patch TuesdayMarch Patch Tuesday
March Patch Tuesday
 
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveKeep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
 
Novo Nordisk's journey in developing an open-source application on Neo4j
Novo Nordisk's journey in developing an open-source application on Neo4jNovo Nordisk's journey in developing an open-source application on Neo4j
Novo Nordisk's journey in developing an open-source application on Neo4j
 
2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf
 
Extra-120324-Visite-Entreprise-icare.pdf
Extra-120324-Visite-Entreprise-icare.pdfExtra-120324-Visite-Entreprise-icare.pdf
Extra-120324-Visite-Entreprise-icare.pdf
 
SIM INFORMATION SYSTEM: REVOLUTIONIZING DATA MANAGEMENT
SIM INFORMATION SYSTEM: REVOLUTIONIZING DATA MANAGEMENTSIM INFORMATION SYSTEM: REVOLUTIONIZING DATA MANAGEMENT
SIM INFORMATION SYSTEM: REVOLUTIONIZING DATA MANAGEMENT
 
Scenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosScenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenarios
 
Automation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projectsAutomation Ops Series: Session 2 - Governance for UiPath projects
Automation Ops Series: Session 2 - Governance for UiPath projects
 
.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx
 
Technical SEO for Improved Accessibility WTS FEST
Technical SEO for Improved Accessibility  WTS FESTTechnical SEO for Improved Accessibility  WTS FEST
Technical SEO for Improved Accessibility WTS FEST
 
From the origin to the future of Open Source model and business
From the origin to the future of  Open Source model and businessFrom the origin to the future of  Open Source model and business
From the origin to the future of Open Source model and business
 
The New Cloud World Order Is FinOps (Slideshow)
The New Cloud World Order Is FinOps (Slideshow)The New Cloud World Order Is FinOps (Slideshow)
The New Cloud World Order Is FinOps (Slideshow)
 
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxGraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
 
Oracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxOracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptx
 
AI Workshops at Computers In Libraries 2024
AI Workshops at Computers In Libraries 2024AI Workshops at Computers In Libraries 2024
AI Workshops at Computers In Libraries 2024
 

Full-stack webapp testing with Selenium and Rails

  • 1. Full-stack webapp testing with Selenium and Rails • Alex Chaffee • Brian Takita
  • 2. Abstract • Want to test your entire Web 2.0 app, from AJAX and DHTML through browser-rendered HTML into a live instance of your application and database? Most web testing frameworks have gaps in their coverage: JUnit and Test::Unit miss the client frontend; JSUnit misses the server backend; web testing frameworks miss some or all of the JavaScript. With Selenium we have a framework that can test the whole application, from browser-executed JavaScript, through a live application backend, then back to assertions on browser-rendered DOM code. Selenium RC takes this further: since you write your tests in your application language, your tests can do data setup and assertions based directly on server-side domain objects that may be inaccessible or only partially accessible from the client side. On our teams we have used and developed a series of helper methods and assertions that allow testing of AJAX and DHTML functions as well. In this tutorial we outline the architecture of Selenium RC and walk through code and examples illustrating how to do full-stack testing against a Ruby on Rails application.
  • 3. Selenium Features • Selenium runs in the browser • Executes your app in a frame • Simulates user actions via JavaScript • Goes all the way to the server and back • Complementary to JSUnit • JSUnit tests JS pages only, not interaction with server • Fun to watch
  • 4. First Example • Basic example (login_test.rb) • def test_login open "/" assert_text_present("Please sign in") type "username", "jdoe" type "password", "password" click "submit" assert_text_present("Welcome, John Doe") open "/" assert_text_present("Welcome, John Doe") end • Sort of a DSL ("Selenese") • Written in Ruby • Can also use Java, .NET, Python, Perl, etc.
  • 5. Accessing Your World • Can access database and/or domain objects • def test_signup open "/signup" assert_text_present("Please sign up") type "username", "noob" type "fullname", "New Bie" type "password", "secret" type "password_verify", "secret" click "submit" assert_text_present("Welcome, New Bie") user = User.find_by_username("noob") assert user.authenticate("secret") end
  • 6. Or even email! • def test_signup_via_email open "/signup" assert_text_present("Please sign up") type "email", "noob@example.com" click "submit" assert_text_present("An email has been sent to noob@example.com") wait_for { !ActionMailer::Base.deliveries.empty? } user = User.find_by_email("noob@example.com”) assert !user.verified? link = extract_link(ActionMailer::Base.deliveries[0].body) open link wait_for do user.reload user.verified? end end def extract_link(s) /http://S*/.match(s)[0] end
  • 7. Or even email! • def test_signup_via_email open "/signup" assert_text_present("Please sign up") type "email", "noob@example.com" click "submit" assert_text_present("An email has been sent to noob@example.com") wait_for { !ActionMailer::Base.deliveries.empty? } user = User.find_by_email("noob@example.com”) assert !user.verified? link = extract_link(ActionMailer::Base.deliveries[0].body) open link wait_for do user.reload user.verified? end end def extract_link(s) /http://S*/.match(s)[0] end
  • 8. Or even email! • def test_signup_via_email open "/signup" assert_text_present("Please sign up") type "email", "noob@example.com" click "submit" assert_text_present("An email has been sent to noob@example.com") wait_for { !ActionMailer::Base.deliveries.empty? } user = User.find_by_email("noob@example.com”) assert !user.verified? link = extract_link(ActionMailer::Base.deliveries[0].body) open link wait_for do user.reload user.verified? end end def extract_link(s) /http://S*/.match(s)[0] end
  • 9. Or even email! • def test_signup_via_email open "/signup" assert_text_present("Please sign up") type "email", "noob@example.com" click "submit" assert_text_present("An email has been sent to noob@example.com") wait_for { !ActionMailer::Base.deliveries.empty? } user = User.find_by_email("noob@example.com”) assert !user.verified? link = extract_link(ActionMailer::Base.deliveries[0].body) open link wait_for do user.reload user.verified? end end def extract_link(s) /http://S*/.match(s)[0] end
  • 10. Or even email! • def test_signup_via_email open "/signup" assert_text_present("Please sign up") type "email", "noob@example.com" click "submit" assert_text_present("An email has been sent to noob@example.com") wait_for { !ActionMailer::Base.deliveries.empty? } user = User.find_by_email("noob@example.com”) assert !user.verified? link = extract_link(ActionMailer::Base.deliveries[0].body) open link wait_for do user.reload user.verified? end end def extract_link(s) /http://S*/.match(s)[0] end
  • 11. And don’t forget to extract a DSL def login(user_name,password) open('/login') type "id=login", user_name type "id=password", password click_and_wait "commit" end def logout open('/logout') end
  • 12. Selenium RC Architecture: launch rake selenium:test rake selenium:server Launch Launch Selenium Test Suite Selenium Server Browser Launch Browser Launch Browser DOM/JS Webrick running app (in "test" mode) Database Remote (possibly)
  • 13. Selenium RC Architecture: run test rake selenium:test rake selenium:server Launch Launch Selenium Test Suite Selenium Server Browser def test_foo click click "submit" 'submit' end Selenese Interpreter click 'submit' DOM/JS HTTP Webrick running app HTTP Proxy (in "test" mode) Database Remote (possibly)
  • 14. Multiple Platform Support • OS (Unix, Windows, Mac) • Browser (IE, Firefox, Safari) • The Selenium Farm (Continuous Integration)
  • 15. Good Things Come To Those Who Wait • Web 2.0 is Asynchronous and Dynamic • The “A” in "AJAX" • The "D" in "DHTML" • The problem: • Since they happen unpredicatably, and inside the context of a single page, they’re harder to test
  • 16. Good Things Come To Those Who Wait • wait_for function • executes in Ruby • wait_for_condition action • takes a JavaScript expression, evals it in browser • wait_for_condition is complementary to wait_for • JavaScript can't poll DB or domain objects • Write your conditions in the language you prefer
  • 17. More examples • Tracker • project_page_editing_test • Peer2Patent • create_prior_art_test • registration_mode_test
  • 18. What kind of tests? • Integration Tests • Test multiple layers of your app working together • Acceptance Tests • Test specific customer features and/or scenarios • UI tests • Test complicated or detailed UI widgets • Smoke Tests • Special case of Integration Tests • Make sure your app doesn’t blow up
  • 19. Wait, do you mean Integration Tests or Integration Tests? • Selenium tests are integration tests in the abstract • Not derived from Rails Integration Tests • Rails ITs are faster • Selenium tests are better for testing AJAX, DHTML, widgets, full-stack integration • Where you can do a test in Ruby instead of Selenium... you should.
  • 20. When to use Selenium? • Test full stack • Test JS->server interaction • Test emails • Smoke testing • Testing in multiple browsers
  • 21. Particular Strengths of Selenium Tests • AJAX/RJS tests • Test what state the browser is in after the RJS/AJAX call • JS tests • Test JavaScript interacting with your DOM • Not just functional/behavioral JS (which JSUnit is great for)
  • 22. When not to use Selenium? • For every edge case • Want to test happy path, and one or two error paths • When speed is of the essence • e.g. in a suite you run a lot, or when your tests start taking more than a few minutes • see next slide... • When you’re testing fine-grained features • Selenium tests tend to sprawl out • setup/teardown are more expensive, so you want to test more things per test • Unit tests should be small and isolated
  • 23. Slow-lenium • Selenium is much faster than a human, but still much slower than unit tests. How do we deal with that? • Fast Suite / Slow Suite • Run Fast suite before checkin • Run Slow suite in Continuous Integration • When appropriate, convert Selenium tests into unit tests • Consider bootstrapping with Selenium tests, then replacing them with isolated tests once your app is up and running
  • 24. Locators • Specify how to locate an HTML element • id • "id" attribute • e.g. id=userName • name • "name" attribute • followed by optional "value" or "index" filter • e.g. name=flavor value=chocolate
  • 25. Locators (cont.) • identifier • first id, then name • dom • JavaScript expression • e.g. dom=document.forms['icecreamForm'].flavorDropdown • xpath • e.g. xpath=//a[contains(@href,'#id1')]/@class
  • 26. Locators (cont.) • link • selects the <A>` element whose Text content matches the given text • e.g. link=Click Here To Continue • css • css selector • e.g. css=a[href="#id3"] • Custom Locators • By default, it's "identifier", • or "xpath" if it starts with "//" • or "dom" if it starts with "document."
  • 27. Tips • use ids when possible • XPath makes your tests brittle and dependent on page structure • use slow mode for debugging • user_extensions.js
  • 28. Gotchas • Disable Transactional Fixtures for Selenium tests • Reload all fixtures before every test • consistent state • order-independent • set allow_concurrency=true • cookies stay between tests • can lead to tests passing when run alone, failing when run together • you can eval JS to clear cookies between tests • Firefox profiles
  • 29. Test-driving from Selenium • Some people like it, some don't • Pro: • Top-down • When test passes, feature is done • Stay close to well-defined customer requirements • Con: • Still vulnerable to edge cases • Brittle in the face of UI changes • You usually iterate through all layers of tests, several times over
  • 30. Pivotal rake integration • launches server locally • runs tests locally and/or remotely
  • 31. Pivotal Ruby Classes • selenium_suite.rb • selenium_helper.rb
  • 32. Selenium On Rails • Generates HTML (FIT-style) • Can't go into your DB or domain • Any custom test code has to be JavaScript • Does it work remotely?
  • 33. Q&A
  • 36. Timeline • 90 minutes with Q&A interspersed