Testing Grails Applications With Selenium Rc
2 likes1,760 views
The document discusses testing Grails applications using Selenium RC, focusing on installation and execution of tests. It highlights the benefits of using the Page Object pattern and the ease of migrating from Selenese, along with the integration of BDD frameworks. Additionally, it provides insights into writing better-structured tests and leveraging tools like Spock for better testing outcomes.
Testing Grails Applications With Selenium Rc
- 1. Testing Grails Applications with Selenium RC Rob Fletcher, Energized Work
- 2. Running Selenium RC Tests grails install-plugin selenium-rc grails test-app grails test-app -functional
- 3. Browsers grails -Dselenium.browser=*firefox test-app
- 4. Selenium RC vs. Selenium IDE
- 6. Writing Selenium RC Tests Use @Mixin(SeleniumTest) Simple
- 7. Works with non-JUnit frameworks Extend GrailsSeleniumTestCase Offers Selenese-like assertions, e.g. assertTextPresent
- 8. Easy migration from Selenese Use Page Object Pattern Tests do not interact directly with Selenium
- 9. The Page Object Pattern
- 10. Page Object Test Example
- 13. Data Driving
- 15. BDD Frameworks
- 17. rfletcherEW adhockery.blogspot.com energizedwork.com github.com/robfletcher/grails-selenium-rc
Editor's Notes
- #2: Comparison with webtest/g-func Comparison with Selenium IDE Test examples Running tests Browsers Page Objects Data Driving Spock/BDD
- #3: Show example suite run
- #5: Selenese not a 'real' language Sequence, Selection & Iteration (1 out of 3) No encapsulation / modularity
- #6: Selenese tests as a 'run-on sentence' divide into methods simpler modularity (no custom commands) leads into… less repetition… page object pattern Bits of coverage hide in long tests Temptation to extend tests
- #8: What is a page object? exposes methods that reflect the things the user can see and do on a page eliminate duplication by building abstractions hides the detail of how code completion tests responsible for assertions, not page object Underlying implementation can be changed
- #9: Note does not extend or mixin Selenium test classes
- #10: shows how page object hide detail of implementation Page object handles position of elements in table, test can access by name
- #11: Factory method that opens URL Navigation method that returns another page object Scrapes error messages and returns in useful form Returns element value if present (can't do in Selenese) Uses MOP to override property access to type in form fields
- #12: using monolithic data setup Build test data Fixtures tearDown
- #13: withTransaction blocks ensure data committed and errors thrown right away Importance of tearDown