![Introduction Lukáš Fryč [Luka:ʃ Frɪdʒ]](https://image.slidesharecdn.com/testing-jsf-applications-110920035747-phpapp02/75/Testing-JSF-with-Arquillian-and-Selenium-2-2048.jpg)
Uploaded byLukáš Fryč
Testing JSF with Arquillian and Selenium
Lukáš Fryč discusses the challenges of testing JavaServer Faces (JSF) applications and introduces Arquillian as a solution that simplifies testing by managing the test lifecycle and allowing in-container testing. The document outlines various testing tools and frameworks, including JSFUnit and Ajocado, that enhance testing capabilities for JSF and RichFaces components. It emphasizes the effectiveness of these testing methods in achieving reliable and efficient functional testing.
More Related Content
Similar to Testing JSF with Arquillian and Selenium
Testing JSF with Arquillian and Selenium
- 1. JSF & RichFacesConference UNIQA Testing JSF with Arquillian & Selenium by Lukáš Fryč 9.9.2011
- 2. Introduction Lukáš Fryč[Luka:ʃ Frɪdʒ]
- 3. @lfryc, #RichFaces SoftwareEngineer at JBoss by Red Hat RichFaces Core Developer
- 4. Seam, Arquillian andHTML5 enthusiast
- 5. JBoss Testing Initiative member
- 6. JSF Testing: AgendaOutline up-to-date state
- 7.
- 8.
- 9. Checklist Are theresome frameworks targeting JSF app testing?
- 10. Are RichFaces simplytestable?
- 11. What is JBossTesting Initiative?
- 12. Story begins... JavaEE testing was always pain Start a container
- 13. Build and deployarchive
- 14.
- 15. Deal with classpathisolation
- 16.
- 17. ...sad story TestingJSF isn't exception Black-box testing
- 18. Mocking JSF APIAnd bears additional challenges UI
- 19. No one ableto save the World?
- 20. Wait, there issomeone... Exceptional who is not satisfied how things goes Who is brave to change the game
- 21. Arquillian is comingon Earth Heavy equipment make the testing a breeze!
- 22. Arquillian saves theWorld
- 23. Arquillian's Test FactsAs easy as writing unit test
- 24.
- 25.
- 26.
- 27. Arquillian Container-oriented testingframework Abstracts test lifecycle including deployment
- 28. and container managementFocus on test logic
- 29. JBoss Testing InitiativeLead by Aslak Knutsen
- 30. In-container Approach Starta container
- 31. Package and deploytest archive
- 32.
- 33.
- 34.
- 35. Arquillian's Equipment (1)Unit testing framework runner JUnit, TestNG Deployable test archive
- 36. Packaging ShrinkWrap Programmaticcreation of Test Archives JARs, WARs, EARs Fluent Java API
- 37.
- 38. Developed by JBossCommunity Lead by Andrew Lee Rubinger
- 39. Arquillian's Equipment (2)Target container Broad range of supported containers Test enrichers @Inject, @EJB, @Resource, @PersistenceContext
- 40.
- 41. Test Run ModesIn-container Test runs in same JVM
- 42. Invokes application directlyAs client Remote client
- 43. Java EE enrichmentnot available
- 44. Advantages of runningwith Arquillian
- 45. Summary Arquillian Rethoughintegration testing
- 46. Makes Java EEcomponents testable
- 47.
- 48. Simplifies test developmentand maintenance
- 49.
- 50. Powerful Extensions Arquillianopens new possibilities
- 51. Rethinking of toolingHtmlUnit JSFUnit Selenium / WebDriver Ajocado
- 52.
- 53. JSFUnit HtmlUnit onSteroids
- 54. Takes test fromclient to server and back Developed in JBoss Community Lead by Stan Silvert
- 55. JSFUnit: Gray-box TestingManaged Beans
- 56.
- 57.
- 58.
- 59.
- 60.
- 61. Allowed UI testingof RichFaces Developed in JBoss Community Lead by Lukáš Fryč
- 62. Ajocado: AJAX-ready SeleniumRequest Interception
- 63.
- 64.
- 65.
- 66.
- 67. Drone Hard-Working FunctionalTester Selenium
- 68.
- 69.
- 70. Developed by JBossCommunity Lead by Karel Piwko
- 71. Drone: Real-Browser TestingTake advantages of Arquillian and brings Browser lifecycle to test Drone manages browser session
- 72. inject test dependenciesbrowser controller
- 73.
- 74. Tool Summary ArquillianCore White-box testing JSFUnit Gray-box testing Ajocado + Drone Black-box testing
- 75. How does itfit to JSF and RichFaces?
- 76.
- 77. Java EE ComponentTesting Test your model in isolation EJBs, POJOs In real environment container
- 78. JSF Integration TestingVerify client and server state in one test
- 79. Functional Testing Verifywhat user experiences
- 80. Do it reliableMaking model deterministic
- 81. Shading integration interfacesDB, Messaging
- 82. Time for RethinkingGoals Right tool for the job
- 83.
- 84. Test in JavaIt's simple Test in IDE It's fast
- 85.
- 86. Conditions in RichFaces4 Semantic markup CSS classes Well-defined Component API Java
- 87.
- 88. Are RichFaces Testable?Yes , they are 2,350 unique functional tests 18,800 tests
- 89. Thanks to Ajocadoand Arquillian Testable Component Model
- 90.
- 91. What has notbeen covered? Visual Verification - RushEye
- 92. Failure injection -ByteMan
- 93.
- 94. Verify JSF internalinteractions Testing Mobile Devices
- 95. JavaScript Drone torun your unit tests In real browsers (using Selenium)
- 96. Setup once, runeverywhere
- 97.
- 98. Spying on JSFClasses Verify what happens in JSF impl.? Spy JSF classes
- 99. Delegate to realimplementation
- 100. But verify whatmethods are called
- 101. Testing Mobile DevicesSupport for Mobile Devices Device emulators Managing lifecycle of emulator Real devices Managing device driver Arquillian Drone
- 102. Testing Through Wholethe Platform
- 103. JBoss Testing InitiativeContribution of many JBoss projects With cohesive leadership Widely supported by Community Which feels the need for change Targeting only one goal Making the testing breeze!
- 104.
- 105. Checklist Are theresome frameworks targeting JSF app testing?
- 106. Are RichFaces simplytestable?
- 107. What is JBossTesting Initiative?
- 108. Resources Project SitesArquillian - bit.ly/aREYip
- 109.
- 110.
- 111. JSFUnit – bit.ly/mio87Tirc.freenode.net #jbosstesting
- 112.
- 113.
- 114.
- 115. Testing JSF with Arquillian & Selenium Q/A by Lukáš Fryč