Slides from my talk in Selenium Conference London 2016 about "Sharing (Less) Pain with Protractor & Selenium WebDriver"
See blog for more information - http://essenceoftesting.blogspot.com/2016/11/shared-relatively-less-pain-of-using.html
My blog: https://essenceoftesting.blogspot.com
This document discusses patterns for test automation frameworks. It begins by introducing common patterns like page objects, business layer, and factories. It then provides examples of page object and business layer page object patterns. The document also discusses test data patterns and different ways to specify test data and locators. Finally, it outlines advantages of using patterns like reduced complexity, reusability, and maintenance. The key message is that the best pattern depends on the specific test automation context.
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.
Visual Validation - The Missing Tip of the Automation Pyramid
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!
Here are slides from my talk on "What, Why and How of Analytics Testing" at Selenium Conference, Berlin 2017.
This talk focusses on Analytics related to Browser & Mobile Native apps, with impact on / of IoT (Internet of Things) and Big Data.
See my blog for more details - https://essenceoftesting.blogspot.com/2017/10/analytics-forgotten-child.html
Build the "right" regression suite using Behavior Driven Testing (BDT)
Behavior Driven Testing (BDT) is an evolved way of thinking about Testing. It helps in identifying the 'correct' scenarios, in form of user journeys, to build a good and effective (manual & automation) regression suite that validates the Business Goals.
Build the "right" regression suite using Behavior Driven Testing (BDT)
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"
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 my talk on how to Eradicate Flaky Tests from AppiumConf 2021
https://confengine.com/conferences/appium-conf-2021/proposal/15581/eradicate-flaky-tests
Visual Validation - The missing tip of the automation pyramid @AgileIndia2020
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.
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.
Presentation about how to use REST, Web and Mobile open source tools to increase your test codebase.
This presentation was made by me and Edson Yanaga for JavaOne 2017 San Francisco on 04/09/2017
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.
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
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.
Angularjs Protractor Training in viman nagar,just only in 8k. let's call us on 8652457999 for more information.
We have provided basic information in ppt, you can get more in training. we provide 100+ examples which make you perfect in Protractor. We also provide corporate training.
We have already provided multiple corporate training in multiple offices.
You can learn online
Database continuous integration, unit test and functional test
Discuss continuous integration for database projects, including building project, deploying project to database, and executing unit tests and functional tests.
This presentation will also discuss database test standards, tips and tricks.
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.
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.
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!
Patterns of a “good” test automation frameworkAnand Bagmar
This document discusses patterns for test automation frameworks. It begins by introducing common patterns like page objects, business layer, and factories. It then provides examples of page object and business layer page object patterns. The document also discusses test data patterns and different ways to specify test data and locators. Finally, it outlines advantages of using patterns like reduced complexity, reusability, and maintenance. The key message is that the best pattern depends on the specific test automation context.
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.
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!
The What, Why and How of Analytics TestingAnand Bagmar
Here are slides from my talk on "What, Why and How of Analytics Testing" at Selenium Conference, Berlin 2017.
This talk focusses on Analytics related to Browser & Mobile Native apps, with impact on / of IoT (Internet of Things) and Big Data.
See my blog for more details - https://essenceoftesting.blogspot.com/2017/10/analytics-forgotten-child.html
Build the "right" regression suite using Behavior Driven Testing (BDT)Anand Bagmar
Behavior Driven Testing (BDT) is an evolved way of thinking about Testing. It helps in identifying the 'correct' scenarios, in form of user journeys, to build a good and effective (manual & automation) regression suite that validates the Business Goals.
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"
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 my talk on how to Eradicate Flaky Tests from AppiumConf 2021
https://confengine.com/conferences/appium-conf-2021/proposal/15581/eradicate-flaky-tests
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.
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.
Java Test Automation for REST, Web and MobileElias Nogueira
Presentation about how to use REST, Web and Mobile open source tools to increase your test codebase.
This presentation was made by me and Edson Yanaga for JavaOne 2017 San Francisco on 04/09/2017
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.
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
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.
Angularjs Protractor Training in viman nagar,just only in 8k. let's call us on 8652457999 for more information.
We have provided basic information in ppt, you can get more in training. we provide 100+ examples which make you perfect in Protractor. We also provide corporate training.
We have already provided multiple corporate training in multiple offices.
You can learn online
Database continuous integration, unit test and functional testHarry Zheng
Discuss continuous integration for database projects, including building project, deploying project to database, and executing unit tests and functional tests.
This presentation will also discuss database test standards, tips and tricks.
Pivotal Labs Open View Presentation Quality Assurance And Developer Testingguestc8adce
1) The document discusses moving from a traditional development model where QA finds bugs after development is complete, to a model where quality is the focal point and everyone is responsible for testing.
2) It advocates for automating tests and running them frequently during development to find bugs early and have confidence in changes.
3) The goal is to develop software quickly with low defect rates by shifting left the work of finding bugs through techniques like test-driven development.
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 contains information about protractor training including understanding JavaScript and examples of protractor, setting up protractor in Eclipse, the Jasmine testing framework, and tricks and tips. It also includes sections on Angular, controllers, views, MVC patterns, Razor templating, app fabric caching, WCF, HTML5, CSS3, Bootstrap, HTTP/HTTPS requests, logging, and more.
An overview of how Pivotal Labs performs quality assurance on mobile. We have over 1300 mobile devices on all platforms - iOS, Android, Windows, BlackBerry and more. We perform automated and manual testing using various tools and methodologies to ensure a bug-free app for our clients.
Protractor is an end-to-end testing framework developed by Google for testing Angular applications. While powerful, it has some limitations including being slow to write tests for, not working well for complex user interactions, and only working optimally with Chrome. The document provides tips for writing more effective Protractor tests such as using explicit waits, avoiding direct abstraction to page objects, and handling asynchronous code carefully.
This document discusses JavaScript testing using Selenium. It recommends using Selenium 2/WebDriver for JavaScript testing as it allows direct execution of JavaScript commands and assertions of results. The key aspects of JavaScript that should be tested are DOM manipulation, event handling, network calls, and JavaScript code/state. Client-side unit testing frameworks like QUnit can be used with Selenium to execute tests and assert results. Selenium 2 aims to provide a shared browser automation API that allows launching browsers quickly and navigating/executing tests across browsers and versions.
Tracing allows you to see the path a query takes through the Cassandra cluster. It shows details like which nodes are queried, how long each step takes, and can help identify performance bottlenecks. The tracing information can be accessed via the Java driver, cqlsh, or DevCenter and provides a detailed timeline of query execution. Reviewing traces is recommended during development to catch unexpected query behavior.
Successful Software Development with Apache CassandraDataStax Academy
The document provides an overview of software development with Cassandra, including data modeling, writing code, testing, reviewing code, and managing environments. It discusses using the Java driver for writing code, preparing statements, batches, and lightweight transactions. Testing recommendations include using naming schemes, grouping tests into logical suites, and integrating unit and integration tests. The document also covers tracing queries, instrumentation with metrics, and reviewing code.
Quilt - Distributed Load Simulation from AWSAjith Jose
A distributed load testing tool to generated 100s of thousands of audio video endpoints along with all the API calls and WebSocket connections it needs!
We designed the load generation tool as a highly scalable distributed system, as it needs a lot of computing power to simulate 100K+ automated endpoints. It starts 100s of AWS/GCP instances before starting the fire. Fully automated, Get - Set - Fire !
One possible solution to ensure that your e-commerce site will not break during high-sales periods such as Black Friday or Christmas, is running JMeter distributed performance tests on Rancher.
This presentation was given during iQuest Keyboards & Mice event which took place in Craiova, Romania, on October 19th 2017.
Continous UI testing with Espresso and JenkinsSylwester Madej
Talk from Droidcon Zagreb 2015 about approach to Continous Integration and integration testing we are using in Outline.
In short: we use Jenkins CI on Intel NUC to build, analyse and test apps. To speed up tests we are using Spoon with some devices connected to our CI server via USB hub.
Comprehensive Performance Testing: From Early Dev to Live ProductionTechWell
Although the idea of doing performance testing throughout the software lifecycle sounds simple enough, as soon as you try to combine the concepts of “always testing” (in dev, pre-prod, and production) with “limited time and resources” and throw in the word “comprehensive,” the challenges can be monumental. Quickly the “how” of it emerges as the most important question—and one worth focusing on. Brad Stoner tackles this topic by explaining how he has been able to solve this seemingly impossible puzzle by applying various approaches such as early and often, learning when to say no, and seriously, I did say no—and more. Brad shares concrete examples of how he has successfully implemented full lifecycle performance testing at several companies. Join Brad to learn what performance tests to run at each development and delivery stage—from a simple load profile on a single server to full-scale soak tests over several days.
JMeter - Performance testing your webappAmit Solanki
JMeter is an open-source tool for performance and load testing web applications. It can test applications by simulating heavy loads to determine stability and identify performance bottlenecks. JMeter simulates multiple users accessing web services concurrently to model expected usage during peak periods. It provides instant visual feedback and allows tests to be run interactively or in batch mode for later analysis. Tests are composed of thread groups, samplers, timers, listeners and other elements to control test flow and capture response data. JMeter also supports distributed testing across multiple servers to simulate very large loads.
Introduction to Performance Testing & LoadrunnerAisha Mazhar
This document discusses HP LoadRunner, a performance testing tool. It provides an overview of LoadRunner, including what performance testing is, the types of performance testing, limitations of manual testing, LoadRunner components, designing and executing scenarios, and analyzing results. The key points are that LoadRunner automates performance testing by using virtual users to simulate real user loads and measure system behavior, components include VuGen, Controller, and Load Generators, and it allows designing, running, and analyzing load testing scenarios to evaluate system performance.
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.
More and more clients are looking to understand the capabilities of the OTM/G-Log architecture and configuration in order better tune OTM. Usually, this is required because of poor OTM performance or as preparation for significant changes to OTM configuration, volume, or platform. The client may be experience poor performance throughout the entire system or for a very specific use cases. The primary objective of a Performance Tuning Exercise is to understand how OTM is being utilized and to recommend solution to improve the performance of OTM.
We recommend and will take the audience through a “ground-up” performance tuning exercise, starting with hardware and infrastructure, moving to Java and App server tuning, then to OTM technical tuning and finally to the OTM functional tuning (data, agents, etc).
These audits may identify hardware constraints at each tier, networking, or other infrastructure constraints causing sub-optimal system performance. Simply stated, the performance audit will identify all bottlenecks in the system if they exist.
In many cases the largest performance is impacts are not hardware, but rather how the data is configured within the application. So as part of the exercise we will analyze database performance, individual SQL queries, OTM Queues, bulk planning parameters, agents, rates and the settlement process.
Understanding the methods which will best identify these bottlenecks will help you avoid performance issues early in your project and save considerable time and expense as you near go-live. This presentation will guide you through the steps necessary to better understand what is impacting performance and how to best handle it. It will provide lessons learned and tools that are available to you better manage and maintain a healthy OTM environment.
Presented by Chris Plough at MavenWire
The document discusses lessons learned in building robust QA infrastructure for commercial software. Key points include:
1) QA infrastructure is as important as the application itself and must be developed in parallel, not as an afterthought. QA and development teams should work closely together.
2) The build, source control, and test systems form an integrated distributed infrastructure that should allow development and testing from any location.
3) Tests should be written to easily grow over time, from simple unit tests to complex tests that export application states. An automated continuous testing system is critical.
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.
The thread dump identifies the application and JVM threads present in the JVM at the time of the dump. It provides information on each thread's state, stack trace and timing details. It also includes a summary of JVM heap utilization broken down by generation. This information can help identify potential blocking issues, performance bottlenecks or memory leaks in the application.
This document discusses code quality and testing tools from Micro Focus including DevPartner Studio, SilkTest, and Silk Central Test Manager. It summarizes the capabilities of these tools such as source code review, security scanning, debugging, performance analysis, test automation, requirements management, and deployment. The document emphasizes that these tools can help achieve better software faster through a proactive approach to continuous integration, testing, and analysis.
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.
This document discusses building automated acceptance tests that are stable and maintainable for continuous delivery. It emphasizes that developers should own acceptance testing by writing tests in the same way they write production code. This includes writing many unit and regression tests, optimizing for test execution, using immutable environments like Docker for isolation, and leveraging techniques like parallelization and separation of concerns with domain-specific languages. The document also provides examples of testing strategies, tools, and processes that can help achieve this goal.
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.
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.
The document describes the history and development of the "little Jenkinsfile" used to automate testing of the AdoptOpenJDK, OpenJ9, and Eclipse OMR projects. It outlines the principles of keeping the Jenkinsfile simple and learn from past lessons. Key aspects include testing across multiple platforms and versions, using open source tools when possible, and whole team involvement. The ecosystem now includes over 250,000 tests running on multiple servers.
Similar to Sharing (less) Pain of using Protractor & WebDriver (20)
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 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
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
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!
Test Automation - Principles and PracticesAnand Bagmar
This document discusses principles and practices for test automation. It covers topics like different levels of testing from unit to integration to UI, the importance of testing non-functional requirements, using a test pyramid approach with more unit and component tests than UI tests. It also discusses practices like continuous integration, test automation framework design considerations, sample framework architectures, and page object patterns. The overall goal is to provide guidance on building quality into software through effective test automation practices.
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
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.
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.
NBFC Software: Optimize Your Non-Banking Financial CompanyNBFC Softwares
NBFC Software: Optimize Your Non-Banking Financial Company
Enhance Your Financial Services with Comprehensive NBFC Software
NBFC software provides a complete solution for non-banking financial companies, streamlining banking and accounting functions to reduce operational costs. Our software is designed to meet the diverse needs of NBFCs, including investment banks, insurance companies, and hedge funds.
Key Features of NBFC Software:
Centralized Database: Facilitates inter-branch collaboration and smooth operations with a unified platform.
Automation: Simplifies loan lifecycle management and account maintenance, ensuring efficient delivery of financial services.
Customization: Highly customizable to fit specific business needs, offering flexibility in managing various loan types such as home loans, mortgage loans, personal loans, and more.
Security: Ensures safe and secure handling of financial transactions and sensitive data.
User-Friendly Interface: Designed to be intuitive and easy to use, reducing the learning curve for employees.
Cost-Effective: Reduces the need for additional manpower by automating tasks, making it a budget-friendly solution. Benefits of NBFC Software:
Go Paperless: Transition to a fully digital operation, eliminating offline work.
Transparency: Enables managers and executives to monitor various points of the banking process easily.
Defaulter Tracking: Helps track loan defaulters, maintaining a healthy loan management system.
Increased Accessibility: Cutting-edge technology increases the accessibility and usability of NBFC operations. Request a Demo Now!
Explore the rapid development journey of TryBoxLang, completed in just 48 hours. This session delves into the innovative process behind creating TryBoxLang, a platform designed to showcase the capabilities of BoxLang by Ortus Solutions. Discover the challenges, strategies, and outcomes of this accelerated development effort, highlighting how TryBoxLang provides a practical introduction to BoxLang's features and benefits.
A Comparative Analysis of Functional and Non-Functional Testing.pdfkalichargn70th171
A robust software testing strategy encompassing functional and non-functional testing is fundamental for development teams. These twin pillars are essential for ensuring the success of your applications. But why are they so critical?
Functional testing rigorously examines the application's processes against predefined requirements, ensuring they align seamlessly. Conversely, non-functional testing evaluates performance and reliability under load, enhancing the end-user experience.
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.
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/
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.
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 –
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.
13. CHALLENGES - JAVASCRIPT
What is Test Automation?
Synchronous,
Step-by-Step execution
ASynchronous
Callbacks & Promises!
Power of JavaScript?
14. CHALLENGES – PATH TO PRODUCTION
Local
- Mac OS
- Vagrant (Open SuSe)
CI Environment
- Build
- Unit Tests
- Integration
- End-2-End (E2E)
- Performance
Sandbox / QA
- Exploratory
- Demos
- Client-pre-setups
Production
15. 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
17. 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
22. SOLUTIONS – DETERMINISTIC TEST DATA
q Same Test Data in all environments / tenants
q Minimal Environment specific configuration
q Intelligent ‘before’ & ‘after’ setups
23. SOLUTIONS – UTILITIES
Page functions
- Common behavior
- Non-angular
Screenshots with
counters, per spec
Unique output directory
names
JS Console warnings &
errors Map & Chart functions
CSV, Zip file loader
Modals & Alerts
File Upload
File Download
Head & Head-less
execution
Configurations
25. DID WE SOLVE ALL THE PROBLEMS?
JUST KIDDING!!! - Of course, NO!!
- Maps, Use Soft-asserts (intelligently), phantomJS
- Quick(er) root-cause analysis
- Reports
- Easier debugging
- How many and where to put “assertions”?
- Faster test execution
- Parallel Test execution
- Implement View tests (html specs)
YES!!!
26. 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
q Evolve
26
27. 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
