Sharing the pain in Automating with Protractor & WebDriver
There is a saying ..."Sukh baatne se badhta hai, dukh baatne se kam hota hai", translated as - "happiness increases & sadness reduces on sharing with others".
We want to take this opportunity to share with our experiences - the good and the bad, in the journey of building a Test Automation framework for an AngularJS based application.
We will learn, by a case study, what thought process we applied on the given context (product, team, skills, capabilities, long term vision) to come up with an appropriate Test Automation Strategy. This Test Automation strategy covered all aspects of Test Automation - Unit, Integration, UI - i.e. End-2-End tests (E2E).
Lastly, we will share the challenges that came up in the implementation of the Test Automation, and how we overcame them. This will also include how we managed to get the tests running in Jenkins - a Continuous Integration tool.
This discussion is applicable to all team members who are working on Test Automation!
P.S. We will be attempting to make a sample protractor-based automation framework available on github for anyone to use as a starting point for setting up protractor-based Test Automation framework.
Outline/Structure of the Case Study
- Explain the case study - 2 min
- Tech stack & tool evaluation, and why Protractor seemed to be the right choice - 10 min
- Challenges using Protractor - 10 min
- Overcoming the challenges - 10 min
- The features we have built in the Test Automation Framework - 10 min
- Approach for test automation tech stack & tool evaluation
- Tips to build e2e test automation framework using protractor
Testers, Automation Testers, QAs, Developers, any other roles / team members involved with Automation
schedule Submitted 4 years ago
People who liked this proposal, also liked:
Anand Bagmar - Test Data - Food for your Test Automation Framework!Anand BagmarSoftware Quality EvangelistEssence of Testing
schedule 4 years agoSold Out!
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.
Teams already building 1000s of tests of various types - UI, web service-based, integration, unit, etc. is a proof of that.
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.
In this talk, we will focus on one of the critical aspects and patterns in building the Test Automation framework - Test Data!
We will look at different data patterns as options and techniques how to create, manage, use, reuse Test Data in a way to keep the tests running in an reliable and deterministic way. We will also discuss what questions to ask, what things to think about in selecting your approach for Test Data!
This discussion will be applicable for any type of Test Automation (web / mobile / desktop), but, we will focus primarily on UI automation frameworks, ex. using Selenium.
Sargis Sargsyan - Better Page Object Handling with Loadable Component PatternSargis SargsyanDirector, Quality AssurancePicsArt Inc.
schedule 4 years agoSold Out!
One of the painful problems in Selenium automated testing is determining whether a HTML page has been loaded. This is especially the case when web application uses a JS heavy framework such as the popular AngularJS.
During this talk we will discuss how to handle Selenium Page Object pattern better with Loadable Component.
The Loadable Component helps test case developers make sure that the page or a component of the page is loaded successfully. I will share my experience about the concept of the Loadable Component and Page Object patterns.