![Regex Step Definitions Good: Reuse Definitions Bad: Then /^(?:|I )should see "([^\"]*)"(?: within "([^\"]*)")?$/ do](https://image.slidesharecdn.com/cucumberv2-110410124837-phpapp02/85/Selenium-and-Cucumber-Selenium-Conf-2011-61-320.jpg)
Selenium and Cucumber Selenium Conf 2011
- 2. Dima Kovalenko @dimacus www.agilesoftwaretesting.com www.dimakovalenko.com linked in.com/in/dimakovalen ko
- 4. Disclaimer > Dima.kind_of?(Developer) => false
- 6. Why automated tests? Too expensive Too much work to create Not enough staff to maintain Never know the coverage level No one but developers knows what is being tested
- 7. We don’t need Automated Tests!
- 8. We don’t need Automated Tests! The End See You all at Selenium 2012!
- 10. Selenium and Cucumber Img Source: http://pickledillies.homestead.com/
- 11. Overview Set the stage Introduce Cucumber Good features Bad features ??? Profit!
- 12. Assumptions Startup or small business Understaffed Inadequate test coverage Need to defend existence of having automated tests to business.
- 13. The Stage
- 14. The Stage First casualty of an agile development environment is documentation. - me
- 15. The Stage First casualty of an agile development environment is documentation. - me No written test cases to speak of
- 16. The Stage First casualty of an agile development environment is documentation. - me No written test cases to speak of Need to deliver features, NOW!!!
- 17. The Stage First casualty of an agile development environment is documentation. - me No written test cases to speak of Need to deliver features, NOW!!! Groupon: Weekly deployments
- 18. The Stage First casualty of an agile development environment is documentation. - me No written test cases to speak of Need to deliver features, NOW!!! Groupon: Weekly deployments IMVU: Up to 50 deploys a day http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/
- 19. Why automated tests? Too expensive Too much work to create Not enough staff to maintain Never know the coverage level No one but developers knows what is being tested
- 20. Cucumber
- 21. Cucumber A BDD framework to help with TDD and other TLAs
- 22. Cucumber A BDD framework to help with TDD and other TLAs It’s Agile, Promotes Synergy, Enterprise, will shift Paradigms and completely Web 2.0
- 23. Cucumber A BDD framework to help with TDD and other TLAs It’s Agile, Promotes Synergy, Enterprise, will shift Paradigms and completely Web 2.0 You too can be BUZZ WORD compliant!
- 25. Natural Language @search Feature: Searching For Hello World, and some more overview of the feature that we are trying to test @google Scenario: User Searches for Hello World on Google.com Given I'm on Google's Home Page And I search for Hello World Then I should see Wikipedia's Hello World article as 1st result @bing Scenario: User Searches for Hello World on Bing.com Given I'm on Bing's Home Page And I search for Hello World Then I should see car videos as first result
- 26. Step Definitions Given /^I'm on Google's Home Page$/ do @selenium.open " www.google.com " end Given /^I'm on Bing's Home Page$/ do @selenium.open " www.bing.com " end When /^I search for Hello World$/ do @selenium.type "q", "Hello World" end Then /^I should see Wikipedia's Hello World article as 1st result$/ do assert_stuff end Then /^I should see car videos as first result$/ do assert_stuff end
- 27. Why automated tests? Too expensive Too much work to create Not enough staff to maintain Never know the coverage level No one but developers knows what is being tested
- 28. Who should be writing tests?
- 29. Who should be writing tests? Developers Unit, Integration, Functional
- 30. Who should be writing tests? Developers Unit, Integration, Functional QAs Functional, End-To-End
- 31. Who should be writing tests? Developers Unit, Integration, Functional QAs Functional, End-To-End Everyone else At least the feature definitions
- 32. Why automated tests? Too expensive Too much work to create Not enough staff to maintain Never know the coverage level No one but developers knows what is being tested
- 34. Why automated tests? Too expensive Too much work to create Not enough staff to maintain Never know the coverage level No one but developers knows what is being tested
- 35. Good Features Tags Encourages BDD/TDD Supports multiple test drivers Selenium 1 and Selenium 2 support Multilingual i18n support Readable test results
- 36. Tags @search Feature: Searching For Hello World, and some more overview of the feature that we are trying to test @google @selenium Scenario: User Searches for Hello World on Google.com Given I'm on Google's Home Page And I search for Hello World Then I should see Wikipedia's Hello World article as 1st result @bing Scenario: User Searches for Hello World on Bing.com Given I'm on Bing's Home Page And I search for Hello World Then I should see car videos as first result
- 37. Tags @search Feature: Searching For Hello World, and some more overview of the feature that we are trying to test @google @selenium Scenario: User Searches for Hello World on Google.com Given I'm on Google's Home Page And I search for Hello World Then I should see Wikipedia's Hello World article as 1st result @bing Scenario: User Searches for Hello World on Bing.com Given I'm on Bing's Home Page And I search for Hello World Then I should see car videos as first result
- 38. Encourages BDD/TDD Write feature description first Run test see it fail Create one step definition at the time Write functionality for the step Run test see it pass
- 39. First run
- 40. First run
- 42. Write More Step Definitions
- 43. Even More Step Definitions
- 44. Multiple Test Drivers Steam Celerity Culerity FireWatir SafariWatir ChromeWatir Img Source: Wikipedia
- 45. Selenium 1 support Before do | scenario | @selenium = Selenium::Client::Driver.new ( :host => "localhost", :port => 4444, :browser => “firefox”, :url => “ www.google.com ”) end
- 46. Selenium 1 Tip Use Hpricot Or Nokogiri!!! page = Hpricot ( @selenium .get_html_source)
- 50. Selenium 2 support Capybara + Selenium = Love
- 51. Selenium 2 support Capybara + Selenium = Love Capybara + Selenium + Rails = .......
- 52. Capybara Uses Nokogiri Uses XPath outside of browser Works outside of rails
- 53. Multilingual JVM: JRuby, Java .NET: IronRuby, IronRuby .NET, Mono Adoby Flex: FunFX, Melomel Python Erlang Groovy Scala Closure Javascript Spring
- 54. Java Step Definition package cukes; import cuke4duke.annotation.I18n.EN.Given; import java.util.List; import java.util.ArrayList; public class BellySteps { private List<String> belly = new ArrayList<String>(); @Given("I have (\\d+) cukes in my belly") public void bellyCukes(int cukes) { for(int i = 0; i < cukes; i++) { belly.add("cuke " + i); } } }
- 55. i18n
- 56. i18n Функционал: Сложение чисел Чтобы не складывать в уме Все, у кого с этим туго Хотят автоматическое сложение целых чисел Сценарий: Сложение двух целых чисел Допустим я ввожу число 50 И затем ввожу число 70 Если я нажимаю "+" То результатом должно быть число 120
- 57. i18n Chinese 功能 : 加法 為了避免愚蠢的錯誤 作為一個數學白痴 我希望有人能告訴我兩個數相加的結果 場景大綱 : 將兩個數相加 假 設我已經在計算機上輸入 < 數值 _1> 而 且我已經在計算機上輸入 < 數值 _2> 當 我按下 < 按鈕 > 那 麼螢幕上應該顯示 < 結果 >
- 58. i18n LOLz OH HAI: STUFFING MISHUN: CUCUMBR I CAN HAZ IN TEH BEGINNIN 3 CUCUMBRZ WEN I EAT 2 CUCUMBRZ DEN I HAS 2 CUCUMBERZ IN MAH BELLY AN IN TEH END 1 CUCUMBRZ KTHXBAI
- 60. Bad Features Regex step definitions Hard To find Step Definitions Slower Natural language parser Messy directory structure
- 61. Regex Step Definitions Good: Reuse Definitions Bad: Then /^(?:|I )should see "([^\"]*)"(?: within "([^\"]*)")?$/ do
- 62. Hard to find Step Definitions cucumber-tmbundle Vim Rails
- 63. Bad Features Regex step definitions Hard To find Step Definitions Slower Natural language parser Messy directory structure
- 64. Conclusion Cucumber is a great tool to Describe Features Document Features Get the whole team involved However, it has downsides also
- 65. @dhh RSpec offends me aesthetically with no discernible benefit for its added complexity over test/unit.
- 66. @dhh RSpec offends me aesthetically with no discernible benefit for its added complexity over test/unit. Cucumber makes no sense to me unless you have clients reading the tests. Why would you build a test-specific parser for English?
- 67. @dhh RSpec offends me aesthetically with no discernible benefit for its added complexity over test/unit. Cucumber makes no sense to me unless you have clients reading the tests. Why would you build a test-specific parser for English? The important thing is of course that we get people testing, so tools shouldn't matter too much....
- 68. Work @ Groupon www.groupon.com/techjobs
- 69. The End