Interactive Session on "Chaos engineering: Break it to make it" by Anupam Agarwal,Nagarro, Peeyush Girdhar, Cloud / DevOps Nagarro. at #ATAGTR2021.
#ATAGTR2021 was the 6th Edition of Global Testing Retreat.
The video recording of the session is now available on the following link: https://www.youtube.com/watch?v=4bM4f8xNp2A
To know more about #ATAGTR2021, please visit:https://gtr.agiletestingalliance.org/
General overview of what is "Chaos Engineering", the current
"perturbation models" available and the benefits of Chaos Engineering to Customers, Business and Tech.
One of the core tenets of what people consider to be “DevOps” is to shorten the feedback loop in your development cycles. This tenet ties in directly with Agile methodologies utilized by software engineering teams. With the advent of easily accessible cloud infrastructure, and with the various operational tooling around those new infrastructure providers reaching a new level of maturity, we are now seeing a world where “DevOps” is mainstream. For companies starting new product development initiatives, using some form of Configuration Management is now table stakes to iterate quickly. Continuous Integration. Continuous Deployment. But who (or what) is continually monitoring the state of your operational security? This is where SecDevOps, or SecOps, comes into play. The SecDevOps methodology allows you to improve your security monitoring and response time, while maintaining your ability to continually deploy changes.
The Next Wave of Reliability EngineeringMichael Kehoe
In 2018, Site Reliability Engineering (SRE) will turn 15 years old. Since Google's inception of the term SRE, companies across the world have adopted a new operations mindset along with automation, deployment and monitoring principals. Most of what SRE does now is well established throughout the industry, so what is the next-wave of reliability principals and automation frameworks?
This session will dive into what the future holds for reliability engineering as a field and what will be the next areas of investment and improvement for reliability teams.
Chaos Engineering - The Art of Breaking Things in ProductionKeet Sugathadasa
This is an introduction to Chaos Engineering - the Art of Breaking things in Production. This is conducted by two Site Reliability Engineers which explains the concepts, history, principles along with a demonstration of Chaos Engineering
The technical talk is given in this video: https://youtu.be/GMwtQYFlojU
Curious about how chaos engineering can make your systems more resilient?
Get a comprehensive introduction to the history, principles, and practice of chaos engineering
You will walk away from this session with an in-depth understanding of what chaos engineering is, why it’s crucial to prevent outages, and how you can use it to build resilience into your own systems.
Site Reliability Engineering: An Enterprise Adoption Story (an ITSM Academy W...ITSM Academy, Inc.
Presenter: Perry Statham
SRE Squad Leader with IBM Cloud DevOps Services
In this presentation, the IBM DevOps Services SRE team will give a brief introduction to Site Reliability Engineering, then show how they adopted its principals in their existing enterprise organization.
General overview of what is "Chaos Engineering", the current
"perturbation models" available and the benefits of Chaos Engineering to Customers, Business and Tech.
One of the core tenets of what people consider to be “DevOps” is to shorten the feedback loop in your development cycles. This tenet ties in directly with Agile methodologies utilized by software engineering teams. With the advent of easily accessible cloud infrastructure, and with the various operational tooling around those new infrastructure providers reaching a new level of maturity, we are now seeing a world where “DevOps” is mainstream. For companies starting new product development initiatives, using some form of Configuration Management is now table stakes to iterate quickly. Continuous Integration. Continuous Deployment. But who (or what) is continually monitoring the state of your operational security? This is where SecDevOps, or SecOps, comes into play. The SecDevOps methodology allows you to improve your security monitoring and response time, while maintaining your ability to continually deploy changes.
The Next Wave of Reliability EngineeringMichael Kehoe
In 2018, Site Reliability Engineering (SRE) will turn 15 years old. Since Google's inception of the term SRE, companies across the world have adopted a new operations mindset along with automation, deployment and monitoring principals. Most of what SRE does now is well established throughout the industry, so what is the next-wave of reliability principals and automation frameworks?
This session will dive into what the future holds for reliability engineering as a field and what will be the next areas of investment and improvement for reliability teams.
Chaos Engineering - The Art of Breaking Things in ProductionKeet Sugathadasa
This is an introduction to Chaos Engineering - the Art of Breaking things in Production. This is conducted by two Site Reliability Engineers which explains the concepts, history, principles along with a demonstration of Chaos Engineering
The technical talk is given in this video: https://youtu.be/GMwtQYFlojU
Curious about how chaos engineering can make your systems more resilient?
Get a comprehensive introduction to the history, principles, and practice of chaos engineering
You will walk away from this session with an in-depth understanding of what chaos engineering is, why it’s crucial to prevent outages, and how you can use it to build resilience into your own systems.
Site Reliability Engineering: An Enterprise Adoption Story (an ITSM Academy W...ITSM Academy, Inc.
Presenter: Perry Statham
SRE Squad Leader with IBM Cloud DevOps Services
In this presentation, the IBM DevOps Services SRE team will give a brief introduction to Site Reliability Engineering, then show how they adopted its principals in their existing enterprise organization.
Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below!
Chaos Engineering, When should you release the monkeys?Thoughtworks
Chaos Engineering is listed as 'Trial' in the ThoughtWorks Tech Radar, but what is it really and how is it different from traditional testing? When and why should you get started with Chaos Engineering and is Chaos Monkey the right place to start when you do?
4 Steps to Effectively Integrate DevOps Workflows With Cloud Security PracticesThreat Stack
Most companies value speed over security, which has traditionally been a blocker in delivering software. But with more and more breaches and vulnerabilities reported (Shellshock and Heartbleed to name a just few) it's more important than ever that security gets integrated into the operations process. Here are the top four ways to balance DevOps workflows while maintaining a pragmatic view on security.
A testing environment is nothing but a setup of hardware and software requirements for the testing teams to run the test cases. As such, it provides support for test execution with software, hardware and network arranged.
Architectural Testability Workshop for Test Academy BarcelonaAsh Winter
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model.
It All Started With a Wager About System UpgradesThreat Stack
When running workloads in Cloud environments, do organizations routinely and blindly upgrade their systems? While immutable infrastructure, blue/green deployments, and treating servers like cattle instead of pets is all the buzz, in reality, successfully executing these practices is trickier than expected.
Chaos Engineering: Why the World Needs More Resilient SystemsC4Media
Video and slides synchronized, mp3 and slide download available at URL https://bit.ly/2luk9iS.
Tammy Butow shares her experiences using chaos engineering to build resilient systems, when they couldn’t build their systems from scratch. Filmed at qconlondon.com.
Tammy Butow is a Principal SRE at Gremlin where she works on Chaos Engineering, the facilitation of controlled experiments to identify systemic weaknesses. Previously, she led SRE teams at Dropbox responsible for Databases and Storage systems used by over 500 million customers.
Testability is Everyone's ResponsibilityAsh Winter
Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends.
Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking 'when will testing be done.' It's never done, it can only stop, just so you know.
Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers.
During the talk, we will cover:
* How testability is a key advantage in building systems of ever increasing complexity.
* Why it's important for developers and operational stakeholders to build inherently testable systems.
* What testers can do to be catalysts for testability improvements.
The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It's for all of us to care about.
Software development practices & Infrastructure as Code - how well do they wo...Equal Experts
Infrastructure as Code (IaC) has rapidly become a key part of cloud native engineering. The hard gained experience from writing software can be applied to infrastructure, but fundamental differences means some fundamental approached need to be reconsidered. This talk will explore the implications for test driven development and build pipelines applied to IaC.
Jon Barber is an Engineer with Equal Experts.
He has been paid to write software for over 30 years, and has spent most of his time recently in the platform engineering space. He’s a keen advocate of XP values and practices, and sees himself more as an engineer than craftsman.
Should You Use Security Point Solutions?Threat Stack
Compiling the right set of security solutions to meet your company’s unique requirements is no easy feat. The security needs of each company can vary widely depending on compliance regulations, the industry threat profile and types of data processed, among many other factors. This post breaks down point solutions vs. security platforms.
SHOWDOWN: Threat Stack vs. Red Hat AuditDThreat Stack
Traditionally, people have used the userland daemon ‘auditd’ built by some good Red Hat folks to collect and consume this data. However, there are a couple of problems with traditional open source auditd and auditd libraries that we’ve had to deal with ourselves, especially when trying to run it on performance sensitive systems and make sense of the sometimes obtuse data that traditional auditd spits out. To that effect, we’ve written a custom audit listener from the ground up for the Threat Stack agent (tsauditd).
Security incident response is a reactive and chaotic exercise. What if it were possible to flip the scenario on its head? Security focused chaos engineering takes the approach of advancing the security incident response apparatus by reversing the postmortem and preparation phases. Contrary to Purple Team or Red Team game days, Security Chaos Engineering does not use threat actor tactics, techniques and procedures. It develops teams through unique configuration, cyber threat and user error scenarios that challenge responders to react to events outside their playbooks and comfort zones.
Security Chaos Engineering allows incident response and product teams to derive new information about the state of security within their distributed systems that was previously unknown. Within this new paradigm of instrumentation where we proactively conduct “Pre-Incident” vs. “Post-Incident” reviews we are now able to more accurately measure how effective our security incident response teams, tools, skills, and procedures are during the manic of the Incident Response function.
In this session Aaron Rinehart, the mind behind the first Open Source Security Chaos Engineering tool ChaoSlingr, will introduce how Security Chaos Engineering can be applied to create highly secure, performant, and resilient distributed systems.
InfoQ Live - Reducing Uncertainty in Software Delivery - Building reliability...Ana Medina
Building Reliability One Step at a Time
Building reliability in our organizations allows us to continue giving our customers a great user experience when they need it most. Many companies measure their reliability via nines of availability or system uptime percentage. Site Reliability Engineering has taught us some of the practices we can adopt to reach our availability goals but we have to keep in mind that reaching your organization’s availability goals will be a learning experience and we have to be proactive about responding to failure. In this talk, Ana will share how she has been using Chaos Engineering since 2016 to learn more about the systems she worked on and how this practice can be used to decouple our system’s weak points, learn from incidents and improve monitoring and observability.
30 February 2005 QUEUE rants [email protected] DARNEDTestin.docxtamicawaysmith
30 February 2005 QUEUE rants: [email protected] DARNEDTesting large systems is a daunting task, but there are steps we can take to ease the pain.
T
he increasing size and complexity of software, coupled with concurrency and dis-
tributed systems, has made apparent the ineffectiveness of using only handcrafted
tests. The misuse of code coverage and avoidance of random testing has exacer-
bated the problem. We must start again, beginning with good design (including
dependency analysis), good static checking (including model property checking), and
good unit testing (including good input selection). Code coverage can help select and
prioritize tests to make you more effi cient, as can the all-pairs technique for controlling
the number of confi gurations. Finally, testers can use models to generate test coverage
and good stochastic tests, and to act as test oracles.
HANDCRAFTED TESTS OUTPACED BY HARDWARE AND SOFTWARE
Hardware advances have followed Moore’s law for years, giving the capability for run-
ning ever-more complex software on the same cost platform. Developers have taken
advantage of this by raising their level of abstraction from assembly to fi rst-generation
compiled languages to managed code such as C# and Java, and rapid application devel-
opment environments such as Visual Basic. Although the number of lines of code per
day per programmer appears to remain relatively fi xed, the power of each line of code
has increased, allowing complex systems to be built. Moore’s law provides double the
computing power every 18 months and software code size tends to double every seven
years, but software testing does not appear to be keeping pace.
QUEUE February 2005 31 more queue: www.acmqueue.comBIGBIGBIGTO TESTTOO DARNED
Quality
AssuranceFO
C
U
S
KEITH STOBIE, MICROSOFT
32 February 2005 QUEUE rants: [email protected]
Unfortunately, the increased power has not, in gen-
eral, made testing easier. While in a few cases the more
powerful hardware means we can do more complete test-
ing, in general the testing problem is getting worse. You
can test square root for all the 32-bit values in a reason-
able time,1,2 but we are now moving to 64-bit machines
with 64-bit values (and even longer for fl oating point).
Assuming a nanosecond per test case, it would take 584
years to test all the values. Sure, you could scale to, say,
1,000 processors, but you would still need six months for
just this one test case.
Two other issues of complexity to consider are: the
number of different execution states software can go
through, and concurrency. User interfaces were originally
very rigid, letting users progress through a single fi xed
set of operations—for example, a single set of hierarchi-
cal menus and prompts. Now, good user design is event
driven with the user in control of the sequence of actions.
Further, many actions can be accomplished in multiple
manners (e.g., closing a window via the menu [File/
Close] ...
Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below!
Chaos Engineering, When should you release the monkeys?Thoughtworks
Chaos Engineering is listed as 'Trial' in the ThoughtWorks Tech Radar, but what is it really and how is it different from traditional testing? When and why should you get started with Chaos Engineering and is Chaos Monkey the right place to start when you do?
4 Steps to Effectively Integrate DevOps Workflows With Cloud Security PracticesThreat Stack
Most companies value speed over security, which has traditionally been a blocker in delivering software. But with more and more breaches and vulnerabilities reported (Shellshock and Heartbleed to name a just few) it's more important than ever that security gets integrated into the operations process. Here are the top four ways to balance DevOps workflows while maintaining a pragmatic view on security.
A testing environment is nothing but a setup of hardware and software requirements for the testing teams to run the test cases. As such, it provides support for test execution with software, hardware and network arranged.
Architectural Testability Workshop for Test Academy BarcelonaAsh Winter
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model.
It All Started With a Wager About System UpgradesThreat Stack
When running workloads in Cloud environments, do organizations routinely and blindly upgrade their systems? While immutable infrastructure, blue/green deployments, and treating servers like cattle instead of pets is all the buzz, in reality, successfully executing these practices is trickier than expected.
Chaos Engineering: Why the World Needs More Resilient SystemsC4Media
Video and slides synchronized, mp3 and slide download available at URL https://bit.ly/2luk9iS.
Tammy Butow shares her experiences using chaos engineering to build resilient systems, when they couldn’t build their systems from scratch. Filmed at qconlondon.com.
Tammy Butow is a Principal SRE at Gremlin where she works on Chaos Engineering, the facilitation of controlled experiments to identify systemic weaknesses. Previously, she led SRE teams at Dropbox responsible for Databases and Storage systems used by over 500 million customers.
Testability is Everyone's ResponsibilityAsh Winter
Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends.
Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking 'when will testing be done.' It's never done, it can only stop, just so you know.
Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers.
During the talk, we will cover:
* How testability is a key advantage in building systems of ever increasing complexity.
* Why it's important for developers and operational stakeholders to build inherently testable systems.
* What testers can do to be catalysts for testability improvements.
The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It's for all of us to care about.
Software development practices & Infrastructure as Code - how well do they wo...Equal Experts
Infrastructure as Code (IaC) has rapidly become a key part of cloud native engineering. The hard gained experience from writing software can be applied to infrastructure, but fundamental differences means some fundamental approached need to be reconsidered. This talk will explore the implications for test driven development and build pipelines applied to IaC.
Jon Barber is an Engineer with Equal Experts.
He has been paid to write software for over 30 years, and has spent most of his time recently in the platform engineering space. He’s a keen advocate of XP values and practices, and sees himself more as an engineer than craftsman.
Should You Use Security Point Solutions?Threat Stack
Compiling the right set of security solutions to meet your company’s unique requirements is no easy feat. The security needs of each company can vary widely depending on compliance regulations, the industry threat profile and types of data processed, among many other factors. This post breaks down point solutions vs. security platforms.
SHOWDOWN: Threat Stack vs. Red Hat AuditDThreat Stack
Traditionally, people have used the userland daemon ‘auditd’ built by some good Red Hat folks to collect and consume this data. However, there are a couple of problems with traditional open source auditd and auditd libraries that we’ve had to deal with ourselves, especially when trying to run it on performance sensitive systems and make sense of the sometimes obtuse data that traditional auditd spits out. To that effect, we’ve written a custom audit listener from the ground up for the Threat Stack agent (tsauditd).
Security incident response is a reactive and chaotic exercise. What if it were possible to flip the scenario on its head? Security focused chaos engineering takes the approach of advancing the security incident response apparatus by reversing the postmortem and preparation phases. Contrary to Purple Team or Red Team game days, Security Chaos Engineering does not use threat actor tactics, techniques and procedures. It develops teams through unique configuration, cyber threat and user error scenarios that challenge responders to react to events outside their playbooks and comfort zones.
Security Chaos Engineering allows incident response and product teams to derive new information about the state of security within their distributed systems that was previously unknown. Within this new paradigm of instrumentation where we proactively conduct “Pre-Incident” vs. “Post-Incident” reviews we are now able to more accurately measure how effective our security incident response teams, tools, skills, and procedures are during the manic of the Incident Response function.
In this session Aaron Rinehart, the mind behind the first Open Source Security Chaos Engineering tool ChaoSlingr, will introduce how Security Chaos Engineering can be applied to create highly secure, performant, and resilient distributed systems.
InfoQ Live - Reducing Uncertainty in Software Delivery - Building reliability...Ana Medina
Building Reliability One Step at a Time
Building reliability in our organizations allows us to continue giving our customers a great user experience when they need it most. Many companies measure their reliability via nines of availability or system uptime percentage. Site Reliability Engineering has taught us some of the practices we can adopt to reach our availability goals but we have to keep in mind that reaching your organization’s availability goals will be a learning experience and we have to be proactive about responding to failure. In this talk, Ana will share how she has been using Chaos Engineering since 2016 to learn more about the systems she worked on and how this practice can be used to decouple our system’s weak points, learn from incidents and improve monitoring and observability.
30 February 2005 QUEUE rants [email protected] DARNEDTestin.docxtamicawaysmith
30 February 2005 QUEUE rants: [email protected] DARNEDTesting large systems is a daunting task, but there are steps we can take to ease the pain.
T
he increasing size and complexity of software, coupled with concurrency and dis-
tributed systems, has made apparent the ineffectiveness of using only handcrafted
tests. The misuse of code coverage and avoidance of random testing has exacer-
bated the problem. We must start again, beginning with good design (including
dependency analysis), good static checking (including model property checking), and
good unit testing (including good input selection). Code coverage can help select and
prioritize tests to make you more effi cient, as can the all-pairs technique for controlling
the number of confi gurations. Finally, testers can use models to generate test coverage
and good stochastic tests, and to act as test oracles.
HANDCRAFTED TESTS OUTPACED BY HARDWARE AND SOFTWARE
Hardware advances have followed Moore’s law for years, giving the capability for run-
ning ever-more complex software on the same cost platform. Developers have taken
advantage of this by raising their level of abstraction from assembly to fi rst-generation
compiled languages to managed code such as C# and Java, and rapid application devel-
opment environments such as Visual Basic. Although the number of lines of code per
day per programmer appears to remain relatively fi xed, the power of each line of code
has increased, allowing complex systems to be built. Moore’s law provides double the
computing power every 18 months and software code size tends to double every seven
years, but software testing does not appear to be keeping pace.
QUEUE February 2005 31 more queue: www.acmqueue.comBIGBIGBIGTO TESTTOO DARNED
Quality
AssuranceFO
C
U
S
KEITH STOBIE, MICROSOFT
32 February 2005 QUEUE rants: [email protected]
Unfortunately, the increased power has not, in gen-
eral, made testing easier. While in a few cases the more
powerful hardware means we can do more complete test-
ing, in general the testing problem is getting worse. You
can test square root for all the 32-bit values in a reason-
able time,1,2 but we are now moving to 64-bit machines
with 64-bit values (and even longer for fl oating point).
Assuming a nanosecond per test case, it would take 584
years to test all the values. Sure, you could scale to, say,
1,000 processors, but you would still need six months for
just this one test case.
Two other issues of complexity to consider are: the
number of different execution states software can go
through, and concurrency. User interfaces were originally
very rigid, letting users progress through a single fi xed
set of operations—for example, a single set of hierarchi-
cal menus and prompts. Now, good user design is event
driven with the user in control of the sequence of actions.
Further, many actions can be accomplished in multiple
manners (e.g., closing a window via the menu [File/
Close] ...
Test Environment Management (TEM) is a function in the software delivery process which aids the software testing cycle by providing a validated, stable and usable test-environment to execute the test scenarios or replicate bugs.
For Impetus’ White Papers archive, visit- http://www.impetus.com/whitepaper
In this white paper, Impetus focuses on how the power of the Cloud can be harnessed to address the software product testing challenges faced by organizations.
Using security to drive chaos engineering - April 2018Dinis Cruz
Presentation I delivered at ISSA UK "Application Security - London Chapter Meeting" https://www.eventbrite.co.uk/e/application-security-london-chapter-meeting-tickets-42284085839
This publication is to help software engineering students to understand the basis in software testing. Software testing is an inevitable process in software development.
What is DevOps? It’s a fairly hot term in today’s application development and operations space,but there are many different definitions as to what DevOps really is. Ultimately, DevOps is abouthow teams build software, deploy software and maintain it throughout its lifecycle. There is nosingle, right answer to the question, but there are a number of tools and strategies that can helpcustomers adopt a winning DevOps process that allows dev and operations teams to moreproductive together.In this session, the audience will learn what DevOps is at a high level, provide strategies for howto implement a DevOps process that fits their organization’s needs and how the MicrosoftApplication Lifecycle Management (ALM) tooling can help with this. As part of the session,attendees can expect to learn how to set up the Microsoft ALM stack for their teams and how touse it effectively in their software development lifecycle, regardless of the role each individual plays on the team.
DBTest 2013 - In Data Veritas - Data Driven Testing for Distributed SystemsMihir Gandhi
The increasing deployment of distributed systems to solve
large data and computational problems has not seen a con-
comitant increase in tools and techniques to test these sys-
tems. In this paper, we propose a data driven approach to
testing. We translate our intuitions and expectations about
how the system should behave into invariants, the truth of
which can be verified from data emitted by the system. Our
particular implementation of the invariants uses Q, a high-
performance analytical database, programmed with a vector
language.
Chaos Engineering to Establish Software ReliabilityGleecusTechlabs1
Chaos Engineering is the practice of intentionally introducing controlled and measurable failures into software systems to build resilience and confidence in their ability to withstand unexpected conditions.
Creating and managing test environments best practices for test infrastructur...Knoldus Inc.
Explore best practices for setting up and managing test environments. Learn about infrastructure considerations, environment provisioning, configuration management, and infrastructure as code (IaC) principles. Gain insights to create stable, scalable, and reusable test environments.
Developing a web or mobile application takes a lot of effort, but all that effort can go down the drain quickly if you improperly load test the application or completely skip testing. Load testing applications is important and a necessary step in the pre-production stage.
New applications, ones that have not yet made it to the production stage, likely don’t have a performance benchmark established. You don’t typically know what to expect with a new app, which is why before you do a larger load test on any application you first do some baseline testing. This will allow you to establish some benchmarks and pick out any performance issues before you place a larger load on the app. For example, if your app crashes with just five users, you have a problem. Look to the application architects to determine if any service level agreements have been set for the application during design.
Once you have done some baseline testing you are ready to load test your application to determine its performance levels under heavier load. Here are 5 essential tips for starting load testing on an application.
From the the teams struggling with DevOps to experienced professionals trying to make a shift to DevOps, this presentation helps in how understanding how DevOps makes Deliveries faster and accurate
_DevOps Certification and Chaos Engineering Testing System Resilience.pptxwicultylearningsolut
while DevOps certification provides professionals with essential skills for streamlining software delivery, integrating Chaos Engineering principles into DevOps practices enhances system resilience and reliability. By embracing both disciplines, organizations can build a culture of continuous learning, experimentation, and resilience, ultimately delivering better software products that meet the demands of today's dynamic business environment.
in this presentation i demonstrated all of the testings that can be done to improve the continuous delivery system in the development process of software in the end i have demonstrated what TDD is and what are it's benefits after the slides i demonstrated the TDD methodology by building a small project(a simple stack) with three rules of TDD.
Similar to #ATAGTR2021 Presentation : "Chaos engineering: Break it to make it" by Anupam Agarwal, Peeyush Girdhar. (20)
#Interactive Session by Anindita Rath and Mahathee Dandibhotla, "From Good to...Agile Testing Alliance
#Interactive Session by Anindita Rath and Mahathee Dandibhotla, "From Good to Great: Enhancing Testability in Software Testing " at ATAGTR2023
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Ajay Balamurugadas, "Where Are The Real Testers In T...Agile Testing Alliance
#Interactive Session by Ajay Balamurugadas, "Where Are The Real Testers In The Age of AI? " at ATAGTR2023
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Jishnu Nambiar and Mayur Ovhal, "Monitoring Web Per...Agile Testing Alliance
#Interactive Session by Jishnu Nambiar and Mayur Ovhal, "Monitoring Web Performance: Leveraging Grafana and Selenium for Real-Time Issue Alerts" at ATAGTR2023
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Pradipta Biswas and Sucheta Saurabh Chitale, "Navigat...Agile Testing Alliance
#Interactive Session by Pradipta Biswas and Sucheta Saurabh Chitale, "Navigating the IoT Performance Testing Landscape" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Apoorva Ram, "The Art of Storytelling for Testers" at...Agile Testing Alliance
#Interactive Session by Apoorva Ram, "The Art of Storytelling for Testers" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Nikhil Jain, "Catch All Mail With Graph" at #ATAGTR2023.Agile Testing Alliance
#Interactive Session by Nikhil Jain, "Catch All Mail With Graph" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Ashok Kumar S, "Test Data the key to robust test cove...Agile Testing Alliance
#Interactive Session by Ashok Kumar S, "Test Data the key to robust test coverage" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Seema Kohli, "Test Leadership in the Era of Artificia...Agile Testing Alliance
#Interactive Session by Seema Kohli, "Test Leadership in the Era of Artificial Intelligence" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Ashwini Lalit, RRR of Test Automation Maintenance" at...Agile Testing Alliance
#Interactive Session by Ashwini Lalit, RRR of Test Automation Maintenance" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Srithanga Aishvarya T, "Machine Learning Model to aut...Agile Testing Alliance
#Interactive Session by Srithanga Aishvarya T, "Machine Learning Model to automate performance test script development using Jmeter" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Kirti Ranjan Satapathy and Nandini K, "Elements of Qu...Agile Testing Alliance
#Interactive Session by Kirti Ranjan Satapathy and Nandini K, "Elements of Quality Engineering in Remote IoT System" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Sudhir Upadhyay and Ashish Kumar, "Strengthening Test...Agile Testing Alliance
#Interactive Session by Sudhir Upadhyay and Ashish Kumar, "Strengthening Testing Oversight Using Environment Automation" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Sayan Deb Kundu, "Testing Gen AI Applications" at #AT...Agile Testing Alliance
#Interactive Session by Sayan Deb Kundu, "Testing Gen AI Applications" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Dinesh Boravke, "Zero Defects – Myth or Reality" at #...Agile Testing Alliance
#Interactive Session by Dinesh Boravke, "Zero Defects – Myth or Reality" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Saby Saurabh Bhardwaj, "Redefine Quality Assurance – Journey from Centralized to Decentralized, Distributed Blockchain/Web3 testing" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Keynote Session by Sanjay Kumar, "Innovation Inspired Testing!!" at #ATAGTR2...Agile Testing Alliance
#Keynote Session by Sanjay Kumar, "Innovation Inspired Testing!!" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Keynote Session by Schalk Cronje, "Don’t Containerize me" at #ATAGTR2023.Agile Testing Alliance
#Keynote Session by Schalk Cronje, "Don’t Containerize me" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Chidambaram Vetrivel and Venkatesh Belde, "Revolution...Agile Testing Alliance
#Interactive Session by Chidambaram Vetrivel and Venkatesh Belde, "Revolutionizing Security Testing with AI" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Aniket Diwakar Kadukar and Padimiti Vaidik Eswar Dat...Agile Testing Alliance
#Interactive Session by Aniket Diwakar Kadukar and Padimiti Vaidik Eswar Datta, "A Holistic Testing Methodology for Immersive Experience in AR, VR, and the Metaverse" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
#Interactive Session by Vivek Patle and Jahnavi Umarji, "Empowering Functiona...Agile Testing Alliance
#Interactive Session by Vivek Patle and Jahnavi Umarji, "Empowering Functional Testing with Support Vector Machines: An Experimental Journey" at #ATAGTR2023.
#ATAGTR2023 was the 8th Edition of Global Testing Retreat.
To know more about #ATAGTR2023, please visit: https://gtr.agiletestingalliance.org/
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
3. AGENDA
01
02
03
04
Concept of Chaos Engineering
Need for Chaos Engineering
Chaos Engineering vs Normal
Testing
Start your journey with Chaos
Engineering
4. Why the World Needs more Resilient Systems ?
1
BREACH
2
MATURITY
3
TEAMS
4
TESTING
Organizations confirmed or suspected breaches tied to their
applications or Infrastructure.
Organization that are in immature or improving state with respect to
environment resilience.
Teams have not incorporated resilience testing in their design during
initial stages of SDLC
Traditional testing are still not helping them to find the issues within
the ecosystems..
24%
86%
65%
47%
Common issues faced by multiple organizations
5. Chaos Engineering : Where are we ?
The art of breaking things purposefully
Ever since Netflix introduced Chaos Engineering
through their Simian Army toolset in 2012, the idea of
inducing failure as a preventative means has become
one of the preferred resilience techniques for cloud
native distributed systems.
“Chaos Engineering is the discipline of
experimenting on a distributed system in
order to induce artificial failures to build
confidence in the system's capability to withstand
turbulent conditions in production.”
Here's how Netflix describes why they built these chaos tools:
The cloud is all about redundancy and fault-tolerance. Since no single component can guarantee
100% uptime (and even the most expensive hardware eventually fails), we have to design a cloud
architecture where individual components can fail without affecting the availability of the entire
system. In effect, we have to be stronger than our weakest link.
6. Why Chaos Engineering?
Chaos Engineering is Preventive Medicine
Chaos Engineering is an approach for learning about how your
system behaves by applying a discipline of empirical
exploration.
Chaos engineering enables organizations to develop reliable and fault-tolerant
software systems, building your team’s confidence in them. The more stable
your systems are, the more confident you can be that they will function
properly.
By designing and executing Chaos Engineering experiments,
you will learn about weaknesses in your system that could
potentially lead to outages in customer environment.
LEARN
PREVENT
OUTAGES
BUILD
CONFIDENCE
7. Getting Started with Chaos Engineering
Disciplined approach to find failures before they become outages.
DEFINE ‘STEADY
STATE’
CREATE
HYPOTHESIS
RUN EXPERIMENTS INTERPRET THE
RESULTS
LEARN & IMPROVE
Start by defining
‘steady state’ as
some
measurable
output of a
system that
indicates normal
behavior.
Hypothesize that
this steady state
will continue in
both the control
group and the
experimental
group
Introduce attacks
that reflect real
world events like
server crash, hard
drive
malfunctioning,
network outage etc.
Try to disprove
the hypothesis
by looking for a
difference in
steady state
between the
control group
and the
experimental
Improve
functionalities in
the existing
system from the
above
experiments and
their results.
8. Chaos Engineering Meets DevOps
Maximize benefits by practicing automated Chaos Engineering within your
CI/CD pipelines
10. What is Game Day?
Game Day are like fire drills on a dedicated day for
running chaos engineering experiments on our
systems.
Define the timelines
Whiteboarding
Execution
Review
Define the Targets
How to run a
Game Day
Promote Chaos Days !!
11. How Chaos Engineering differ from Testing ?
Practice for generating new information
• Experiments propose a hypothesis,
and if the hypothesis is not
disproven, confidence grows in that
hypothesis. If it is disproven, then
we learn something new.
GENERATE NEW
INFORMATION
• An important distinction can be drawn
between testing and experimentation.
Tests make an assertion, based on
existing knowledge, and then running the
test collapses the valence of that
assertion, usually into either true or false.
DRAW DISTINCTION
When you want to explore the many ways,
a complex system can misbehave,
injecting communication failures like
latency and errors is one good approach.
EXPLORATION OF
UNKNOWN
• Testing, strictly speaking, does not
create new knowledge. Testing
requires that the engineer writing the
test knows specific properties about
the system that they are looking for
in advance.
COMPLEX ECOSYSTEM
12. Tools to kickstart your Chaos Journey
AWS Fault Injection
Which one to choose?
13. Is it even worth embracing?
Pros Cons
• Insights received after running chaos
testing can lead to a reduction in
production incidents for the future.
• Implementing Chaos tools for a large-
scale system and experimenting can
lead to an increase in cost.
• Helps in improving the confidence
and engagement of team members for
carrying out disaster recovery
methods and makes applications
highly reliable.
• Carelessness or Incorrect
steps in formation and implementation
can impact the application, thereby
hampering the customer.
• On a high level, Chaos Engineering
provides us an advantage by overall
system availability.
• It doesn't support all kinds of
deployment.
• Production outages can lead to huge
losses; therefore, chaos engineering
helps in the prevention of large
losses in revenue.
• Most of the chaos Engineering tools
do not covers all type of
environments and its components.
• The team can verify
system's behavior on failure to take
Opportunities & Obstacles