This post is based my question in stackoverflow site. These questions help us learn best practices while developing an automation framework.
Summarizing Discussion Points
- Page Object test design pattern is a good approach in building automation framework. Based on it only I have written example posts
- Don't use the Selenium IDE generated code as Automation Framework base
- Build a very good underlying framework architecture and refactor it as you keep updating the suite
- Learn Design patterns and Apply it wherever applicable
- 3 layer test automation framework is very good. I feel convinced with this approach.
- GUI Level Testing
- Methods Level Testing
- Database Checks
- Selenium - Page Object Pattern
- Selenium WebDriver: Page Object Pattern and PageFactory
- Verifying email configuration using Selenium
- ANT build for Selenium Java Project
- Selenium Grid I.O Configuration
- Selenium-ANT-TestNG (SAT) Framework
- Selenium Tutorial to set up a Selenium Grid
- Common Test Patterns and Reuse of Test Designs - Summarizes Test Data and Operations based on Application Type. Good read to arrive at Test Data, Test Scenarios, Edge Case Scenarios.
- Quality in the Test Automation Review Process and Design Review Template - Very Good Article on documenting and sharing Test Automation Framework Code, Architecture and Implmentation Details
- Test Automation Design Pattern - Approach for building UI Automation Framework
- Test Harness Design Patterns -Summarizes passing data in Flat Files, Excel, XML
- Lightweight UI Test Automation with .NET - Good Article on WinForm Test Automation
- Silverlight UI Automation Testing using Prism 4.0
- UI Automation Verify (UIA Verify) Test Automation Framework
- .NET Based Test Automation Framework Available in Code Plex
- How to implement UI testing without shooting yourself in the foot
- Selenium RC Java Patterns: Watch this Space
- Testing a JavaEE database application
- Building a GUI test automation framework: Structuring the project
- Click on Dynamic Objects at Dynamic Positions in Selenium
Integration Test Principles - Notes from the post
- Configuration should be minimal (Pointing to a different Db to run a test)
- Test cases should be independent (Select and run few cases)
- Tests should be efficient
- The test suite should clean up after itself (Good to clear logs/data)
Any comments / suggestions please comment on this blog post / alternatively you can connect on my email provided in homepage.
Happy Reading!!
No comments:
Post a Comment