Selenium ui paradigm - DDD North 2
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Selenium ui paradigm - DDD North 2

on

  • 1,299 views

Slide deck from the presentation at DDD North 2

Slide deck from the presentation at DDD North 2

Statistics

Views

Total Views
1,299
Views on SlideShare
1,298
Embed Views
1

Actions

Likes
0
Downloads
5
Comments
0

1 Embed 1

https://twitter.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • JavaScriptTestRunnerMost probably the first open source UI testing tool

Selenium ui paradigm - DDD North 2 Presentation Transcript

  • 1. UI Testing Paradigm SELENIUMnathangloyn@NathanGloynDesign Code Releasenathans.dropbox@gmail.com
  • 2. Agenda UI testing Why use Selenium? Selenium: Origins Selenium: IDE & Concepts Selenium: WebDriver Selenium: Advanced concepts Summary Questions
  • 3. What is UI testing? a.k.a System Testing, Functional testing Use UI to drive the system All parts of system exercised Ensure that UI behaves as expected
  • 4. Testing through the UI Pros  Ensure that system works as a whole  Easy regression testing Cons  Expensive  Time consuming
  • 5. Why use Selenium Free Open source Supports Java, Ruby, .Net, Python, PHP & Perl Portable Combine with other tools
  • 6. Origins Thoughtworks Jason Huggins Javascript Java + Http Request Simon Stewart WebDriver
  • 7. Origins: ProjectsSelenium 2.0 1.0 Web driver Selenium CoreRemote Control IDE Grid
  • 8. Selenium IDE Firefox addin Record & replay Supports plugins Creates Selenese scripts Can output unit tests in various languages
  • 9. Selenium IDEDemo
  • 10. Concepts: Assert vs Verify a.k.a hard or soft assertions Different uses Fail Assert = immediate test failure Fail verify = continue to end of test Use depends on test
  • 11. Concepts: Commands Actions  Click  keyDown Accessors  Title  Text Assertions  Assert  Verify
  • 12. Concepts: Locators id Name Tag Name Attribute based Class Name CSS Link Content based Partial link Xpath Structure based
  • 13. Concepts using Selenium IDEDemo
  • 14. Selenium IDE: Summary Easy way to get started Able to create suites of tests Very good for quick smoke tests e.g navigation Test can be exported to different languages Limited to FireFox Very data sensitive Not usable from a CI server
  • 15. Web Driver Has native browser specific drivers No server needed Object Oriented API HtmlUnit support Support for Selenium RC
  • 16. WebDriverDemo
  • 17. Brittle tests Data dependent Framework & test code combined Incorrect locators
  • 18. Data Deterministic vs Non-Deterministic Static vs Dynamic Easier vs Hard
  • 19. Brittle testsBad Code
  • 20. Page Object Pattern Popular design pattern in testing Abstracts a page Encapsulates all operations Helps prevent brittle tests Page Object does not assert or verify
  • 21. Page Object PatternDemo
  • 22. Domain Specific Language Abstraction Specification Not a “proper” DSL Readable Build it piece at a time Investment
  • 23. Domain Specific LanguageDemo
  • 24. Summary Tests the application end to end Very easy to get going with Strategies to avoid brittle tests Free Investment in tests
  • 25. Questions?