Slides from my talk in Selenium Conference 2016 about "Sharing the pain with Protractor & Selenium WebDriver"
See blog for more information - http://essenceoftesting.blogspot.com/2016/06/sharing-pain-using-protractor.html
My blog: http://essenceoftesting.blogspot.com
Slides from my talk in UNICOM's Next Generation Testing Conference on 13th December in Bangalore on "The What, Why and How of Web Analytics Testing". This is based on my open-source tool - WAAT.
More information about the talk is available here: http://goo.gl/FxISG
Information about WAAT is available here: http://goo.gl/oUNHU
This document discusses Selenium with Protractor for testing Angular applications. It covers the necessary prerequisites like Node.js, Java, NPM. It also discusses configurations, locators, debugging, reporting and the differences between using traditional Selenium locators vs Angular locators in Protractor.
Better End-to-End Testing with Page Objects Model using Protractor
This presentation focuses on implementing Page Objects Model using Protractor for AngularJS apps for more maintainable, reusable and flexible end-to-end testing for your project. The presentations was done at 99X Technology as a Tech Talk session done by Team Finale.
Andrew Eisenberg gives an overview of UI testing with Protractor. He discusses installing and running Protractor, writing basic tests, more complex test scenarios using page objects and promises, debugging tips, and considerations around when and how to use Protractor for UI testing AngularJS applications. While Protractor is a powerful tool, he notes it has limitations and maintenance costs, and manual testing may be better for unstable UIs and use cases in flux.
The document discusses Protractor, an end-to-end test framework for AngularJS applications. It provides an overview of Protractor, how it differs from Selenium WebDriver, how to install and configure it, how to write tests using the Page Object Model pattern, and how to structure tests into suites and specs. Key aspects covered include Protractor's Angular-specific features, use of Jasmine, and capabilities like multi-browser testing.
I presented "What is WAAT" in "vodQA - Chennai" conference in Jan 2012. This is the slide deck I used.
I walked through what is web analytics, and then how WAAT can be used to automate the testing of the web analytics tags being reported from the client browser.
Automated testing is important to reduce the time and costs of manual testing. Cucumber is a behavior-driven development framework that allows writing automated acceptance tests in plain language. It executes tests written in its own language called Gherkin. Each Cucumber feature file describes a single feature or scenario using keywords like Feature, Scenario, Given, When, Then. Benefits of Cucumber include involving business stakeholders through human-readable tests, focusing on end-user experience, and easier code reuse and test execution.
This document discusses end-to-end testing with Protractor.js. It introduces Protractor and describes how it can be used to test Angular applications directly within browsers using WebDriverJS. It also discusses best practices like using page object patterns to organize tests and hide implementation details. Key aspects covered include setting up tests, writing maintainable page objects, and decomposing pages into reusable sections and fields.
Protractor is an end-to-end test framework for AngularJS applications built on top of Selenium WebDriver. It runs tests against an application in a real browser, interacting with it as a user would. Protractor provides AngularJS-specific APIs and tools to help with debugging on top of WebDriverJS. Functional tests are the foundation of quality but should be isolated and decoupled from the UI using patterns like page objects. Protractor is ready to use today for testing AngularJS applications.
Creating automated functional tests of your web application with Selenium IDE is quick and easy, but leads to massive duplication in your test scripts. See why this duplication is a problem, and how to address it using a simple design pattern called the Page Object.
APIs are proposed as an alternative to page objects for reducing repetition, improving maintenance and readability in tests. APIs abstract the test code away from the page structure by making calls to functions that interact with the system under test via its API. While APIs can improve tests, they require close cooperation from developers to implement and do not completely replace page objects due to upfront costs.
This document provides an overview of end-to-end testing with Protractor by summarizing various terminology, demonstrating example tests, and discussing continuous integration practices. It defines key Angular and testing concepts like directives, dependency injection, Jasmine, and WebDriver. Example tests are shown for a calculator app and a mock Facebook app. Continuous integration is discussed in the context of running Protractor tests within Docker containers as part of the software delivery pipeline.
Better Page Object Handling with Loadable Component Pattern
This document discusses the Loadable Component pattern for improving page object handling in Selenium tests. It begins with an introduction to page object patterns and common failures. It then covers topics like wait strategies in Selenium, the LoadableComponent and SlowLoadableComponent patterns, and implementing these patterns on an existing project. Examples are provided in Java of how to update base page classes and page object classes to use these patterns. Common failures like brittle tests are also discussed.
Protractor end-to-end testing framework for angular js
Protractor is an end-to-end test framework for AngularJS applications that runs tests against a real browser, interacting with the application as a user would. It is built on WebDriverJS and uses native events and browser-specific drivers to test asynchronous behavior and support for AngularJS. Protractor tests can run in any browser and interact directly with page elements rather than testing JavaScript code.
This document provides an overview of Protractor, an end-to-end test framework for AngularJS applications. It discusses prerequisites for setting up Protractor, including installing Node.js and Java. Steps are outlined for configuring Protractor, writing a first test, and running tests. Code examples are also shown for interacting with Angular elements in tests using Protractor capabilities. The document aims to demonstrate the basics of Protractor through a simple todo application example and code snippets.
Carmen Popoviciu - Protractor styleguide | Codemotion Milan 2015
In this talk, I would like to speak about best practices for writing e2e tests with Protractor. The styleguide that I will introduce, is a joint initiative of mine and @andresdom from Google. Some of the subjects that will be covered include why e2e testing is important, what e2e tests should cover, naming conventions, selector strategies, page objects, helper objects and performance considerations. That and lots of smileys obviously, because we wanted to smiley all the things ...right? ¯\_(ツ)_/¯
Session from GIDS 2014, showing how to do automated Web testing using a variety of JavaScript frameworks, including QUnit, Jasmine, Protractor, Selenium, and PhantomJS
The document discusses best practices, tips, performance, and debugging strategies for Protractor, an end-to-end testing framework for AngularJS applications. It addresses common problems like unknown window sizes, fragile tests due to small HTML changes, and long test run times. Solutions include setting the window size before tests, using page objects to abstract the HTML, enabling sharding to run tests in parallel, and integrating with IDEs for debugging. The tips are from Sergey Bolshchikov, a developer advocate and creator of resources for front-end developers.
Test Data - Food for your Test Automation Framework
Slides from my talk in Selenium Conference 2016, Bangalore
Blog post: http://essenceoftesting.blogspot.com/2016/06/test-data-food-for-test-automation.html
Abstract:
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.
Video & blog post will be linked soon!
Slides from workshop conducted at ThoughtWorks, Pune in vodQA, on Sat, 27th August, 2016.
Workshop Facilitators - Anand Bagmar, Smriti Tuteja, Pallipuspa Samal, Rohit Singhal, S Ramalingam, Shilpa G
More information about vodQA, and this workshop can be found from the following links -
https://essenceoftesting.blogspot.com/2016/08/vodqa-pune-less-talk-only-action-agenda.html
https://essenceoftesting.blogspot.com/search/label/vodQA
https://essenceoftesting.blogspot.com/search/label/waat
Slides from my 4-hour workshop on Client-Side Performance Testing conducted at Phoenix, AZ in STPCon 2017 (March).
Workshop Takeaways:
Understand difference between is Performance Testing and Performance Engineering.
Hand’s on experience of some open-source tools to monitor, measure and automate Client-side Performance Testing.
Examples / code walk-through of some ways to automate Client-side Performance Testing.
See blog for more details - https://essenceoftesting.blogspot.com/2017/03/workshop-client-side-performance.html
This document provides an overview of Cucumber, a behavior-driven development framework. It discusses what BDD is, the benefits it provides like usability, fewer defects, and living documentation. Popular BDD tools like Cucumber, Jasmine and JBehave are mentioned. Cucumber is introduced in more detail, explaining how it executes scenarios using a Given, When, Then format and supports multiple programming languages. Hands-on examples demonstrate features like data and table-driven execution, background, hooks, tags and reports. Suggested additional reading materials on BDD and Cucumber are also provided.
Slides from the workshop I conducted on "Client-side Performance Testing".
Abstract of the workshop:
In this workshop, we will see the different dimensions of Performance Testing and Performance Engineering, and focus on Client-side Performance Testing.
Before we get to doing some Client-side Performance Testing activities, we will first understand how to look at client-side performance, and putting that in the context of the product under test. We will see, using a case study, the impact of caching on performance, the good & the bad! We will then experiment with some tools like WebPageTest and Page Speed to understand how to measure client-side performance.
Lastly - just understanding the performance of the product is not sufficient. We will look at how to automate the testing for this activity - using WebPageTest (private instance setup), and experiment with yslow - as a low-cost, programatic alternative to WebPageTest.
The what, why and how of web analytics testingAnand Bagmar
Slides from my talk in UNICOM's Next Generation Testing Conference on 13th December in Bangalore on "The What, Why and How of Web Analytics Testing". This is based on my open-source tool - WAAT.
More information about the talk is available here: http://goo.gl/FxISG
Information about WAAT is available here: http://goo.gl/oUNHU
This document discusses Selenium with Protractor for testing Angular applications. It covers the necessary prerequisites like Node.js, Java, NPM. It also discusses configurations, locators, debugging, reporting and the differences between using traditional Selenium locators vs Angular locators in Protractor.
Better End-to-End Testing with Page Objects Model using ProtractorKasun Kodagoda
This presentation focuses on implementing Page Objects Model using Protractor for AngularJS apps for more maintainable, reusable and flexible end-to-end testing for your project. The presentations was done at 99X Technology as a Tech Talk session done by Team Finale.
Andrew Eisenberg gives an overview of UI testing with Protractor. He discusses installing and running Protractor, writing basic tests, more complex test scenarios using page objects and promises, debugging tips, and considerations around when and how to use Protractor for UI testing AngularJS applications. While Protractor is a powerful tool, he notes it has limitations and maintenance costs, and manual testing may be better for unstable UIs and use cases in flux.
The document discusses Protractor, an end-to-end test framework for AngularJS applications. It provides an overview of Protractor, how it differs from Selenium WebDriver, how to install and configure it, how to write tests using the Page Object Model pattern, and how to structure tests into suites and specs. Key aspects covered include Protractor's Angular-specific features, use of Jasmine, and capabilities like multi-browser testing.
I presented "What is WAAT" in "vodQA - Chennai" conference in Jan 2012. This is the slide deck I used.
I walked through what is web analytics, and then how WAAT can be used to automate the testing of the web analytics tags being reported from the client browser.
Automated testing is important to reduce the time and costs of manual testing. Cucumber is a behavior-driven development framework that allows writing automated acceptance tests in plain language. It executes tests written in its own language called Gherkin. Each Cucumber feature file describes a single feature or scenario using keywords like Feature, Scenario, Given, When, Then. Benefits of Cucumber include involving business stakeholders through human-readable tests, focusing on end-user experience, and easier code reuse and test execution.
This document discusses end-to-end testing with Protractor.js. It introduces Protractor and describes how it can be used to test Angular applications directly within browsers using WebDriverJS. It also discusses best practices like using page object patterns to organize tests and hide implementation details. Key aspects covered include setting up tests, writing maintainable page objects, and decomposing pages into reusable sections and fields.
Protractor is an end-to-end test framework for AngularJS applications built on top of Selenium WebDriver. It runs tests against an application in a real browser, interacting with it as a user would. Protractor provides AngularJS-specific APIs and tools to help with debugging on top of WebDriverJS. Functional tests are the foundation of quality but should be isolated and decoupled from the UI using patterns like page objects. Protractor is ready to use today for testing AngularJS applications.
Creating automated functional tests of your web application with Selenium IDE is quick and easy, but leads to massive duplication in your test scripts. See why this duplication is a problem, and how to address it using a simple design pattern called the Page Object.
APIs: A Better Alternative to Page ObjectsSauce Labs
APIs are proposed as an alternative to page objects for reducing repetition, improving maintenance and readability in tests. APIs abstract the test code away from the page structure by making calls to functions that interact with the system under test via its API. While APIs can improve tests, they require close cooperation from developers to implement and do not completely replace page objects due to upfront costs.
This document provides an overview of end-to-end testing with Protractor by summarizing various terminology, demonstrating example tests, and discussing continuous integration practices. It defines key Angular and testing concepts like directives, dependency injection, Jasmine, and WebDriver. Example tests are shown for a calculator app and a mock Facebook app. Continuous integration is discussed in the context of running Protractor tests within Docker containers as part of the software delivery pipeline.
Better Page Object Handling with Loadable Component PatternSQALab
This document discusses the Loadable Component pattern for improving page object handling in Selenium tests. It begins with an introduction to page object patterns and common failures. It then covers topics like wait strategies in Selenium, the LoadableComponent and SlowLoadableComponent patterns, and implementing these patterns on an existing project. Examples are provided in Java of how to update base page classes and page object classes to use these patterns. Common failures like brittle tests are also discussed.
Protractor end-to-end testing framework for angular jscodeandyou forums
Protractor is an end-to-end test framework for AngularJS applications that runs tests against a real browser, interacting with the application as a user would. It is built on WebDriverJS and uses native events and browser-specific drivers to test asynchronous behavior and support for AngularJS. Protractor tests can run in any browser and interact directly with page elements rather than testing JavaScript code.
This document provides an overview of Protractor, an end-to-end test framework for AngularJS applications. It discusses prerequisites for setting up Protractor, including installing Node.js and Java. Steps are outlined for configuring Protractor, writing a first test, and running tests. Code examples are also shown for interacting with Angular elements in tests using Protractor capabilities. The document aims to demonstrate the basics of Protractor through a simple todo application example and code snippets.
Carmen Popoviciu - Protractor styleguide | Codemotion Milan 2015Codemotion
In this talk, I would like to speak about best practices for writing e2e tests with Protractor. The styleguide that I will introduce, is a joint initiative of mine and @andresdom from Google. Some of the subjects that will be covered include why e2e testing is important, what e2e tests should cover, naming conventions, selector strategies, page objects, helper objects and performance considerations. That and lots of smileys obviously, because we wanted to smiley all the things ...right? ¯\_(ツ)_/¯
Session from GIDS 2014, showing how to do automated Web testing using a variety of JavaScript frameworks, including QUnit, Jasmine, Protractor, Selenium, and PhantomJS
The document discusses best practices, tips, performance, and debugging strategies for Protractor, an end-to-end testing framework for AngularJS applications. It addresses common problems like unknown window sizes, fragile tests due to small HTML changes, and long test run times. Solutions include setting the window size before tests, using page objects to abstract the HTML, enabling sharding to run tests in parallel, and integrating with IDEs for debugging. The tips are from Sergey Bolshchikov, a developer advocate and creator of resources for front-end developers.
Test Data - Food for your Test Automation FrameworkAnand Bagmar
Slides from my talk in Selenium Conference 2016, Bangalore
Blog post: http://essenceoftesting.blogspot.com/2016/06/test-data-food-for-test-automation.html
Abstract:
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.
Video & blog post will be linked soon!
Slides from workshop conducted at ThoughtWorks, Pune in vodQA, on Sat, 27th August, 2016.
Workshop Facilitators - Anand Bagmar, Smriti Tuteja, Pallipuspa Samal, Rohit Singhal, S Ramalingam, Shilpa G
More information about vodQA, and this workshop can be found from the following links -
https://essenceoftesting.blogspot.com/2016/08/vodqa-pune-less-talk-only-action-agenda.html
https://essenceoftesting.blogspot.com/search/label/vodQA
https://essenceoftesting.blogspot.com/search/label/waat
Slides from my 4-hour workshop on Client-Side Performance Testing conducted at Phoenix, AZ in STPCon 2017 (March).
Workshop Takeaways:
Understand difference between is Performance Testing and Performance Engineering.
Hand’s on experience of some open-source tools to monitor, measure and automate Client-side Performance Testing.
Examples / code walk-through of some ways to automate Client-side Performance Testing.
See blog for more details - https://essenceoftesting.blogspot.com/2017/03/workshop-client-side-performance.html
This document discusses the perils of using the page object pattern for test automation frameworks. It describes the page object pattern, how it can be used to model pages in code and reduce duplication. However, it also notes limitations like tests becoming too implementation focused rather than intent focused. It then introduces a business layer page object pattern that aims to address these limitations by validating business requirements and separating concerns with abstraction layers. This allows the test pyramid to remain balanced and makes maintenance and scaling easier.
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!
Slides for the presentation I did for the Vancouver AngularJS meetup group.
http://www.meetup.com/vanangularJS/events/216391652/
The code is available on my github account.
https://github.com/aeisenberg/angular-app/tree/vanangular-protractor
(Notice the branch is not master.)
Integration Testing in Enterprises using TaaSAnand Bagmar
Typically in organizations, there are multiple projects / products. These products may be of implemented using tech-stacks over many years. Yet - they interact with each other in some way. To manage the complexity around Test Automation, many organizations prefer to have a common Test Automation solution across these products in an effort to build, standardize and maintain the framework.
However, this is not a good idea! With this approach one potentially ends up having to compromise on the quality of automation that can be done for each product, limited by the toolset.
The better approach would be to use the tools and technologies that are "right" for each product. This does have other disadvantages, but you would ensure each product is well tested! The only missing piece that remains is that these different products talk with each other. You need to test the integration between them in an automated way to verify all is well.
"TaaS" is an open-source product solution that allows you do achieve the "correct" way of doing integration testing across a variety of products via Test Automation.
Example:
For one set of products, Selenium-based toolset may be the right choice, where as for legacy reasons, QTP may be used for some other product. With TaaS - you will be able to automate the Integration Testing between these products, by re-using the tests already implemented in the individual product suites.
Bhumika S, Anand Bagmar (Thoughtworks)
How many times do we test the same things at multiple layers, multiple levels, adding time to the build process and testing cycle, delaying the feedback?
We know what to test and how to test, but what is the right place to test it?
In this workshop, we will demonstrate how we, as QA’s, can identify which tests can be classified as unit tests, integration tests, and functional tests. Using a case study, we will see how each component can be tested as part of unit testing; the integration of different parts and the functioning of a software system as a whole, and how functional tests fit into this big picture. We will then bring all these tests together to understand and build the testing pyramid and how it enables us to build the right testing framework with fewer Selenium, i.e., functional tests.
Agile India 2017 Conference is Asia's Largest and Premier Conference on Agile, Scrum, eXtreme Programming, Lean, Kanban, DevOps, Enterprise Agile, Lean Startup, Continuous Delivery, Research and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 6 - 12 March 2017 at ITC Gardenia, Bangalore. More details: http://2017.agileindia.org
What is Software Quality and how to measure it?Denys Zaiats
Software quality refers to the desirable attributes of software such as correctness, reliability, efficiency, integrity, usability, maintainability, testability, flexibility, portability, and interoperability. These attributes can be measured on a scale of 1 to 10 using methods like Scrum Poker. Teams should measure their software quality every 2 sprints in order to continuously improve processes, products, and development quality. Automating tests, keeping documentation up-to-date, and using efficient tools can help improve software quality over time.
Future of Testing, Test Automation and The Quality AnalystAnand Bagmar
In vodQA Hyderabad, I spoke on what I think is the "Future of Testing, Test Automation and the Quality Analyst". This is an evolved presentation from what I did in vodQA Bangalore (http://essenceoftesting.blogspot.in/2014/06/future-of-testing-test-automation-and.html)
This document discusses using Docker containers to improve testing workflows. It outlines challenges with traditional testing approaches that can slow down deployments. Containers are presented as a solution by providing isolated, portable testing environments. The rest of the document demonstrates how to test applications using Docker containers, Docker Compose, and Selenium with examples of API, web, and Selenium Grid tests. Best practices are provided for containerizing tests along with a proposed continuous integration workflow using containers.
Create the Future - Innovations in TestingAnand Bagmar
My keynote talk delivered in vodQA Pune, Innovations in Testing, on Sat, 6th June 2015, at ThoughtWorks, Pune.
Video available here: https://www.youtube.com/watch?v=EJcaUZYGDic
Protractor is an AngularJS end-to-end testing framework built on WebDriverJS and Selenium. It allows automating tests that involve interacting with a browser and verifies that Angular applications work as expected. Protractor uses promises and asynchronous control flow, requiring tests to be written differently than other frameworks. It can run tests across multiple browsers simultaneously using Selenium Grid and supports generating test reports.
Build the "right" regression suite using Behavior Driven Testing (BDT)Anand Bagmar
Slides from the workshop conducted in ThoughtWorks, vodQA Gurgaon on - "What is BDT, and how can you use this technique to identify the 'right' regression suite for your product"
Keyword-driven testing, Геннадий Алпаев
Keyword-driven подход к автоматизации тестирования был описан в литературе более 10ти лет назад, однако в русскоязычных источниках по этой теме информации довольно мало. В докладе Геннадий расскажет о том, в чем заключается подход, когда применяется, его достоинства и недостатки, а также покажет пример практической реализации Keyword-driven подхода для простого тестируемого приложения с помощью TestComplete и SilkTest.
Keyword-driven testing is a software testing methodology that uses predefined keywords to describe test cases instead of natural language. Keywords represent common testing actions and are associated with code that implements those actions. This allows testers to write automated test cases without extensive programming knowledge. The document discusses how to implement keyword-driven testing using the Maveryx test automation tool, including identifying keywords, writing test cases with keywords, implementing keyword code, and executing automated tests.
This document discusses client-side performance testing. It describes measuring client-side performance through synthetic monitoring tools like WebPageTest.org, SiteSpeed.io and ShowSlow which test page load speeds, and real user monitoring through Akamai RUM, Monitis RUM and Google Analytics. WebPageTest.org is demonstrated in more detail, showing how to use it to test pages and understand key metrics like time to first byte, time to start render and full page loaded time. Private instances and automation of WebPageTest is also covered. YSlow and Google PageSpeed are also mentioned as alternatives for measuring client performance.
Future of Testing, Test Automation and The Quality AnalystAnand Bagmar
My thoughts presented in vodQA at ThoughtWorks Bangalore on 21st June 2014 on what is the "Future of Testing, Test Automation and the Quality Analyst"
See my blog for more details: http://essenceoftesting.blogspot.in/2014/06/future-of-testing-test-automation-and.html
Tooling for Machine Learning: AWS Products, Open Source Tools, and DevOps Pra...SQUADEX
This document provides an overview of machine learning tooling on AWS, including data pipelines, modeling and training, and deployment. It discusses AWS products for streaming and batch data ingestion, machine learning services like Amazon Machine Learning, Amazon SageMaker, and AWS Deep Learning AMIs. It also provides best practices for notebooks, model maintenance, and ML lifecycle management using tools like MLFlow and KubeFlow. The document concludes that while AWS provides a strong foundation, operations require additional layers for successful and reproducible machine learning.
In a team which is developing mobile apps for multiple platforms, it becomes extremely difficult to maintain multiple Automation codebases and frameworks to test the app. This becomes a bigger problem when the same team is churning out multiple flavours of the same app.
What this showcases is how we have built an automation framework that tests 2 different flavours of an app along with using the same framework to test these apps across 3 different platforms.
The session will also include the challenges we faced while moving from a purely Functional approach to writing code to an Object-oriented approach to structure our automation code.
This will help other testing practitioners attending this session in building a robust automation framework with a very reliable and scalable codebase that can be extended beyond just one application/platform.
Enabling CD in Enterprises with Testing - Anand BagmarThoughtworks
This document discusses enabling continuous delivery in enterprises through testing. It defines continuous integration as integrating work frequently, at least daily, and verifying with automated builds and tests. Continuous delivery aims to make releases releasable at any time through frequent, automated testing. The document recommends automating testing from the unit to user interface level. It also discusses challenges like coordinating multiple teams and environments, and emphasizes establishing the right automated testing practices, processes, and tools to achieve continuous delivery.
This document discusses how to implement automated performance testing using Maven and JMeter. It describes configuring Maven to run JMeter tests as part of a continuous integration build cycle. Running performance tests automatically allows issues to be detected quickly before code is deployed. The process involves packaging JMeter tests with Maven, configuring Maven profiles and plugins to run tests across different environments and datasets, and using tools like Chronos and Bamboo for reporting and comparing performance over time.
The document discusses agile testing and how it differs from traditional testing methodologies. It outlines how agile transformations affect testing practices, requiring testers to shift from solely writing test scripts to participating in requirements definition and writing test cases earlier. It also discusses common types of agile testing like exploratory and risk-based testing. The document provides examples of open source tools that can be used for agile testing and highlights both advantages like reduced costs and faster delivery, and disadvantages like less documentation.
The document discusses how to deliver software fast while maintaining high quality through modern QA practices. It describes setting up a DevTest team that combines agile methodologies, automated testing, and testing software-as-a-service products on tight 1.5 month release cycles. The DevTest team builds reliable automation frameworks, performs continuous testing on every code push, and has the goal of deploying fixes within one day through a continuous deployment pipeline.
Have you ever wondered what the best way would be to test emails? Or how you would go about testing a messaging queue?
Making sure your components are correctly interacting with each other is both a tester and developer’s concern. Join us to get a better understanding of what you should test and how, both manually and automated.
This session is the first ever in which we will have two units working together to give you a nuanced insight on all aspects of integration testing. We’ll start off exploring the world of integration testing, defining the terminology, and creating a general understanding of what phases and kinds of testing exist. Later on we’ll delve into integration test automation, ranging from database integration testing to selenium UI testing and even as far as LDAP integration testing.
We have a wide variety of demos prepared where we will show you how easy it is to test various components of your infrastructure. Some examples:
- Database testing (JPA)
- Arquillian, exploring container testing, EJB testing and more
- Email testing
- SOAP testing using SoapUI
- LDAP testing
- JMS testing
Serverless in production, an experience report (Going Serverless)Yan Cui
1. The document discusses best practices for making serverless applications production ready, including practices around testing, monitoring, logging, configuration management, and continuous integration/deployment.
2. It recommends integrating serverless applications with services like API Gateway, Kinesis, DynamoDB, and SSM Parameter Store and considering practices like centralized logging, distributed tracing, role-based access controls, and parameterizing configurations.
3. The document emphasizes the importance of testing at the unit, integration, and end-to-end/acceptance levels and having automated testing and deployment pipelines to catch errors and deploy changes quickly and reliably.
Serverless in production, an experience report (JeffConf)Yan Cui
This document provides an experience report on getting serverless applications ready for production. It discusses several important considerations for production readiness including testing, monitoring and alerting, configuration management, security, and continuous integration/delivery pipelines. The document also shares lessons learned from rebuilding several services using a serverless approach at Skype and the cost savings and velocity gains achieved.
Rahul Anand is a Senior Software Engineer and Performance Testing Analyst at Accenture with over 5 years of experience in performance testing, functional testing, and security testing. He has extensive experience using tools like LoadRunner, QC, and diagnostics tools to perform load, stress, endurance, and other types of performance tests on applications in the retail, utilities, and other domains. Rahul has worked on projects for clients such as Tesco, Best Buy, ALDO, and Hydro Quebec. He is proficient in languages like C and has strong analytical skills for performance testing and bottleneck analysis.
Real world selenium resume which gets more job interviewsABSoft Trainings
Don’t miss our “Real World Selenium Resume which gets more Job Interviews” where we will discuss what you should put in your Selenium resume and how, what you shouldn't put to make it amazing and excellent. Note that you can easily apply best practices/tips discussed in this post to other profiles, resumes as well like QTP automation tester, manual tester, developer, fresher.
Service Solahart 02199316735 Center solahart Pemanas Air Solar Water Heater Tenaga Matahari Kami Dari CV.DAVITAMA Menyediakan Jasa Perbaiakan Pemanas Air SOLAHART
Apakah mesin pemanas air anda bermasalah
1.TIDAK PANAS 2.BOCOR 3.BONGKAR PASANG
5.PENGGANTIAN SPAREPART 6.INSTALASI PIPA AIR PANAS 7.PENJUALAN UNIT
Dengan tenaga ahli kami yang berpengalaman secara profesional dapat kami tangani masalah mesin pemanas air.
Dengan pemanas air tenaga Matahari rutin diservice, maka akan mendapatkan 95% kebutuhan energy secara gratis dari Matahari.
KEUNTUNGAN EKONOMIS DARI PEMANAS AIR TENAGA MATAHARI
Pemanas Air memerlukan energi. Apakah energi tersebut harus dibeli atau tidak, tergantung apakah anda mempunyai Pemanas Air Tenaga Surya. Dengan Pemanas Air Tenaga Surya Solahart, anda dapat mengharapkan mendapat energi matahari yang bebas biaya sampai 95% dari total energi yang diperlukan. Prosentase ini tergantung pada kondisi iklim dan type Pemanas Air Tenaga Surya yang anda pakai.
CV. DAVINATAMA SERVICE
E-mail: [email protected] Nomer Telpon: +6221 99316735 Fax : +6221 48702925
This document discusses best practices for performance testing in Agile and DevOps environments. It recommends implementing early and continuous performance testing as part of CI/CD pipelines using tools like JMeter and WebPageTest. Additionally, it stresses the importance of system-level performance tests during targeted sprints and prior to production deployments. The use of application performance management tools to monitor tests and production is also highlighted to facilitate quick feedback loops and issue resolution.
What to Do—Develop Your Own Automation or Use Crowdsourced Testing?TechWell
Modern software products tend to have a rich UI that supports many user workflows, all of which need to be covered in testing. Agile organizations quickly discover that manual end-to-end testing neither supports their velocity nor provides respectable regression coverage. A common progression is to move from fully manual testing to record/replay, then to Selenium IDE style tests, then to automation based on Selenium WebDriver, perhaps with a BDD overlay. Daria Mehra has practiced this approach and shares her experience. She compares the Selenium style of automation to an alternative—crowdsourced test execution— which provides all the benefits of test automation, including continuous integration. This approach allows non-coders to express test cases in natural language, avoids the dependency on UI implementation, adds a “human eye” advantage, and provides the ability to massively parallelize tests for fast execution. Learn the pros and cons of end-to-end, UI-based test automation via Selenium compared to crowdsourcing. Find out how you can assess the suitability of these testing approaches for your needs.
Testing Vue Apps with Cypress.io (STLJS Meetup April 2018)Christian Catalan
Presented at the STLJS Meetup (St Louis, MO)
We dive into a Vue application used in semiconductor labs for transistor measurements. We discuss how get started with E2E testing with Cypress.io. And give a crash course into Vue applications.
Video: https://www.youtube.com/watch?v=dpB0YgnFyZQ
Quality attributes testing. From Architecture to test acceptanceIT Weekend
This document summarizes an expert's experience and qualifications in software architecture and automation testing, including 8 years of IT experience and a PhD in IT automation testing. It then discusses what software architecture is, how it is formed based on business, users and systems, and what quality attributes and acceptance criteria can be tested. Finally, it provides an example of defining acceptance criteria for a software error scenario using a specific methodology and tools.
Streamlining End-to-End Testing Automation with Azure DevOps Build & Release Pipelines
Automating end-to-end (e2e) test for Android and iOS native apps, and web apps, within Azure build and release pipelines, poses several challenges. This session dives into the key challenges and the repeatable solutions implemented across multiple teams at a leading Indian telecom disruptor, renowned for its affordable 4G/5G services, digital platforms, and broadband connectivity.
Challenge #1. Ensuring Test Environment Consistency: Establishing a standardized test execution environment across hundreds of Azure DevOps agents is crucial for achieving dependable testing results. This uniformity must seamlessly span from Build pipelines to various stages of the Release pipeline.
Challenge #2. Coordinated Test Execution Across Environments: Executing distinct subsets of tests using the same automation framework across diverse environments, such as the build pipeline and specific stages of the Release Pipeline, demands flexible and cohesive approaches.
Challenge #3. Testing on Linux-based Azure DevOps Agents: Conducting tests, particularly for web and native apps, on Azure DevOps Linux agents lacking browser or device connectivity presents specific challenges in attaining thorough testing coverage.
This session delves into how these challenges were addressed through:
1. Automate the setup of essential dependencies to ensure a consistent testing environment.
2. Create standardized templates for executing API tests, API workflow tests, and end-to-end tests in the Build pipeline, streamlining the testing process.
3. Implement task groups in Release pipeline stages to facilitate the execution of tests, ensuring consistency and efficiency across deployment phases.
4. Deploy browsers within Docker containers for web application testing, enhancing portability and scalability of testing environments.
5. Leverage diverse device farms dedicated to Android, iOS, and browser testing to cover a wide range of platforms and devices.
6. Integrate AI technology, such as Applitools Visual AI and Ultrafast Grid, to automate test execution and validation, improving accuracy and efficiency.
7. Utilize AI/ML-powered central test automation reporting server through platforms like reportportal.io, providing consolidated and real-time insights into test performance and issues.
These solutions not only facilitate comprehensive testing across platforms but also promote the principles of shift-left testing, enabling early feedback, implementing quality gates, and ensuring repeatability. By adopting these techniques, teams can effectively automate and execute tests, accelerating software delivery while upholding high-quality standards across Android, iOS, and web applications.
Automating the real-user scenarios across multi-apps, and multi-devicesAnand Bagmar
This document discusses teswiz, an open source framework for automating real-user scenarios across multiple apps, devices, users, and platforms. It can simulate user actions and behavior to test web, mobile web, Android, iOS, Windows, MacOS and Linux applications. Teswiz uses Cucumber, Appium, Selenium and other tools and supports features like multi-device testing, visual testing with Applitools, and generating reports with ReportPortal. The document provides instructions on getting started with teswiz and links to its GitHub page.
Visual Validation - The missing tip of the automation pyramid @GoT2022Anand Bagmar
The document discusses visual validation testing as a missing piece of the automation testing pyramid. Visual testing is important but challenging as it is typically done manually, which is tedious, error-prone, and difficult to scale. Automating visual testing can help by taking screenshots of expected user interfaces and comparing them to actual screenshots. However, automating also poses challenges around false positives/negatives, maintaining baselines, and accounting for product changes. The document promotes using artificial intelligence in visual test automation to help address these challenges and advocates for including visual testing in an organization's overall quality and automation strategy.
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!
Change Tyres In A Moving Car - Make Functional Test Automation Effective KeynoteAnand Bagmar
https://confengine.com/conferences/selenium-conf-2022/proposal/17141/changing-tyres-in-a-moving-car-making-functional-test-automation-effective
In my experience, I have seen teams struggle with more than one, and in many cases, all of the above statements.
On retrospection, I have realized, that most of these challenges are because of a combination of the following issues:
Lack of holistic vision, understanding, skills, and capabilities for taking on this seemingly easy activity of functional test automation
Lack of time for design, implementation, and maintenance of the automated test code
In this session, I will share, with examples, the features & capabilities that are not used right in Test Automation implementation resulting in you answering “NO” to the above statements. These are anti-patterns of functional automation implementation and have a negative impact on the quality of feedback from your automated tests.
More importantly, I will share approaches and solutions of how you can avoid these anti-patterns and evolve to answer “YES” to each of the above statements.
Slides from my talk on "Rewrite Vs Refactor" given at Agile India 2021. https://confengine.com/conferences/agile-india-2021/proposal/15495/rewrite-vs-refactor
In this session, I will share various examples and experiences and as a result of being in such situations, the factors I looked at when enhancing the code-base to decide - should I refactor or rewrite the code-under-consideration to be able to move forward faster, while moving towards the long-term vision.
Though I will focus on various examples of Test Automation, this session is applicable for any role that writes / maintains code of any nature.
Next Generation Functional & Visual Testing powered by AIAnand Bagmar
Slides from hands-on workshop at Agile India 2021.
Machine setup instructions are available in the proposal - https://confengine.com/conferences/agile-india-2021/proposal/15552/next-generation-functional-amp-visual-testing-powered-by-ai
In this workshop, using numerous examples, we will explore:
Why Automated Visual Validation is essential to be part of your Test Strategy
How Visual AI increases the coverage of your functional testing, while reducing the code, and increasing stability of your automated tests
Potential solutions / options for Automated Visual Testing, with pros & cons of each
How an AI-powered tool, Applitools Eyes, can solve this problem
Hands-on look at Applitools Visual AI and how to get started using it
The Best Test Automation Framework is...Anand Bagmar
I had the privilege of delivering the opening keynote at the recent Future Of Testing event focused on Test Automation Frameworks on 30th September 2021. My topic was “The best test automation framework is …”.
Here is the mind map I used in my keynote presentation.
https://applitools.com/future-of-testing-frameworks-north-america-2021/
Slides from my talk on how to Eradicate Flaky Tests from AppiumConf 2021
https://confengine.com/conferences/appium-conf-2021/proposal/15581/eradicate-flaky-tests
Slides used in workshop on "Getting started with Appium 2.0" at AppiumConf 2021
https://confengine.com/conferences/appium-conf-2021/proposal/15634/getting-started-with-appium-20
Visual Validation - The missing tip of the automation pyramid @AgileIndia2020Anand Bagmar
https://confengine.com/agile-india-2020/proposal/11065/visual-validation-the-missing-tip-of-the-automation-pyramid
The top of the pyramid is our UI / end-2-end functional tests - which simulate end-user behavior and interactions with the product-under test.
While Automation helps validate functionality of your product, aspects of UX validations can only be seen and captured by the human eye and is hence mostly a manual activity. This is an area where AI & ML can truly help.
With everyone wanting to be Agile, make quick releases, the look & feel / UX validation, which is a slow, and error-prone activity, quickly becomes a huge bottleneck. In addition, with any UX related issues propping up cause huge brand-value and revenue loss, may lead to social-trolling and worse - dilute your user-base.
In this session, using numerous examples, we will explore:
Why Automated Visual Validation is essential to be part of your Test Strategy
Potential solutions / options for Automated Visual Testing, with pros & cons of each
How an AI-powered tool, Applitools Eyes, can solve this problem.
This document outlines an agenda for a Selenium workshop. It covers topics like getting started with Selenium, implementing page object models and design patterns, handling test data, using assertions, and responsive web design testing. Exercises are provided to demonstrate concepts like building page objects, running tests across browsers, and using test data. The goal is to help students learn Selenium concepts and address common automation challenges.
Does your functional automation really add value?Anand Bagmar
We all know that automation is one of the key enablers for those on the CI-CD journey.
Most teams are:
• implementing automation
• talking about its benefits
• up-skilling themselves
• talking about tooling
• etc.
In my experience, unfortunately most of the functional automation that is built is:
• not optimal
• not fit-for-purpose
• does not run fast enough
• gives inconsistent feedback, hence unreliable
Hence, for the amount of effort invested in implementing automation, are you really getting the value from this activity?
In this talk, we will discuss these challenges and why it would lead to poor ROI of automation. More importantly, we will discuss the following techniques to make automation valuable:
• know the objective for the automation framework
• establish criteria for tests to be automated
• design your framework with proper abstraction layers
• develop using appropriate design patterns
It is easy to measure code coverage when running unit tests.
However, very frequently the following questions come up:
- How can we measure API test coverage and e2e / UI test coverage?
- Does e2e / UI test coverage add value?
- If not, what other data can we look at to know if the e2e tests have good coverage?
This session is about understanding the above questions, and finding solutions for the same.
When one has fun at work, work becomes fun. However, daily pressures, metrics, KPIs, and what not, have dissolved the fun, and made work drudgery in various ways. This creates stress for individuals, in teams, and across teams, there is mistrust, unnecessary competition, blame, finger-pointing ….What better way to learn, and re-learn the basics of life, work, team-work - than to play a game, have fun, and correlate it with how life and work indeed should be treated as a game, and we should have fun in this journey. Only then can people truly succeed, and so can organisations.Here, we will play a game – “Collaboration - A Taboo!” – where you will –Re-learn collaboration techniques via a game!Learning applicable for individuals & teams, in small or big organisationsRe-live your childhood when playing this gameBe prepared for a twist which will leave you thinking!
Visual Validation - The Missing Tip of the Automation PyramidAnand Bagmar
The Test Automation Pyramid is not a new concept. The top of the pyramid is our UI / end-2-end functional tests - which should cover the breadth of the product.
What the functional tests cannot capture though, is the aspects of UX validations that can only be seen and in some cases, captured by the human eye. This is where the new buzzwords of AI & ML can truly help.
In this session, we will explore why Visual Validation is an important cog in the wheel of Test Automation and also different tools and techniques that can help achieve this. We will also see a demo of Applitools Eyes - and how it can be a good option to close this gap in automation!
React and Next.js are complementary tools in web development. React, a JavaScript library, specializes in building user interfaces with its component-based architecture and efficient state management. Next.js extends React by providing server-side rendering, routing, and other utilities, making it ideal for building SEO-friendly, high-performance web applications.
React Native vs Flutter - SSTech SystemSSTech System
Your project needs and long-term objectives will ultimately choose which of React Native and Flutter to use. For applications using JavaScript and current web technologies in particular, React Native is a mature and trustworthy choice. For projects that value performance and customizability across many platforms, Flutter, on the other hand, provides outstanding performance and a unified UI development experience.
Efficient hot work permit software for safe, streamlined work permit management and compliance. Enhance safety today. Contact us on +353 214536034.
https://sheqnetwork.com/work-permit/
Sami provided a beginner-friendly introduction to Amazon Web Services (AWS), covering essential terms, products, and services for cloud deployment. Participants explored AWS' latest Gen AI offerings, making it accessible for those starting their cloud journey or integrating AI into coding practices.
Software development... for all? (keynote at ICSOFT'2024)miso_uam
Our world runs on software. It governs all major aspects of our life. It is an enabler for research and innovation, and is critical for business competitivity. Traditional software engineering techniques have achieved high effectiveness, but still may fall short on delivering software at the accelerated pace and with the increasing quality that future scenarios will require.
To attack this issue, some software paradigms raise the automation of software development via higher levels of abstraction through domain-specific languages (e.g., in model-driven engineering) and empowering non-professional developers with the possibility to build their own software (e.g., in low-code development approaches). In a software-demanding world, this is an attractive possibility, and perhaps -- paraphrasing Andy Warhol -- "in the future, everyone will be a developer for 15 minutes". However, to make this possible, methods are required to tweak languages to their context of use (crucial given the diversity of backgrounds and purposes), and the assistance to developers throughout the development process (especially critical for non-professionals).
In this keynote talk at ICSOFT'2024 I presented enabling techniques for this vision, supporting the creation of families of domain-specific languages, their adaptation to the usage context; and the augmentation of low-code environments with assistants and recommender systems to guide developers (professional or not) in the development process.
Discover the Power of ONEMONITAR: The Ultimate Mobile Spy App for Android Dev...onemonitarsoftware
Unlock the full potential of mobile monitoring with ONEMONITAR. Our advanced and discreet app offers a comprehensive suite of features, including hidden call recording, real-time GPS tracking, message monitoring, and much more.
Perfect for parents, employers, and anyone needing a reliable solution, ONEMONITAR ensures you stay informed and in control. Explore the key features of ONEMONITAR and see why it’s the trusted choice for Android device monitoring.
Share this infographic to spread the word about the ultimate mobile spy app!
Seamless PostgreSQL to Snowflake Data Transfer in 8 Simple StepsEstuary Flow
Unlock the full potential of your data by effortlessly migrating from PostgreSQL to Snowflake, the leading cloud data warehouse. This comprehensive guide presents an easy-to-follow 8-step process using Estuary Flow, an open-source data operations platform designed to simplify data pipelines.
Discover how to seamlessly transfer your PostgreSQL data to Snowflake, leveraging Estuary Flow's intuitive interface and powerful real-time replication capabilities. Harness the power of both platforms to create a robust data ecosystem that drives business intelligence, analytics, and data-driven decision-making.
Key Takeaways:
1. Effortless Migration: Learn how to migrate your PostgreSQL data to Snowflake in 8 simple steps, even with limited technical expertise.
2. Real-Time Insights: Achieve near-instantaneous data syncing for up-to-the-minute analytics and reporting.
3. Cost-Effective Solution: Lower your total cost of ownership (TCO) with Estuary Flow's efficient and scalable architecture.
4. Seamless Integration: Combine the strengths of PostgreSQL's transactional power with Snowflake's cloud-native scalability and data warehousing features.
Don't miss out on this opportunity to unlock the full potential of your data. Read & Download this comprehensive guide now and embark on a seamless data journey from PostgreSQL to Snowflake with Estuary Flow!
Try it Free: https://dashboard.estuary.dev/register
Attendance Tracking From Paper To DigitalTask Tracker
If you are having trouble deciding which time tracker tool is best for you, try "Task Tracker" app. It has numerous features, including the ability to check daily attendance sheet, and other that make team management easier.
Lots of bloggers are using Google AdSense now. It’s getting really popular. With AdSense, bloggers can make money by showing ads on their websites. Read this important article written by the experienced designers of the best website designing company in Delhi –
An MVP (Minimum Viable Product) mobile application is a streamlined version of a mobile app that includes only the core features necessary to address the primary needs of its users. The purpose of an MVP is to validate the app concept with minimal resources, gather user feedback, and identify any areas for improvement before investing in a full-scale development. This approach allows businesses to quickly launch their app, test its market viability, and make data-driven decisions for future enhancements, ensuring a higher likelihood of success and user satisfaction.
12. Unit (xUnit / JavaScript)
Component
Integration
View
Web Service
UI
Manual / Exploratory
P
e
r
f
o
r
m
a
n
c
e
S
e
c
u
r
i
t
y
Accessibility
TEST PYRAMID
16. CHALLENGES - JAVASCRIPT
What is Test Automation?
Synchronous,
Step-by-Step execution
ASynchronous
Callbacks & Promises!
Power of JavaScript?
17. CHALLENGES – BROWSER (& OS) SUPPORT
Browser / Driver Why? Challenges
phantomJS Headless execution
- easier for developers
- Seamless CI
integration
- Officially not
recommended by
Protractor
Chrome - End-user
requirement
- Excellent for
development &
testing
- Certain elements
“not visible” – though
worked with Firefox
Firefox - End-user
requirement
- Worked locally
- Worked in CI – in
headless (xvfb), but
NOT for maps
- Worked in headless
mode (xvfb) in
vagrant
19. CHALLENGES - ANGULAR
Type Example
Angular Directives Ex: ng-repeat, ng-model
Custom Directives Ex: third party libraries providing
multi-column select, Sliders for
range, Charts
Working with non-Angular Ex: Login, Admin
24. SOLUTIONS – DETERMINISTIC TEST DATA
q Same Test Data in all environments / tenants
q Minimal Environment specific configuration
q Intelligent ‘before’ & ‘after’ setups
27. DID WE SOLVE ALL THE PROBLEMS?
JUST KIDDING!!!
Of course, NO!!
- Maps
- Reports
- How many and where to put “assertions”?
- Use Soft-asserts
YES!!!
28. OUR TAKEAWAYS FROM THIS PAIN & GAIN!
q Choose tech-stack based on context
q Experiment & Fail-Fast!
q Proper Cost-Value evaluation
q Manage Risk (what to automate – now / later, and what NOT
to automate)
q Keep learning & sharing – new and better solutions
28
29. REFERENCES
Page Objects – Google - https://code.google.com/p/selenium/wiki/PageObjects
Page Objects – Martin Fowler - http://martinfowler.com/bliki/PageObject.html
Perils of Page-Object Pattern – Anand Bagmar -
http://essenceoftesting.blogspot.in/2014/09/perils-of-page-object-pattern.html
Protractor – https://docs.angularjs.org/guide/e2e-testing,
http://www.protractortest.org/#/
Learn Protractor for Angular – https://docs.angularjs.org/tutorial
Sample project – https://github.com/NikithaIyer/angular-phonecat-e2e
