Enabling CD in Enterprises with Testing
12 likes4,179 views
The key objectives of Organizations is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality! In such a fast moving environment, CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury! There are various practices that Organizations and Enterprises need to implement to enable CD. Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful. Testing in Organizations on the CD journey is tricky and requires a lot of discipline, rigor and hard work. In Enterprises, the Testing complexity and challenges increase exponentially. I am sharing my vision of the Test Vision and Strategy required to make successful the journey of an Enterprise on the path of implementing CD. Learn via a case study of an Enterprise, what does CD really means, and how and what Testing needs to be done in order to enable CD.
1 of 38
Downloaded 70 times
Ad
Recommended
To Deploy or Not-To-Deploy - decide using TTA's Trend & Failure Analysis
To Deploy or Not-To-Deploy - decide using TTA's Trend & Failure AnalysisAnand Bagmar Here are the slides from my recent talks on "To Deploy or Not-To-Deploy - decide using TTA's Trend and Failure Analysis"
More information available from my blog:
http://essenceoftesting.blogspot.com/search/label/tta
Patterns in Test Automation
Patterns in Test AutomationAnand Bagmar 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!
Say NO To (More) Selenium Tests
Say NO To (More) Selenium TestsAnand Bagmar 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 Framework
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!
Agile Testing Dilemmas
Agile Testing DilemmasAman King Based on hands-on Agile experience acquired over multiple delivery projects and Agile coaching/consulting assignments, Vatsala and Aman share common Agile Testing dilemmas, and possible solutions, tying them to the principle of "moving testing upstream".
Presented at Next Generation Testing conference in Bangalore, India (July 2014).
Patterns of a “good” test automation framework
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.
Perils of Page-Object Pattern
Perils of Page-Object PatternAnand Bagmar 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.
What is Agile Testing? How does Automation help?
What is Agile Testing? How does Automation help?Anand Bagmar Agile Methodology is not new. Many organisations / teams have already adopted Agile way of Software Development or are in the enablement journey for the same.
What does this mean for Testing? There is no doubt that the Testing approach and mindset also needs to change to be in tune with the Agile Development methodology.
Learn what does it mean to Test on Agile Projects. Also, learn how Test Automation approach needs to change for the team to be successful!
Also, see the skills and capabilities required to make anyone in the Quality / Testing role add tremendous value to the team!
Client-Side Performance Testing
Client-Side Performance TestingAnand Bagmar 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.
Build the "right" regression suite using Behavior Driven Testing (BDT)
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.
An easy way to automate complex UI
An easy way to automate complex UIIvan Pashko This talk is a brief overview of how we deal with UI test architecture on our project. Complex backend, SPA as a frontend, 20+ different brands and 100+ features for each, more and more code.
We will discuss:
– fakes and test doubles, approaches how to build and maintain them;
– development patterns, which help you to make your architecture more simple, stable and readable;
– tips and tricks – how to make your life with UI tests easier.
Software Test Patterns: Successes and Challenges
Software Test Patterns: Successes and ChallengesBob Binder This document discusses the successes and challenges of using test patterns over the past 10 years. It describes how test patterns were useful for articulating testing insights and practices, but have not been widely adopted. Reasons for limited adoption include the proliferation of templates, confusion between different pattern types, and the perception that using patterns requires too much additional modeling effort. The document also suggests that while innovators create new patterns, those seeking existing patterns may be less influential. It argues that test patterns will remain important for building a conceptual framework for testing and efficiently sharing solutions, especially as software systems increase in complexity.
Build the "right" regression suite using Behavior Driven Testing (BDT)
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"
Future of Testing, Test Automation and The Quality Analyst
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)
Integration Testing in Enterprises using TaaS
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.
VodQA3_ATDD_KetanSoni
VodQA3_ATDD_KetanSonivodQA This was a full length talk presented by Ketan Soni in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
Visual Validation - The Missing Tip of the Automation Pyramid
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!
Enabling CD in Enterprises with Testing
Enabling CD in Enterprises with TestingAnand Bagmar Slides from my talk in Agile India 2015, Discuss Agile 2015 on "Enabling Continuous Delivery (CD) in Enterprises with Testing"
Grading the Quality of Selenium Tests
Grading the Quality of Selenium TestsMarcus Merrell This document discusses how to evaluate and improve Selenium tests, page objects, and locators. It provides rubrics to grade tests on a 100 point scale, deducting points for issues like using Selenium commands directly or hard-coded waits. Page objects are graded on lines of code, assertions, and waits. Locators are given letter grades based on attributes like being dynamic, tied to layout, or using semantic IDs. An example shows overall grades for a test suite, individual tests, and locators within tests. The document concludes by proposing implementing the rubrics as an IntelliJ plugin to automate evaluation and reporting.
Test automation - What? Why? How?
Test automation - What? Why? How?Anand Bagmar This document discusses test automation in agile projects. It begins with an overview of agile principles like the agile manifesto. It then discusses agile testing principles and practices like continuous integration and continuous delivery. The bulk of the document focuses on test automation, including why it's important, different types of test automation frameworks, and design considerations like the test automation pyramid. It provides tips for test automation including design patterns, abstraction layers, and evolving the framework over time.
Test Automation Architecture in Microservices
Test Automation Architecture in MicroservicesAlper Mermer Tips and tricks on implementing a successful test automation architecture in a Microservices environment.
Eradicate Flaky Tests - AppiumConf 2021
Eradicate Flaky Tests - AppiumConf 2021Anand Bagmar 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
Roman iovlev battle - JDI vs Selenide - Selenium Camp
Roman iovlev battle - JDI vs Selenide - Selenium CampРоман Иовлев The Battle on Selenium Camp conferece February 2017
http://seleniumcamp.com/talk/qa-livecoding-battle-typed-element-framework-jdi-vs-untyped-elements-framework-selenide/
Why typed elements (like Buttons, Images, Checkboxes, Links etc.) are bad practice in UI tests? Or are non-typed elements (like SelenideElement for ´em all!) more evil? Is it better to have predefined Element hierarchy or not?
Alexei and Roman have delivered a sound theoretical battle earlier at Heisenbug-2016 Conference in Moscow. But were everything said just words? The both QA wrestlers are still standing behind their concepts and are willing to prove their point at live coding sessions before the judging audience! In this QA Battle the parties will solve problems using a typed framework JDI and an non-typed one – Selenide, commenting their actions. The audience will decide with their votes which of the concept was better.
How to scale your Test Automation
How to scale your Test AutomationKlaus Salchner Learn how you can use the Test Pyramid from Mike Cohn to guide how to scale your QA test automation while keeping it effective and fast. As your product and team scales it is really important to have a solid framework in place which allows your test automation to scale for the various layers of your product and your teams.
Reaching for Your Quality Stretch Goals: Testing at Realtor.com
Reaching for Your Quality Stretch Goals: Testing at Realtor.comKlaus Salchner A/B Testing
If you are not familiar yet, an introduction to A/B testing and how you can leverage this approach to truly measure customer impact before and after a change. It's a practice highly leveraged in the e-commerce and cloud space to truly measure the impact of a change and be able to iterate through it till you see the desired outcome.
Where in your stack to invest in test automation
This short talk will explain in which layer to invest in test automation and the pros and cons. Too many teams still invest heavily in automated UI testing which then results in large test automation suites once the platform grows while still not being able to catch critical quality issues before they reach customers.
Testing for reliability, resilience and recovery
Your customer experience is also impacted by how reliable your application is. How do you test for reliability. But also how do you build and test for resilience, as guaranteed reliability is unachievable and the closer you get the costlier it becomes. Lastly how do you test for recovery, so once an outage or partial outage happened how to you recover, and how do you prepare for that recovery.
Test Automation Architecture That Works by Bhupesh Dahal
Test Automation Architecture That Works by Bhupesh DahalQA or the Highway The document discusses test automation architecture and provides recommendations for building an effective architecture. It recommends prioritizing unit testing and API/service layer testing over GUI testing to create a testing pyramid. Unit tests should be isolated and test small pieces of code, while API tests can test application logic through service calls. GUI tests should be limited in number and used to test broad end-to-end scenarios, not every small scenario. The goal is to have fewer, more stable automated tests rather than many fragile tests. Following best practices like testing different layers, prioritizing types of tests, and continuous refactoring can help create a maintainable and effective test automation architecture.
Design patterns in test automation
Design patterns in test automationMikalai Alimenkou Design patters exist for years in software development. Some developers love them, some think they are useless. But design patters has very clear goals: describe common solutions for common problems, create shared language for community, improve understanding and reuse of existing approaches. Test automation has its own set of problems, so there is a set of helpful design patterns for this area. In this talk I will run through all known patterns and describe them in details with several practical samples.
Inverting The Testing Pyramid
Inverting The Testing PyramidNaresh Jain As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.
One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.
How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?
Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.
This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.
In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.
The what why and how of web analytics testing
The what why and how of web analytics testingVodqaBLR This document discusses web analytics testing and the opportunities in testing IoT and big data solutions. It provides an overview of web analytics, why testing is needed, and common web analytics solutions like Google Analytics. It then describes challenges with manual testing and introduces WAAT (Web Analytics Automation Testing) as a solution to automate testing. WAAT supports various plugins and has Java and Ruby implementations. The document concludes by discussing how IoT and big data are generating large amounts of data and new opportunities for testing to validate data collection, analysis, and optimization of business value.
Test automation_strategy_for_legacysystems
Test automation_strategy_for_legacysystemsVodqaBLR The document discusses strategies for test automation of legacy systems. It begins by outlining some of the challenges of legacy systems, including a lack of agile testing mindset, unclear requirements, and lack of technical skills. It then covers components of a full test automation puzzle like clarity on user stories, distinguishing test types/levels, and testing infrastructure. Specific strategies discussed include applying the Agile Testing Pyramid, refactoring code using the shortest branch technique or strangulation pattern, and taking a bottom-up testing approach.
Ad
More Related Content
What's hot (19)
Client-Side Performance Testing
Client-Side Performance TestingAnand Bagmar 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.
Build the "right" regression suite using Behavior Driven Testing (BDT)
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.
An easy way to automate complex UI
An easy way to automate complex UIIvan Pashko This talk is a brief overview of how we deal with UI test architecture on our project. Complex backend, SPA as a frontend, 20+ different brands and 100+ features for each, more and more code.
We will discuss:
– fakes and test doubles, approaches how to build and maintain them;
– development patterns, which help you to make your architecture more simple, stable and readable;
– tips and tricks – how to make your life with UI tests easier.
Software Test Patterns: Successes and Challenges
Software Test Patterns: Successes and ChallengesBob Binder This document discusses the successes and challenges of using test patterns over the past 10 years. It describes how test patterns were useful for articulating testing insights and practices, but have not been widely adopted. Reasons for limited adoption include the proliferation of templates, confusion between different pattern types, and the perception that using patterns requires too much additional modeling effort. The document also suggests that while innovators create new patterns, those seeking existing patterns may be less influential. It argues that test patterns will remain important for building a conceptual framework for testing and efficiently sharing solutions, especially as software systems increase in complexity.
Build the "right" regression suite using Behavior Driven Testing (BDT)
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"
Future of Testing, Test Automation and The Quality Analyst
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)
Integration Testing in Enterprises using TaaS
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.
VodQA3_ATDD_KetanSoni
VodQA3_ATDD_KetanSonivodQA This was a full length talk presented by Ketan Soni in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
Visual Validation - The Missing Tip of the Automation Pyramid
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!
Enabling CD in Enterprises with Testing
Enabling CD in Enterprises with TestingAnand Bagmar Slides from my talk in Agile India 2015, Discuss Agile 2015 on "Enabling Continuous Delivery (CD) in Enterprises with Testing"
Grading the Quality of Selenium Tests
Grading the Quality of Selenium TestsMarcus Merrell This document discusses how to evaluate and improve Selenium tests, page objects, and locators. It provides rubrics to grade tests on a 100 point scale, deducting points for issues like using Selenium commands directly or hard-coded waits. Page objects are graded on lines of code, assertions, and waits. Locators are given letter grades based on attributes like being dynamic, tied to layout, or using semantic IDs. An example shows overall grades for a test suite, individual tests, and locators within tests. The document concludes by proposing implementing the rubrics as an IntelliJ plugin to automate evaluation and reporting.
Test automation - What? Why? How?
Test automation - What? Why? How?Anand Bagmar This document discusses test automation in agile projects. It begins with an overview of agile principles like the agile manifesto. It then discusses agile testing principles and practices like continuous integration and continuous delivery. The bulk of the document focuses on test automation, including why it's important, different types of test automation frameworks, and design considerations like the test automation pyramid. It provides tips for test automation including design patterns, abstraction layers, and evolving the framework over time.
Test Automation Architecture in Microservices
Test Automation Architecture in MicroservicesAlper Mermer Tips and tricks on implementing a successful test automation architecture in a Microservices environment.
Eradicate Flaky Tests - AppiumConf 2021
Eradicate Flaky Tests - AppiumConf 2021Anand Bagmar 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
Roman iovlev battle - JDI vs Selenide - Selenium Camp
Roman iovlev battle - JDI vs Selenide - Selenium CampРоман Иовлев The Battle on Selenium Camp conferece February 2017
http://seleniumcamp.com/talk/qa-livecoding-battle-typed-element-framework-jdi-vs-untyped-elements-framework-selenide/
Why typed elements (like Buttons, Images, Checkboxes, Links etc.) are bad practice in UI tests? Or are non-typed elements (like SelenideElement for ´em all!) more evil? Is it better to have predefined Element hierarchy or not?
Alexei and Roman have delivered a sound theoretical battle earlier at Heisenbug-2016 Conference in Moscow. But were everything said just words? The both QA wrestlers are still standing behind their concepts and are willing to prove their point at live coding sessions before the judging audience! In this QA Battle the parties will solve problems using a typed framework JDI and an non-typed one – Selenide, commenting their actions. The audience will decide with their votes which of the concept was better.
How to scale your Test Automation
How to scale your Test AutomationKlaus Salchner Learn how you can use the Test Pyramid from Mike Cohn to guide how to scale your QA test automation while keeping it effective and fast. As your product and team scales it is really important to have a solid framework in place which allows your test automation to scale for the various layers of your product and your teams.
Reaching for Your Quality Stretch Goals: Testing at Realtor.com
Reaching for Your Quality Stretch Goals: Testing at Realtor.comKlaus Salchner A/B Testing
If you are not familiar yet, an introduction to A/B testing and how you can leverage this approach to truly measure customer impact before and after a change. It's a practice highly leveraged in the e-commerce and cloud space to truly measure the impact of a change and be able to iterate through it till you see the desired outcome.
Where in your stack to invest in test automation
This short talk will explain in which layer to invest in test automation and the pros and cons. Too many teams still invest heavily in automated UI testing which then results in large test automation suites once the platform grows while still not being able to catch critical quality issues before they reach customers.
Testing for reliability, resilience and recovery
Your customer experience is also impacted by how reliable your application is. How do you test for reliability. But also how do you build and test for resilience, as guaranteed reliability is unachievable and the closer you get the costlier it becomes. Lastly how do you test for recovery, so once an outage or partial outage happened how to you recover, and how do you prepare for that recovery.
Test Automation Architecture That Works by Bhupesh Dahal
Test Automation Architecture That Works by Bhupesh DahalQA or the Highway The document discusses test automation architecture and provides recommendations for building an effective architecture. It recommends prioritizing unit testing and API/service layer testing over GUI testing to create a testing pyramid. Unit tests should be isolated and test small pieces of code, while API tests can test application logic through service calls. GUI tests should be limited in number and used to test broad end-to-end scenarios, not every small scenario. The goal is to have fewer, more stable automated tests rather than many fragile tests. Following best practices like testing different layers, prioritizing types of tests, and continuous refactoring can help create a maintainable and effective test automation architecture.
Design patterns in test automation
Design patterns in test automationMikalai Alimenkou Design patters exist for years in software development. Some developers love them, some think they are useless. But design patters has very clear goals: describe common solutions for common problems, create shared language for community, improve understanding and reuse of existing approaches. Test automation has its own set of problems, so there is a set of helpful design patterns for this area. In this talk I will run through all known patterns and describe them in details with several practical samples.
Viewers also liked (14)
Inverting The Testing Pyramid
Inverting The Testing PyramidNaresh Jain As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.
One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.
How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?
Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.
This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.
In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.
The what why and how of web analytics testing
The what why and how of web analytics testingVodqaBLR This document discusses web analytics testing and the opportunities in testing IoT and big data solutions. It provides an overview of web analytics, why testing is needed, and common web analytics solutions like Google Analytics. It then describes challenges with manual testing and introduces WAAT (Web Analytics Automation Testing) as a solution to automate testing. WAAT supports various plugins and has Java and Ruby implementations. The document concludes by discussing how IoT and big data are generating large amounts of data and new opportunities for testing to validate data collection, analysis, and optimization of business value.
Test automation_strategy_for_legacysystems
Test automation_strategy_for_legacysystemsVodqaBLR The document discusses strategies for test automation of legacy systems. It begins by outlining some of the challenges of legacy systems, including a lack of agile testing mindset, unclear requirements, and lack of technical skills. It then covers components of a full test automation puzzle like clarity on user stories, distinguishing test types/levels, and testing infrastructure. Specific strategies discussed include applying the Agile Testing Pyramid, refactoring code using the shortest branch technique or strangulation pattern, and taking a bottom-up testing approach.
Winning strategies in Test Automation
Winning strategies in Test AutomationXBOSoft Barely any modern software development project will be initiated without the discussion on test automation. With the demand to deliver software products in higher quality faster, test automation is oftentimes perceived by project leads as the silver bullet, allowing to ‘test everything’ without high overhead in employing skilled workforce. The tools are being discussed more often, than development and maintenance costs of automation frameworks that can support projects from inception into delivery and post-production.
Incorrect approaches that result in choosing invalid test automation strategies are often the cause of much frustration later in the project, when the reality of test automation activities become visible and need to be accounted for.
In this webinar, Anna will discuss her experiences in selecting short term and long term test automation strategies applied within various contexts, various skill sets that are required for running a successful test automation project, and suggest alternatives to full-blown test automation with the insufficient project resources.
Learn:
* when the test automation is an enabler, and when it’s an impediment to project success
* when to start planning for automation, and how to select the tools and methods most suitable for specific project needs
* how to anticipate investment costs and support long term automation effort across multiple projects
* skills and roles in test automation
Gauge from an end user's perspective-fathima harris
Gauge from an end user's perspective-fathima harrisVodqaBLR Gauge is a lightweight cross-platform test automation tool that allows writing test cases in a business-friendly language. It has a minimal learning curve and supports features like specifications, scenarios, steps, data tables, parallel execution, continuous integration, and an active developer community. The document discusses Gauge terminology, syntax, and provides an overall positive experience of using Gauge for its ease of use, language independence, and quick response to issues.
Building a Pyramid: Symfony Testing Strategies
Building a Pyramid: Symfony Testing StrategiesCiaranMcNulty The last few years have seen a huge adoption of testing practices, and an explosion of different testing tools, in the PHP space. The difficulties come when we have to choose which tools to use, in what combinations, and how to apply them to existing codebases.
In this talk we will look at what tools are available, what their strengths are, how to decide which set of tools to use for new or legacy projects, and when to prioritise decoupling and testability over the convenience we get from our frameworks.
Anti-patterns in Your Test coverage
Anti-patterns in Your Test coverageGayathri Mohan Quick overview of your project may end up in one of these anti-patterns when trying to achieve your ideal test pyramid
10 things about BDD, Cucumber and SpecFlow - Long Version 2016
10 things about BDD, Cucumber and SpecFlow - Long Version 2016Seb Rose SpecFlow is quite a recent addition to the software development toolbox. Sometimes it feels like we’re using a hammer to drive in a screw, so in this session we’ll explore what it’s good for and when to use it. We’ll also look at what problems it doesn’t help with and when not to use it.
As you might expect, I’m a huge fan of using SpecFlow, as part of a well thought out approach to Behaviour Driven Development (BDD) or Specification By Example (SBE). I’ve also seen the pain of organisations who have tried using SpecFlow from a pure test automation perspective, and this is one of the misapplications that we’ll talk about.
We’ll look at a further 9 specific, actionable recommendations for using SpecFlow well, including how to write maintainable executable specifications, organising large suites of specifications in an accessible way, and where SpecFlow fits into an Agile development process.
By the end of this session you’ll know enough to decide whether your problems are more like a screw or a nail – and whether SpecFlow is the right tool.
Headless BDD
Headless BDDShashikant Jagtap This talk has been delivered at London Tester Gathering #TesterGathering on 26 June, 2013. This talk was all about demo of Behat and Cucumber with headless drivers Zombie and PhantomJS (Poltergeist).
Event Url : http://www.meetup.com/agiletesting/events/123049092/
BDD: Telling stories through code [For TechNotts]![BDD: Telling stories through code [For TechNotts]](https://cdn.slidesharecdn.com/ss_thumbnails/bdd-fromstorytocodefortechnotts-160105000630-thumbnail.jpg?width=560&fit=bounds)
BDD: Telling stories through code [For TechNotts]Matt Brunt Stories? Scenarios? BDD? Are these just more words in the ever-growing list of jargon that developers have to know? Or are they something more important than new terms to memorise?
In this session we'll look at how BDD fits into the software development work-flow, how to tell user stories through features, and what makes a good feature file.
These techniques will help to ensure you're writing well designed and tested software that focuses on what the users really want from a system.
Test Automation in Business and Enterprise Digital Strategies
Test Automation in Business and Enterprise Digital StrategiesWorksoft The document discusses automation in digital strategy and test automation. It provides an overview of when and how to automate, as well as the business benefits of test automation. An example is given of Metso's test automation project using Worksoft Certify and SAP Solution Manager, which automated 135 end-to-end processes. Metso achieved cost savings and improved release schedules through increased testing frequency and reduced manual testing hours. Test automation was also beneficial for Metso's SAP HANA migration project.
Role of Automation in Testing
Role of Automation in TestingAnand Bagmar Slides explaining the Agile process, and how Test Automation plays a key role in enabling teams to be successful in this fast moving process.
rock-solid TYPO3 development with continuous integration and deployment
rock-solid TYPO3 development with continuous integration and deploymentAOE Shows our best practices of TYPO3 deployment and how these should be integrated in your development workflow. Highlights some of the most recent technologies and how AOE GmbH integrates them towards a smooth and quick rollout of web applications.
Build the ‘Right’ Regression Suite using Behavior Driven Testing (BDT)
Build the ‘Right’ Regression Suite using Behavior Driven Testing (BDT)Thoughtworks The document discusses using behavior driven testing (BDT) to build an effective regression test suite. It describes challenges with existing testing including brittle, outdated tests. BDT involves identifying business flows and prioritizing them to determine which should be automated. Top flows are automated using BDD tools or programming languages. This provides executable specifications, removes ambiguity, and allows testing in sync with product functionality.
Ad
Similar to Enabling CD in Enterprises with Testing (20)
Enabling CD in Enterprises with Testing - Anand Bagmar
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.
Service pemanas air solahart hp 081313462267
Service pemanas air solahart hp 081313462267Service Solahart 081313462267 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
Test Automation - Principles and Practices
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.
Test Automation: Investment Today Pays Back Tomorrow
Test Automation: Investment Today Pays Back TomorrowTechWell Al Wagner from IBM presented on the topic of "Test Automation: Investment today pays back tomorrow". The presentation discussed how test automation is an investment that can reduce testing time and costs. It emphasized that test automation requires planning, resources, and maintenance similar to a software development project. The presentation provided examples of how organizations were able to significantly reduce testing cycles and costs through implementing test automation and service virtualization strategies.
The Automation Firehose: Be Strategic & Tactical With Your Mobile & Web Testing
The Automation Firehose: Be Strategic & Tactical With Your Mobile & Web TestingPerfecto by Perforce The document discusses strategies for effective test automation. It emphasizes taking a risk-based approach to prioritize what to automate based on factors like frequency of use, complexity of setup, and business impact. The document outlines approaches for test automation frameworks, coding standards, and addressing common challenges like technical debt. It provides examples of metrics to measure the effectiveness of test automation efforts.
Encontrando la Aguja en el Rendimiento de Aplicaciones
Encontrando la Aguja en el Rendimiento de AplicacionesSoftware Guru En ocasiones resulta complicado entregar alta calidad de software con la velocidad que el mercado requiere. La propuesta de DevOps es mas allá de una metodología, un cambio cultural en la forma en que funcionan los equipos tanto de operación como de desarrollo, buscando aportar valor para la empresa mediante mejoras en el ciclo de vida de desarrollo y buscando un rendimiento optimo de las aplicaciones mediante herramientas tanto en la fase de desarrollo como de operación.
Pete Marshall - casmadrid2015 - Continuous Delivery in Legacy Environments
Pete Marshall - casmadrid2015 - Continuous Delivery in Legacy EnvironmentsPeter Marshall This document discusses practices for implementing continuous delivery in legacy software environments. It outlines key characteristics of continuous delivery like keeping software deployable throughout its lifecycle. It then provides examples of how one company transitioned their monolithic legacy application to a continuous delivery model by using techniques like the strangler pattern, refactoring to separate concerns, and restructuring their organization into cross-functional product teams. The document emphasizes establishing technical foundations, learning through the build-deploy-learn cycle, and focusing on delivering value to customers.
Lightning Talks by Globant - Automation (This app runs by itself ) 
Lightning Talks by Globant - Automation (This app runs by itself ) Globant When you add new features to your application a lot of things can happen. Do you believe that the app is able to test itself by using automation? Just imagine testing everything manually due to that change. Do you know how many people will be needed to complete this process? The power of automated testing in the development lifecycle allows us things such as scheduling, and executing tests at any time with a big scope on thousands of mobile devices, websites and multiple browsers simultaneously making sure everything is working as expected.
Agile testing
Agile testingRaj Indugula Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
Testing in agile
Testing in agileAndrei Metelski The document discusses testing approaches in Agile development. It outlines Agile core values like prioritizing working software over documentation. It compares the Agile Testing Pyramid model which emphasizes more lightweight unit and integration testing over manual UI testing to the traditional Testing Ice Cream Cone model. It also discusses the Agile Test Quadrants framework and how test automation fits into Agile at different levels including unit, integration/service, and UI testing while maintaining a balance between development and testing. The document provides recommendations for test automation in Agile like starting small and incrementally, balancing automation costs and ROI, and keeping feedback cycles quick.
The Automation Firehose: Be Strategic and Tactical by Thomas Haver
The Automation Firehose: Be Strategic and Tactical by Thomas HaverQA or the Highway The document discusses strategies for automating software testing. It emphasizes taking a risk-based approach to determine what to automate based on factors like frequency of use, complexity, and legal risk. The document provides recommendations for test automation best practices like treating automated test code like development code, using frameworks and tools to standardize coding practices, and prioritizing unit and integration testing over UI testing. It also discusses challenges that can arise with test automation like flaky tests, long test execution times, and keeping automation in sync with changing software. Metrics for measuring the effectiveness of test automation are presented, like test coverage, defect findings and trends, and time savings.
Mastering QA Automation_ From Strategy to Execution.pdf
Mastering QA Automation_ From Strategy to Execution.pdfronikakashyap1 QA test automation helps validate app functionality, simulate user flows, confirm integrations, and catch regressions early, improving accuracy and efficiency in the development process
Dev ops culture and practices
Dev ops culture and practicesAnkaraCloud Ankara Cloud Meetup 5. event from Opsgenie Sezgin Küçükkaraaslan about DevOps Culture And Practices
Discover the power of QA automation testing
Discover the power of QA automation testingSoftweb Solutions Automation testing is achieved by using automation tools to define and execute test cases without any manual input during the testing process.
Test Like A Badger
Test Like A BadgerMichael Badger The document provides guidance on establishing an effective testing strategy that utilizes both manual and automated testing. It advocates that manual testing is time-consuming and reduces productivity and confidence, while automated testing improves maintenance, feedback, and regression when implemented properly. The key steps outlined are gaining stakeholder buy-in, building quality into the process, focusing initial automation on builds and unit tests, adding integration and acceptance testing, and establishing visibility and accountability measures.
Continuous delivery
Continuous deliveryMasas Dani This document discusses several anti-patterns related to manual software deployments including extensive documentation, reliance on manual testing, unpredictable releases, and lack of collaboration between development and operations teams. It advocates for automating deployments to make them repeatable and frequent in order to reduce risk and provide quick feedback. Continuous delivery of software through practices like blue-green deployments and canary releases is recommended to satisfy customers.
Quality attributes testing. From Architecture to test acceptance
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.
Future of QA
Future of QAamitagarwal2006 The document discusses predictions for the future of testing and QA. It predicts that test automation will significantly increase from 31% currently to become a major part of the QA process. It also predicts that testing responsibilities will move earlier in the development cycle, with more testing by developers and end users. Requirements testing will also improve with automation and new technologies that provide 100% test coverage and automatically generate test cases.
Futureofqa
Futureofqaamitagarwal2006 The document discusses predictions for the future of testing and QA. It predicts that test automation will significantly increase from 31% currently to become a major part of the QA process. It also predicts that testing responsibilities will move earlier in the development cycle, with more testing by developers and end users. Requirements testing will also improve with automation and new technologies that provide 100% test coverage and automatically generate test cases.
Thomas Haver - Mobile Testing.pdf
Thomas Haver - Mobile Testing.pdfQA or the Highway Thomas Haver is an ex-scientist and ex-baker who hates sand. M&T Bank needed a better way to test their mobile banking apps and ensure a good user experience. They lacked centralized testing practices and resources. Perfecto was selected as their primary mobile testing tool to help standardize practices and provide metrics. The manual testing features would help train teams, but automation capabilities were also important for maturity.
Ad
More from Thoughtworks (20)
Design System as a Product
Design System as a ProductThoughtworks Design System as a Product - Maria Elena Duenias, Esther Butcher
Design systems are a great example where web development and design meet. You can find innumerable resources on the internet, books and conferences on how to build them, and how they are exactly what your organization needs. But, building one requires a lot more than following a recipe. In this talk we are going to discuss how to build a design system as an internal product, and how it evolves to become what the users need.
Designers, Developers & Dogs
Designers, Developers & DogsThoughtworks Designers, Developers and Dogs: Finding the magic balance between product and tech - Charlotte Vorbeck, ShareNow and Sahil Bajaj
How can an agile delivery team become a successful product team? When does collaboration between product and tech succeed and when not? Why do people in some teams inspire each other while others in the same environment don't speak the same language? In this talk we want to share our learnings and experiences from rebuilding an internal tool for customer support at ShareNow. What could have been just another boring rewrite surprisingly became one of our best experiences in collaboration. We will look at how a joint discovery phase helped us to come up with a shared vision, how a better team setup enabled us to do the necessary work, how focusing on the customer kept us aligned during our journey, and also how we built upon existing collaborative techniques to achieve this new level of cooperation and trust.
Cloud-first for fast innovation
Cloud-first for fast innovationThoughtworks During this presentation, Ward Coessens, ThoughtWorks' Consultant will share best practice insights from the Daimler partnership, helping the automotive group on their cloud innovation journey.
More impact with flexible teams
More impact with flexible teamsThoughtworks How to create more business impact with flexible teams - Jan Hegewald, Zalando & Rebekka Beels, Zalando
Usually, Software Engineering teams are organized around a fixed set of components which they develop further and maintain. Such component teams gain a high level of expert knowledge about their services. However, with agile product development, it often is difficult to implement the most important initiatives with such teams. This leads to a situation where the teams do not work on the most relevant business topics but on those for the respective team. At Zalando, we introduced a new model where we shape teams flexibly around business goals to create the highest impact. How we organize these teams and which challenges especially for the software quality need to be addressed, will be explored in this talk.
Culture of Innovation
Culture of InnovationThoughtworks Amazon’s Culture of Innovation & The Working Backwards session
Working Backwards; leading organisations achieve growth by marrying customer-obsession with a modern technology strategy. Where do you begin? By focusing on the customer.
During this webinar, Amazon will discuss key innovation principles which have been instrumental in their continued success and their Working Backwards approach.
Dual-Track Agile
Dual-Track AgileThoughtworks Dual-Track Agile for Discovery & Development - Adriana Katrandzhieva
The talk will focus on one of the ways teams can ensure continuous delivery and design in their projects. The so-called ‘Dual-track’ model shows the parallel tracks of discovery and development throughout the product design and delivery process. These continually feedback into each other informing new hypothesis that can be tested in order to be proven/disproven. This model is not always easy to implement out of the box and so I will share my own experiences in applying it in practice - what worked, what didn't and how the model can be adjusted to fit different teams and organisational environments.
Developer Experience
Developer ExperienceThoughtworks This document discusses developer experience (DX) and how to design for it. It begins with introductions of the presenters and defines DX as the experience developers have when using a product. It then discusses understanding developer pain points and personas, designing the developer journey, and using different interfaces like APIs, portals, and CLIs. The document outlines challenges in the design process like getting buy-in and measuring DX metrics. It argues that improving DX benefits business goals like enabling experiments, increasing flexibility, and attracting talent. It concludes that developers are also users and designers, and that DX is important to consider for business reasons.
When we design together
When we design togetherThoughtworks When we design together - Sabrina Mach, Ammara Gafoor and James Emmott
From three distinct perspectives, this talk will contend that design is an activity undertaken by everyone in a software development team. It occurs throughout the process of delivery — not only at the beginning or the end — and it is a powerful instrument for learning about and adapting to the problems our work seeks to solve, which is a shared responsibility. Making the best use of our multidisciplinary expertise in the activity of design requires forms of collaboration that are too often disrupted by the role-based silos that keep us separated and weaken the valuable contribution our diverse approaches could make to our collective efforts. If you care about accelerating time to market, improving customer experience, or building happy and productive teams, you will want to know why and how it matters that we believe ‘design is in everything that we do’.
Hardware is hard(er)
Hardware is hard(er)Thoughtworks Hardware is hard(er): designing for distributed user experiences in IoT - Claire Rowland, www.clairerowland.com
Designing connected devices and hardware-enabled services is significantly more complex than pure software. There are more devices on which code can run, connectivity and data sharing patterns to consider, and often multiple and varied touchpoints for users to interact with. Pulling this all together into a coherent experience involves strong collaboration between design and engineering, and a systems thinking approach to UX. In this talk, we’ll introduce what designers need to know about the tech, what engineers need to know about UX for IoT, and how to facilitate the whole-collaboration needed to create great products.
www.clairerowland.com
Customer-centric innovation enabled by cloud
Customer-centric innovation enabled by cloudThoughtworks Working Backwards - Leading organisations achieve growth by marrying customer-obsession with a modern technology strategy. In this upcoming webinar, we’ve partnered with AWS to bring you exclusive insights from one of the world’s most innovative companies, Amazon.
Amazon's Culture of Innovation
Amazon's Culture of InnovationThoughtworks The document discusses Amazon's culture of innovation. It emphasizes starting with the customer and working backwards to develop solutions. Amazon focuses on small, autonomous teams that are nimble and own their work. The company's leadership principles guide decision-making and encourage inventiveness, customer obsession, high standards, and long-term thinking to solve customer problems.
When in doubt, go live
When in doubt, go liveThoughtworks The document discusses techniques for establishing shorter feedback loops between developing features and measuring user behavior, including:
1) Shadow traffic which runs new and old features simultaneously to get early feedback without users noticing a difference.
2) Visual reports which assess the quality of a feature through a report (e.g. HTML page) of key metrics.
3) A/B testing which statistically compares user behavior between a control and test group after exposing each to a different variant of a feature. Sample size considerations and statistical significance are discussed.
Don't cross the Rubicon
Don't cross the RubiconThoughtworks As a tech leader at ThoughtWorks, a large part of my job involves recommending practices to our clients so they can build and deliver good quality software faster. In doing so repeatedly for many clients I have created a toolkit that contains practical advice from being on the ground. This is what we do, we know it works. When Julius Caesar entered Rome with his army by crossing the river Rubicon, he did something that couldn’t be undone ever again. In your journey as a leader, avoid mistakes that are difficult to correct later. Here are a set of practices that you want to adopt as soon as possible.
Error handling
Error handlingThoughtworks Handling error conditions is a core part of the software we write. However, we often treat it as a second class citizen, obscuring our intent through abuse of null values and exceptions that make our code hard to understand and maintain. In the functional programming community, it is common to use datatypes such as Option, Either or Validated to make our intentions explicit when dealing with errors. We can leverage the compiler to verify that we are handling them instead of hoping for the best at runtime. This results in code that is clearer, without hidden path flows. We’ll show how we have been doing this in Kotlin, with the help of the Arrow library.
Your test coverage is a lie!
Your test coverage is a lie!Thoughtworks Mutation testing in software development surfaced in academia during the 70's and has recently seen a resurgence in popularity as a legitimate tool in your testing arsenal. In this session we review the conventional testing pyramid, modern approaches to testing software and look at how mutation testing can help fill in those blind spots.
Docker container security
Docker container securityThoughtworks The document discusses security challenges and best practices for Docker containers. It outlines risks at different stages of the container lifecycle from image development to deployment. Key risks include lack of isolation, complex ecosystems, and known vulnerabilities. The document recommends practices like using linting and scanning during development, restricting resources and access controls at deployment, and signing images from trusted sources to improve container security.
Redefining the unit
Redefining the unitThoughtworks Mainframes handle 30 billion business transactions each day and 87% of all credit card transactions*, they are not traditionally associated with flexible, fail-fast development approaches. Can we bring the practices of agile, CI/CD and fully automated deployments to applications running on a mainframe? During our talk, we'll tell you a story about test automation; redefining the smallest testable unit of a program. And we'll discuss our learnings from introducing continuous integration and agile practices to the world of insurance and mainframes.
*9 Mainframe statistics that may surprise you
Technology Radar Webinar UK - Vol. 22
Technology Radar Webinar UK - Vol. 22Thoughtworks ThoughtWorks' Lucy Kurian, James Lewis & Kief Morris discuss tech trends in our latest Technology Radar, covering techniques, platforms, tools, languages and frameworks.
Recently uploaded (20)
AI-proof your career by Olivier Vroom and David WIlliamson
AI-proof your career by Olivier Vroom and David WIlliamsonUXPA Boston This talk explores the evolving role of AI in UX design and the ongoing debate about whether AI might replace UX professionals. The discussion will explore how AI is shaping workflows, where human skills remain essential, and how designers can adapt. Attendees will gain insights into the ways AI can enhance creativity, streamline processes, and create new challenges for UX professionals.
AI’s influence on UX is growing, from automating research analysis to generating design prototypes. While some believe AI could make most workers (including designers) obsolete, AI can also be seen as an enhancement rather than a replacement. This session, featuring two speakers, will examine both perspectives and provide practical ideas for integrating AI into design workflows, developing AI literacy, and staying adaptable as the field continues to change.
The session will include a relatively long guided Q&A and discussion section, encouraging attendees to philosophize, share reflections, and explore open-ended questions about AI’s long-term impact on the UX profession.
AI and Gender: Decoding the Sociological Impact
AI and Gender: Decoding the Sociological ImpactSaikatBasu37 Exploring the Intersection of Technology and Society. How does AI shape our understanding of gender, and what does it mean for society?
Multi-Agent AI Systems: Architectures & Communication (MCP and A2A)
Multi-Agent AI Systems: Architectures & Communication (MCP and A2A)HusseinMalikMammadli Multi-Agent AI Systems: Architectures & Communication (MCP and A2A)
Cybersecurity Threat Vectors and Mitigation
Cybersecurity Threat Vectors and MitigationVICTOR MAESTRE RAMIREZ Cybersecurity Threat Vectors and Mitigation
DNF 2.0 Implementations Challenges in Nepal
DNF 2.0 Implementations Challenges in NepalICT Frame Magazine Pvt. Ltd. A national workshop bringing together government, private sector, academia, and civil society to discuss the implementation of Digital Nepal Framework 2.0 and shape the future of Nepal’s digital transformation.
accessibility Considerations during Design by Rick Blair, Schneider Electric
accessibility Considerations during Design by Rick Blair, Schneider ElectricUXPA Boston as UX and UI designers, we are responsible for creating designs that result in products, services, and websites that are easy to use, intuitive, and can be used by as many people as possible. accessibility, which is often overlooked, plays a major role in the creation of inclusive designs. In this presentation, you will learn how you, as a designer, play a major role in the creation of accessible artifacts.
Building the Customer Identity Community, Together.pdf
Building the Customer Identity Community, Together.pdfCheryl Hung https://www.oicheryl.com
Limecraft Webinar - 2025.3 release, featuring Content Delivery, Graphic Conte...
Limecraft Webinar - 2025.3 release, featuring Content Delivery, Graphic Conte...Maarten Verwaest Slides of Limecraft Webinar on May 8th 2025, where Jonna Kokko and Maarten Verwaest discuss the latest release.
This release includes major enhancements and improvements of the Delivery Workspace, as well as provisions against unintended exposure of Graphic Content, and rolls out the third iteration of dashboards.
Customer cases include Scripted Entertainment (continuing drama) for Warner Bros, as well as AI integration in Avid for ITV Studios Daytime.
DevOpsDays SLC - Platform Engineers are Product Managers.pptx
DevOpsDays SLC - Platform Engineers are Product Managers.pptxJustin Reock Platform Engineers are Product Managers: 10x Your Developer Experience
Discover how adopting this mindset can transform your platform engineering efforts into a high-impact, developer-centric initiative that empowers your teams and drives organizational success.
Platform engineering has emerged as a critical function that serves as the backbone for engineering teams, providing the tools and capabilities necessary to accelerate delivery. But to truly maximize their impact, platform engineers should embrace a product management mindset. When thinking like product managers, platform engineers better understand their internal customers' needs, prioritize features, and deliver a seamless developer experience that can 10x an engineering team’s productivity.
In this session, Justin Reock, Deputy CTO at DX (getdx.com), will demonstrate that platform engineers are, in fact, product managers for their internal developer customers. By treating the platform as an internally delivered product, and holding it to the same standard and rollout as any product, teams significantly accelerate the successful adoption of developer experience and platform engineering initiatives.
Cybersecurity Tools and Technologies - Microsoft Certificate
Cybersecurity Tools and Technologies - Microsoft CertificateVICTOR MAESTRE RAMIREZ Cybersecurity Tools and Technologies - Microsoft Certificate
Slack like a pro: strategies for 10x engineering teams
Slack like a pro: strategies for 10x engineering teamsNacho Cougil You know Slack, right? It's that tool that some of us have known for the amount of "noise" it generates per second (and that many of us mute as soon as we install it 😅).
But, do you really know it? Do you know how to use it to get the most out of it? Are you sure 🤔? Are you tired of the amount of messages you have to reply to? Are you worried about the hundred conversations you have open? Or are you unaware of changes in projects relevant to your team? Would you like to automate tasks but don't know how to do so?
In this session, I'll try to share how using Slack can help you to be more productive, not only for you but for your colleagues and how that can help you to be much more efficient... and live more relaxed 😉.
If you thought that our work was based (only) on writing code, ... I'm sorry to tell you, but the truth is that it's not 😅. What's more, in the fast-paced world we live in, where so many things change at an accelerated speed, communication is key, and if you use Slack, you should learn to make the most of it.
---
Presentation shared at JCON Europe '25
Feedback form:
http://tiny.cc/slack-like-a-pro-feedback
Building Connected Agents: An Overview of Google's ADK and A2A Protocol
Building Connected Agents: An Overview of Google's ADK and A2A ProtocolSuresh Peiris Google's Agent Development Kit (ADK) provides a framework for building AI agents, including complex multi-agent systems. It offers tools for development, deployment, and orchestration.
Complementing this, the Agent2Agent (A2A) protocol is an open standard by Google that enables these AI agents, even if from different developers or frameworks, to communicate and collaborate effectively. A2A allows agents to discover each other's capabilities and work together on tasks.
In essence, ADK helps create the agents, and A2A provides the common language for these connected agents to interact and form more powerful, interoperable AI solutions.
UiPath AgentHack - Build the AI agents of tomorrow_Enablement 1.pptx
UiPath AgentHack - Build the AI agents of tomorrow_Enablement 1.pptxanabulhac Join our first UiPath AgentHack enablement session with the UiPath team to learn more about the upcoming AgentHack! Explore some of the things you'll want to think about as you prepare your entry. Ask your questions.
論文紹介："InfLoRA: Interference-Free Low-Rank Adaptation for Continual Learning" ...
論文紹介："InfLoRA: Interference-Free Low-Rank Adaptation for Continual Learning" ...Toru Tamaki Yan-Shuo Liang, Wu-Jun Li,"Adaptive Plasticity Improvement for Continual Learning" CVPR2023
https://openaccess.thecvf.com/content/CVPR2023/html/Liang_Adaptive_Plasticity_Improvement_for_Continual_Learning_CVPR_2023_paper.html
Yan-Shuo Liang, Wu-Jun Li,"InfLoRA: Interference-Free Low-Rank Adaptation for Continual Learning" CVPR2024
https://openaccess.thecvf.com/content/CVPR2024/html/Liang_InfLoRA_Interference-Free_Low-Rank_Adaptation_for_Continual_Learning_CVPR_2024_paper.html
How Top Companies Benefit from Outsourcing
How Top Companies Benefit from OutsourcingNascenture Explore how leading companies leverage outsourcing to streamline operations, cut costs, and stay ahead in innovation. By tapping into specialized talent and focusing on core strengths, top brands achieve scalability, efficiency, and faster product delivery through strategic outsourcing partnerships.
AI x Accessibility UXPA by Stew Smith and Olivier Vroom
AI x Accessibility UXPA by Stew Smith and Olivier VroomUXPA Boston This presentation explores how AI will transform traditional assistive technologies and create entirely new ways to increase inclusion. The presenters will focus specifically on AI's potential to better serve the deaf community - an area where both presenters have made connections and are conducting research. The presenters are conducting a survey of the deaf community to better understand their needs and will present the findings and implications during the presentation.
AI integration into accessibility solutions marks one of the most significant technological advancements of our time. For UX designers and researchers, a basic understanding of how AI systems operate, from simple rule-based algorithms to sophisticated neural networks, offers crucial knowledge for creating more intuitive and adaptable interfaces to improve the lives of 1.3 billion people worldwide living with disabilities.
Attendees will gain valuable insights into designing AI-powered accessibility solutions prioritizing real user needs. The presenters will present practical human-centered design frameworks that balance AI’s capabilities with real-world user experiences. By exploring current applications, emerging innovations, and firsthand perspectives from the deaf community, this presentation will equip UX professionals with actionable strategies to create more inclusive digital experiences that address a wide range of accessibility challenges.
Dark Dynamism: drones, dark factories and deurbanization
Dark Dynamism: drones, dark factories and deurbanizationJakub Šimek Startup villages are the next frontier on the road to network states. This book aims to serve as a practical guide to bootstrap a desired future that is both definite and optimistic, to quote Peter Thiel’s framework.
Dark Dynamism is my second book, a kind of sequel to Bespoke Balajisms I published on Kindle in 2024. The first book was about 90 ideas of Balaji Srinivasan and 10 of my own concepts, I built on top of his thinking.
In Dark Dynamism, I focus on my ideas I played with over the last 8 years, inspired by Balaji Srinivasan, Alexander Bard and many people from the Game B and IDW scenes.
Enabling CD in Enterprises with Testing
- 1. ENABLING CONTINUOUS DELIVERY IN ENTERPRISES WITH TESTING Anand Bagmar Test Practice Lead 1
- 3. WHAT DO YOU EXPECT FROM THIS SESSION?
- 4. A Triangle = A Pentagon
- 5. Test Automation A PRACTICE THAT MAKES TEAMS SUCCESSFUL?
- 6. Test Automation A PRACTICE THAT MAKES TEAMS UNSUCCESSFUL?
- 7. What is Test Automation?
- 8. Automation – A Safety Net
- 9. Manual / Exploratory UI Web Service View JavaScript Integration Unit Time Value Cost IDEAL TEST AUTOMATION PYRAMID
- 10. REALITY
- 11. UI Web Service View JavaScript Integration Unit ICE-CREAM CONE ANTI PATTERN Manual / Exploratory
- 12. Developers Test Pyramid QA Team Test Pyramid Web Service View JavaScript Integration Unit Manual / Exploratory UI Web Service DUAL TEST PYRAMID ANTI-PATTERN
- 13. CONTINUOUS INTEGRATION (CI) ”… is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible…." - Martin Fowler, ThoughtWorks Chief Scientist http://www.thoughtworks.com/continuous-delivery
- 14. CI PROCESS
- 15. CONTINUOUS DELIVERY (CD) … is the natural extension of Continuous Integration: an approach in which teams ensure that every change to the system is releasable, and that we can release any version at the push of a button. Continuous Delivery aims to make releases boring, so we can deliver frequently and get fast feedback on what users care about. - Martin Fowler, ThoughtWorks Chief Scientist http://www.thoughtworks.com/continuous-delivery
- 18. ORGANIZATION OBJECTIVE Money / Value Time Quality
- 20. Existing systems in Bank External systems Customizing the Core Banking Product PROGRAM SCOPE Legacy Core Banking Platform
- 21. 130 systems and 290 interfaces!PROGRAM SCOPE
- 22. EXECUTION CHALLENGES Multi-Partners - Policies - Constraints - Way of working Stakeholders Agile Money! Trust
- 23. OTHER CHALLENGES Co-Existence Data Migration Scope Defect Management Team Distribution & Integration
- 26. CODE QUALITY Core product team(s) Customization team(s) Integration & configuration team(s) Systems team(s) NFR Team(s)
- 27. How do you get early feedback in such type of situation? 27
- 28. De Integrated Environment Unit tests Integration tests Web Service tests Functional UI Tests Manual / Exploratory tests Legend
- 33. De Integrated Environment Developer Environment Semi-Integrated Environment Stubbed Environment Pre-Prod / UAT Environment
- 34. WHAT THIS MEANS IS 34 Identify tests for specific environments Automation practices Get early feedback Identify environments Test Consolidation Maintenance Test PrioritizationCommon repository Test categorization Single Dashboard DevOps Testing cannot work in isolation
- 35. KEY TAKEAWAYS Listen Buy-in Levers Scope / Time / Capacity Transparent Quick Feedback - Give & Take Quality Learn & EvolveInnovate Trust Shared Understanding Flexible
- 36. A Triangle == A Pentagon 36 So ….
- 37. OR … 37 A Triangle == A n-dimensional Polygon