Graceful Failure with Selenium and Continuous Integration
7 likes1,122 views
The document discusses the importance of anticipating failure in programming and how to manage it through various testing methods, including unit tests, integration tests, and acceptance tests. It highlights the use of Selenium, an automated testing tool, advocating for Behavior Driven Development (BDD) and Continuous Integration processes to effectively handle testing challenges. The author emphasizes that testing should occur both before and during development to ensure software quality.
Graceful Failure with Selenium and Continuous Integration
- 1. FAILING GRACEFULLY with Selenium and T.D.D.
- 2. FAILURE
- 3. IT’S A WAY OF LIFE
- 5. PREDICTABLE
- 6. SURPRISE
- 7. GRACEFUL
- 8. HOW TO COPE?
- 9. DENY IT
- 10. JUST BE VAGUE
- 11. GO ON THE OFFENSIVE
- 12. STALL FOR TIME
- 13. Better strategies? maybe just .... CLEARER INSTRUCTIONS!
- 16. Good, even.
- 17. Good, even. (fail) (win)
- 18. AS PROGRAMMERS we fail all the time.
- 20. The only way to fail less is to ANTICIPATE FAILURE
- 21. The only way to fail less is to ANTICIPATE FAILURE and then DON’T MAKE THE SAME MISTAKE AGAIN :)
- 22. THINGS HAPPEN.
- 23. BUT THEN ...
- 24. AND THEN ...
- 25. AND, WELL ...
- 28. HUMAN Q.A. TESTING is the ideal. (Too bad humans are so much better at other things and need to eat and sleep and stuff ... )
- 29. SELENIUM IS A tool for helping to automate testing.
- 30. ACTUALLY... There are many kinds of automated tests http://www.flickr.com/photos/60648084@N00/1360619915/
- 31. UNIT TESTS * For individual functions * The cutest test. http://www.flickr.com/photos/donsolo/2900765675/in/set-72157594163175020/
- 32. INTEGRATION TESTS * For groups of related functionality * More relevant and (almost) fun to write http://www.flickr.com/photos/donsolo/399501571/in/set-72157594163175020/
- 33. ACCEPTANCE TESTS * Highest level testing. * Basically user stories. * “Accepted” as in “get fired if they don’t work” http://www.flickr.com/photos/donsolo
- 34. don’t get confused: REGRESSION TESTING (Is part of all of these, not another style)
- 35. So, let’s back up a sec. Let me tell you a story about ... UNIT TESTING IN RUBY http://www.flickr.com/photos/21734563@N04/2198268918/
- 37. ASSERT
- 40. svn ci -m “math library passes unit tests!!”
- 41. Integration testing is super cool
- 42. You can really smell the relevance. (seriously)
- 43. HOORAY FOR USER STORIES! Strive to pass good user-centered tests. http://www.lukeredpath.co.uk/blog/developing-a-rails-model-using-bdd-and-rspec-part-1.html
- 44. B.D.D. = BEHAVIOR DRIVEN DEVELOPMENT in rspec
- 45. (which uh, actually runs)
- 46. WAIT: IT’S IMPORTANT HOW YOU DO IT!!
- 49. RIGHT. SO, ANYWAY ... BACK TO THIS SELENIUM THING
- 51. WEIRD
- 52. why: It’s a Firefox plugin for testing. Turns your actions into test code. Let’s you edit test code in the browser. Let’s you export to lots of languages.
- 53. FUN
- 54. why: It’s a Firefox plugin for testing. Turns your actions into test code. Let’s you edit test code in the browser. Let’s you export to lots of languages.
- 55. POWERFUL
- 56. why: It’s a Firefox plugin for testing. Turns your actions into test code. Let’s you edit test code in the browser. Let’s you export to lots of languages.
- 57. FIRE-FOXY AND SIMPLE Start here: http://seleniumhq.org/
- 59. no forget about that LETS JUST WRITE A TEST ALREADY!
- 60. Now: Record and Playback • Intelligent field selection will use IDs, names, or XPath as needed • Autocomplete for all common Selenium commands • Walk through tests • Debug and set breakpoints • Save tests as HTML, Ruby scripts, or any other format Totally takes 5 seconds, man
- 62. GO RED
- 64. THEN GO GREEN
- 65. SPEAK SELENESE open opens a page using a URL. click/clickAndWait performs a click operation, and optionally waits for a new page to load. verifyTitle/assertTitle verifies an expected page title. verifyTextPresent verifies expected text is somewhere on the page.
- 66. VERIFY PAGE ELEMENTS is ... 1. an element is present somewhere on the page? 2. specific text is somewhere on the page? 3. specific text is at a specific location on the page?
- 67. GOTCHAS • clickAndWait is usually required • type usually requires you to click somewhere else first • it’s slow • brittle if the UI is changing rapidly
- 68. HARD PART’S JUST FINDING IT Good thing you have so many options ... • find elements by name • find them by id if they have it • or with CSS selectors if you understand the cascade • Xpath is like a buzzsaw (a little more expensive) • link text as a last resort (since it changes often)
- 69. Now, SELENIUM IDE is not the same as SELENIUM RC
- 70. IDE and RC play great together!
- 71. RC Remote Control, that is. • Runtests in multiple browsers. • Runthem remotely (on a dedicated server) • Runthem whenever you check in code!
- 72. exported test to c#
- 73. exported test in java
- 74. exported test to ruby
- 75. Selenium-RC leverages the full power of programming languages, creating tests that can do things like • read and write external files, • make queries to a database, • send emails with test reports • practically anything else a user can do with a normal application ...
- 76. RC can where IDE can’t • condition statements • iteration • logging and reporting of test results • error handling, particularly unexpected errors • database testing • test case grouping • re-execution of failed tests • test case dependency • capture screenshots on test failures
- 77. WAIT, WHAT ABOUT TEST- DRIVEN DEVELOPMENT? If you click around the app to build a test, that can’t be testing before development.
- 78. RIGHT. You actually should write them beforehand, by hand, just like you would unit tests. It’s not so scary. • NUnit for C# • Junit for Java • Selenium gem for Ruby
- 79. PUT IT ALL TOGETHER
- 80. Put it on your SVN server trigger it with SVN hooks
- 81. Continuous Integration with Selenium and Criuse Control
- 82. WHAT IT MEANS • Run your unit tests first locally (because they’re fast). • Checking in your changes triggers the continuous integration server running your Selenium tests (slow because they are in the browser). • Cruise Control gives you a web-based heads up when you fail or pass tests. • Joy.
- 83. THANKS! :) Chris Blow http://unthinkingly.com User Experience @ Meedan.net