Patterns of a “good” Test Automation Framework, Locators & Data!
Building a Test Automation Framework is easy - there are so many resources / guides / blogs / etc. available to help you get started and help solve the issues you get along the journey.
However, building a "good" Test Automation Framework is not very easy. There are a lot of principles and practices you need to use, in the right context, with a good set of skills required to make the Test Automation Framework maintainable, scalable and reusable.
Design Patterns play a big role in helping achieve this goal of building a good and robust framework.
In this talk, we will talk about, and see examples of various types of patterns you can use for:
- Build your Test Automation Framework
- Test Data Management
- Locators / IDs (for finding / interacting with elements in the browser / app)
Using these patterns you will be able to build a good framework, that will help keep your tests running fast, and reliably in your CI / CD setup!
Outline/Structure of the Demonstration
- What is a pattern? - 1 min
- Patterns for building a good, robust, scalable, maintainable Test Automation Framework - with examples, Advantages and Disadvantages - 10 min
- Patterns for Test Data Management - with examples, Advantages and Disadvantages - 20 min
- Patterns for Locators / IDs (for finding / interacting with elements in the browser / app) - with examples, Advantages and Disadvantages - 5 min
Q&A all along the way, and in the remaining time
- Patterns for building Test Automation Framework
- Patterns for Test Data Management, with pros and cons of each
- Patterns for managing locators / IDs for interaction with UI
Developers, Testers, Everyone involved in Test Automation
schedule Submitted 5 years ago
People who liked this proposal, also liked:
Tony Xavier - Challenges and Best Practices: Creating Customer Focused Documentation in an Agile FrameworkTony XavierDocumentation/Project LeadInnovatia
schedule 4 years agoSold Out!
Agile is an increasingly popular development method primarily used by software companies. In Agile software development, work is confined to a regular, repeatable work cycle, known as Sprint. A sprint typically lasts for two to three weeks. In Agile, development teams strive to deliver a fully functioning, high quality, and potentially shippable product increment at the end of each sprint. Hence, product documentation becomes an essential part of the sprint deliverable to meet stakeholder requirement. Since, the primary focus of Agile development is to deliver products with high quality, technical communicators are expected to create customer focused documentation with high quality.
Creating Customer focused documents involves paying great attention to needs and opinions of customers, and creating documents with a purpose. As writers we must ensure that the documents we create focus on the needs of the actual customers of the document and provides value. As writers we must identify who the potential customer(s) for our documentation are, what they require, and create minimal documentation that they actually need. By understanding the needs of our customers we will be able to deliver customer focused documentation with high quality. However, the combination of Agile’s high speed of development, short delivery cycles, and limited requirements documentation presents a unique set of challenges in creating customer-focused documentation.
This paper highlights some of the challenges writers face and provides best practices that can be used in creating customer-focused documentation in an Agile framework.