Deliver anything, anywhere, anytime
•
1 like•250 views
This document discusses continuous delivery of software. It defines continuous delivery as building, testing, and releasing software faster and more frequently while ensuring the software can be reliably released at any time to reduce costs and risks. Continuous delivery is compared to continuous deployment. Several large companies that practice continuous deployment, releasing software many times per day, are listed. The key aspects of continuous delivery workflows are described, including integration testing, a testing pyramid, feature toggles/branching, production-like environments, deployment pipelines for visibility, feedback and continual deployments without downtime, rollback capabilities, and close team collaboration. Advantages are highlighted such as reduced deployment risks, believable progress improving customer satisfaction, user feedback building better products, and improved quality.
Report
Share
Report
Share
Recommended
4 spring boot
Spring Boot makes it easy to create standalone Java applications by minimizing configuration boilerplate code. It aims to solve the problem that developers spend too much time re-implementing configuration for web applications rather than business logic. Spring Boot automatically configures Spring and embeds servlet containers like Tomcat, allowing applications to run with just a few lines of code as standalone JAR files. It integrates with many common libraries and tools out of the box.
Webinar Driving DevOps
Aan de hand van onze visualisatie van de DevOps cyclus gaan we in deze sessie in op de verschillende mogelijkheden om DevOps te verbeteren. Uit welke fasen bestaat de DevOps cyclus, welke DevOps practices kunnen hier geïmplementeerd worden en hoe vertaal je dit naar jouw organisatie?
We gaan ook in op hoe je kunt bepalen waar je staat en waar je het meeste verbetering kunt realiseren.
Continuous delivery is not finished
Continuous delivery is not finished for the following reasons:
1. Principles like treating the deployment pipeline as code and versioning it, as well as monitoring the system and mitigating problems, are often neglected.
2. Real user usage reveals different issues than testing, and unexpected things will always happen.
3. Continuous improvement is needed, including experimentation to get feedback from the business on changes and exploring new ideas in a controlled way using the continuous delivery pipeline.
State of continuous delivery in 2015 - Minsk 15-5-2015
The presentation gives high-level overview of most important aspects of implementing Continuous Delivery comparing CD with Agile, DevOps and Lean software development.
Agile Testing
This document provides an overview of agile testing and acceptance test-driven development. It discusses key principles of agile testing including writing tests early and often, providing continuous feedback, keeping tests simple, and practicing continuous improvement. It defines the differences between unit tests and acceptance tests, and best practices for acceptance test automation and design. The document emphasizes treating testing as a collaborative conversation rather than just finding defects.
Bugtracking
Neil Johnson does not use bug tracking software for his team because they take a more agile approach of immediately fixing bugs as they are discovered. Their process emphasizes preventing bugs from being introduced in the first place through practices like test-driven development and pair programming. They are able to prioritize fixing bugs over scheduled work due to the manageable rate of bug discovery and their system's suitability for testing. This talk is not about bug tracking software itself, but rather how continuous process improvement allows the team to inspect and adapt their workflow as needed.
Devops journey conference may 2016
Devops the end to end journey, How to get from where you are, to a fully devoops software delivery way of working
[Rakuten TechConf2014] [F-6] Changing the Behavior of IT
The document discusses changing IT behaviors through a DevOps approach. It outlines the author's journey and epiphany regarding more efficient operations management. Traditional IT processes are described as disjointed and task-focused, rather than maintaining optimal system states. DevOps is presented as integrating development and operations through practices like automation, testing at each step, and continuous feedback loops. This allows changes to automatically flow through environments while focusing on process over tasks.
Recommended
4 spring boot
Spring Boot makes it easy to create standalone Java applications by minimizing configuration boilerplate code. It aims to solve the problem that developers spend too much time re-implementing configuration for web applications rather than business logic. Spring Boot automatically configures Spring and embeds servlet containers like Tomcat, allowing applications to run with just a few lines of code as standalone JAR files. It integrates with many common libraries and tools out of the box.
Webinar Driving DevOps
Aan de hand van onze visualisatie van de DevOps cyclus gaan we in deze sessie in op de verschillende mogelijkheden om DevOps te verbeteren. Uit welke fasen bestaat de DevOps cyclus, welke DevOps practices kunnen hier geïmplementeerd worden en hoe vertaal je dit naar jouw organisatie?
We gaan ook in op hoe je kunt bepalen waar je staat en waar je het meeste verbetering kunt realiseren.
Continuous delivery is not finished
Continuous delivery is not finished for the following reasons:
1. Principles like treating the deployment pipeline as code and versioning it, as well as monitoring the system and mitigating problems, are often neglected.
2. Real user usage reveals different issues than testing, and unexpected things will always happen.
3. Continuous improvement is needed, including experimentation to get feedback from the business on changes and exploring new ideas in a controlled way using the continuous delivery pipeline.
State of continuous delivery in 2015 - Minsk 15-5-2015
The presentation gives high-level overview of most important aspects of implementing Continuous Delivery comparing CD with Agile, DevOps and Lean software development.
Agile Testing
This document provides an overview of agile testing and acceptance test-driven development. It discusses key principles of agile testing including writing tests early and often, providing continuous feedback, keeping tests simple, and practicing continuous improvement. It defines the differences between unit tests and acceptance tests, and best practices for acceptance test automation and design. The document emphasizes treating testing as a collaborative conversation rather than just finding defects.
Bugtracking
Neil Johnson does not use bug tracking software for his team because they take a more agile approach of immediately fixing bugs as they are discovered. Their process emphasizes preventing bugs from being introduced in the first place through practices like test-driven development and pair programming. They are able to prioritize fixing bugs over scheduled work due to the manageable rate of bug discovery and their system's suitability for testing. This talk is not about bug tracking software itself, but rather how continuous process improvement allows the team to inspect and adapt their workflow as needed.
Devops journey conference may 2016
Devops the end to end journey, How to get from where you are, to a fully devoops software delivery way of working
[Rakuten TechConf2014] [F-6] Changing the Behavior of IT
The document discusses changing IT behaviors through a DevOps approach. It outlines the author's journey and epiphany regarding more efficient operations management. Traditional IT processes are described as disjointed and task-focused, rather than maintaining optimal system states. DevOps is presented as integrating development and operations through practices like automation, testing at each step, and continuous feedback loops. This allows changes to automatically flow through environments while focusing on process over tasks.
Agile Project Management: "How I Learned to Stop Worrying and Love Agile”
The document discusses how project managers can adapt to agile methods. It begins by addressing common myths about agile project management and the stereotypes of project managers. It then discusses how the project manager role may change, focusing more on product ownership, collaboration with customers, and ensuring the highest priority features are delivered. The document emphasizes that agile embraces change and focuses on delivering working software over comprehensive documentation and responding to change rather than following a strict plan.
Implementing Test Automation: What a Manager Should Know
Decent test automation performance is no longer just an increased amount of script code. Learn all the ABCs of test automation.
Way to Agile - USTH
My presentation in Agile4U (Agile for University) program of HanoiScrum in 2013.
This presentation may have some customised content for University of Science and Technology of Ha Noi.
Automation testing
Introduction to We Application testing , need of automation , and tools that we use in Web Application testing
Continuous delivery
This document discusses the principles and benefits of continuous delivery. It emphasizes delivering valuable software to users as quickly as possible through early and continuous delivery. It recommends automating the software delivery process through practices like continuous integration, deployment pipelines, and feature flags to reduce risk and enable reliable, repeatable releases. Frequent integration and deployment allows for real project progress updates and quick recovery from any issues.
ATH2013-Unnat-MVP
The document discusses the concept of minimum viable product (MVP) and how it can be used to validate learning about customers with minimal effort. It defines MVP as the version that allows a team to collect the maximum amount of validated learning about customers with the least effort. The document outlines what MVP is and isn't, how to identify an MVP, and compares it to minimum marketable product. It also discusses using MVP in a loop of hypothesis, measurement, and experimentation and provides examples of notable MVPs.
How engineering practices help business
This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.
How to Reduce Time to Market Using Microsoft DevOps Solutions
Microsoft DevOps toolset replaces error-prone manual processes with automation for improved traceability and repeatable workflows.
Learn more about:
- The benefits of Continuous Integration practice
- Continuous Deployment as an accelerator to deliver high quality software
- How to use Visual Studio Team Services and Microsoft Azure to decrease rework and increase team productivity
Myths of Product Development
This document discusses common misconceptions in product development and proposes lean thinking alternatives. It addresses six prevailing practices: 1) high resource utilization improves performance, 2) large batches improve economics, 3) sticking to plans is best, 4) starting sooner finishes sooner, 5) more features increase customer liking, and 6) getting it right the first time is most successful. For each, it advocates limiting work in progress, incorporating customer feedback early and often through minimal viable products and experimentation, and accepting that plans will change and failure is part of the learning process. The key takeaway is to make information visible, quantify delays, introduce slack, focus on response over efficiency, use small batches with fast feedback, and treat plans and features
Bugday bkk-2014 nitisak-auto_perf
Nitisak Mooltreesri from DST Worldwide Services spoke about automated load testing for continuous delivery. He discussed how load testing is important to find bugs under high user loads. His company performs daily automated performance tests using simulation approaches to test incomplete systems cheaply and reliably. This helps reduce performance issues by providing early feedback and catching problems before deployment.
Adopting Scrum and Agile
Lessons learned from the use of the Scrum methodology at our Calgary office over the years. Presented to the rest of the company during a push for agile adoption by all our software groups.
How to Go Codeless for Automated Mobile App Testing
Find out the dos, don’ts and best ways to integrate codeless test automation in this webinar with Applause product director Cathy Huang.
My Customer Won't Accept Smaller Releases
Ignite talk at Lean Kanban North America 2013 on responding to the argument that customers won't accept smaller releases
Rapid deployment models for uPortal
Tom Freestone presented at the 2011 Jasig Conference on moving portal development to a continuous integration and delivery model. He discussed how traditional portal development led to errors and issues due to inconsistent environments across development, testing, staging and production. He advocated for empowering portal teams by enabling continuous integration, flexible and quick deployments, and treating the application as code with binaries, data and configuration managed in repositories. This would reduce errors, lower stress and allow anyone to deploy quickly.
From Dev and Ops to DevOps - reconfiguring the plane in flight.
The presentation describes how bitbrains is transforming from a traditional organisation towards a DevOps organisation while keeping the business running at the same time.
This presentation was given at the "Devops and the enterprise" meetup in Amsterdam on Jan 8th, 2014.
What the heck is Kanban? - CodeMash 2014
This document provides an overview of Kanban and how it was implemented at Hugsmiðjan, a software company in Iceland. It begins with basic Kanban principles like limiting work in progress and visualizing workflows. It then describes how Hugsmiðjan transitioned to Kanban over time, including establishing boards, templates and metrics to manage flow. Benefits included improved visibility, collaboration and reduced lead times, though challenges remained around process adherence and metrics use.
Preso #4
Our product, NoteStamp, is a Chrome extension that helps University of Michigan students easily annotate and take notes on lecture recordings. It allows students to bookmark important points in recordings and sync their notes to the timestamps. Unlike handwritten notes, NoteStamp lets users skip directly to saved bookmarks and view notes linked to specific points in recordings. Based on user feedback, future versions will integrate more seamlessly with lecture sites and allow exporting notes for review outside the extension.
Fundamentals of Agile
The document discusses fundamentals of agile development including the agile manifesto and its 12 principles. It emphasizes values such as individuals and interactions, working software, customer collaboration, and responding to change. It also discusses agile processes like Scrum and Kanban, continuous improvement through inspection and adaptation, and techniques like test-driven development, pair programming, and continuous integration to enable regular rapid feedback. Finally, it notes that while agile is popular, the real question is whether it will make teams more successful in delivering value to customers on time and under budget.
Top ten secret weapons for performance testing in an agile environment
This document outlines 10 secret weapons for performance testing in an agile environment. The secret weapons are: 1) Make performance explicit 2) Include performance testers in development teams 3) Base performance tests on customer requirements 4) Take a disciplined approach to experimentation and hypothesis testing 5) Start performance testing early in the development process 6) Iterate based on performance test results rather than just incrementally adding features 7) Automate all aspects of performance testing 8) Treat performance test code like any other code under test 9) Implement continuous performance testing 10) Get regular feedback on performance from stakeholders.
Continues Integration for Android
There are many tasks that need to be done. But why get bored by doing the exact same series of actions every time? Especially when a machine can do it faster and in a more reliable way! That's what incited us to automate the way we build, test, and deploy apps so we can focus on more creative tasks.
Test pyramid
The document discusses different types of software tests including unit tests, integration tests, service tests, and UI end-to-end tests. Unit tests check individual components, integration tests verify communication between components, service tests validate API requests and responses, and UI end-to-end tests simulate user interactions to check the full application. The document also provides an example of a student result service test response.
Inverting Test Pyramid - A First Hand Experience Report
Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.
Business Impact:
* Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.
* Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.
Reduced test execution time - Backend tests are much faster. Almost 7-10 times faster than UI Tests - improved build certification time.
* Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.
Details: http://confengine.com/agile-pune-2014/proposal/471/inverting-test-pyramid-a-first-hand-experience-report
Conference: http://pune.agileindia.org/
More Related Content
What's hot
Agile Project Management: "How I Learned to Stop Worrying and Love Agile”
The document discusses how project managers can adapt to agile methods. It begins by addressing common myths about agile project management and the stereotypes of project managers. It then discusses how the project manager role may change, focusing more on product ownership, collaboration with customers, and ensuring the highest priority features are delivered. The document emphasizes that agile embraces change and focuses on delivering working software over comprehensive documentation and responding to change rather than following a strict plan.
Implementing Test Automation: What a Manager Should Know
Decent test automation performance is no longer just an increased amount of script code. Learn all the ABCs of test automation.
Way to Agile - USTH
My presentation in Agile4U (Agile for University) program of HanoiScrum in 2013.
This presentation may have some customised content for University of Science and Technology of Ha Noi.
Automation testing
Introduction to We Application testing , need of automation , and tools that we use in Web Application testing
Continuous delivery
This document discusses the principles and benefits of continuous delivery. It emphasizes delivering valuable software to users as quickly as possible through early and continuous delivery. It recommends automating the software delivery process through practices like continuous integration, deployment pipelines, and feature flags to reduce risk and enable reliable, repeatable releases. Frequent integration and deployment allows for real project progress updates and quick recovery from any issues.
ATH2013-Unnat-MVP
The document discusses the concept of minimum viable product (MVP) and how it can be used to validate learning about customers with minimal effort. It defines MVP as the version that allows a team to collect the maximum amount of validated learning about customers with the least effort. The document outlines what MVP is and isn't, how to identify an MVP, and compares it to minimum marketable product. It also discusses using MVP in a loop of hypothesis, measurement, and experimentation and provides examples of notable MVPs.
How engineering practices help business
This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.
How to Reduce Time to Market Using Microsoft DevOps Solutions
Microsoft DevOps toolset replaces error-prone manual processes with automation for improved traceability and repeatable workflows.
Learn more about:
- The benefits of Continuous Integration practice
- Continuous Deployment as an accelerator to deliver high quality software
- How to use Visual Studio Team Services and Microsoft Azure to decrease rework and increase team productivity
Myths of Product Development
This document discusses common misconceptions in product development and proposes lean thinking alternatives. It addresses six prevailing practices: 1) high resource utilization improves performance, 2) large batches improve economics, 3) sticking to plans is best, 4) starting sooner finishes sooner, 5) more features increase customer liking, and 6) getting it right the first time is most successful. For each, it advocates limiting work in progress, incorporating customer feedback early and often through minimal viable products and experimentation, and accepting that plans will change and failure is part of the learning process. The key takeaway is to make information visible, quantify delays, introduce slack, focus on response over efficiency, use small batches with fast feedback, and treat plans and features
Bugday bkk-2014 nitisak-auto_perf
Nitisak Mooltreesri from DST Worldwide Services spoke about automated load testing for continuous delivery. He discussed how load testing is important to find bugs under high user loads. His company performs daily automated performance tests using simulation approaches to test incomplete systems cheaply and reliably. This helps reduce performance issues by providing early feedback and catching problems before deployment.
Adopting Scrum and Agile
Lessons learned from the use of the Scrum methodology at our Calgary office over the years. Presented to the rest of the company during a push for agile adoption by all our software groups.
How to Go Codeless for Automated Mobile App Testing
Find out the dos, don’ts and best ways to integrate codeless test automation in this webinar with Applause product director Cathy Huang.
My Customer Won't Accept Smaller Releases
Ignite talk at Lean Kanban North America 2013 on responding to the argument that customers won't accept smaller releases
Rapid deployment models for uPortal
Tom Freestone presented at the 2011 Jasig Conference on moving portal development to a continuous integration and delivery model. He discussed how traditional portal development led to errors and issues due to inconsistent environments across development, testing, staging and production. He advocated for empowering portal teams by enabling continuous integration, flexible and quick deployments, and treating the application as code with binaries, data and configuration managed in repositories. This would reduce errors, lower stress and allow anyone to deploy quickly.
From Dev and Ops to DevOps - reconfiguring the plane in flight.
The presentation describes how bitbrains is transforming from a traditional organisation towards a DevOps organisation while keeping the business running at the same time.
This presentation was given at the "Devops and the enterprise" meetup in Amsterdam on Jan 8th, 2014.
What the heck is Kanban? - CodeMash 2014
This document provides an overview of Kanban and how it was implemented at Hugsmiðjan, a software company in Iceland. It begins with basic Kanban principles like limiting work in progress and visualizing workflows. It then describes how Hugsmiðjan transitioned to Kanban over time, including establishing boards, templates and metrics to manage flow. Benefits included improved visibility, collaboration and reduced lead times, though challenges remained around process adherence and metrics use.
Preso #4
Our product, NoteStamp, is a Chrome extension that helps University of Michigan students easily annotate and take notes on lecture recordings. It allows students to bookmark important points in recordings and sync their notes to the timestamps. Unlike handwritten notes, NoteStamp lets users skip directly to saved bookmarks and view notes linked to specific points in recordings. Based on user feedback, future versions will integrate more seamlessly with lecture sites and allow exporting notes for review outside the extension.
Fundamentals of Agile
The document discusses fundamentals of agile development including the agile manifesto and its 12 principles. It emphasizes values such as individuals and interactions, working software, customer collaboration, and responding to change. It also discusses agile processes like Scrum and Kanban, continuous improvement through inspection and adaptation, and techniques like test-driven development, pair programming, and continuous integration to enable regular rapid feedback. Finally, it notes that while agile is popular, the real question is whether it will make teams more successful in delivering value to customers on time and under budget.
Top ten secret weapons for performance testing in an agile environment
This document outlines 10 secret weapons for performance testing in an agile environment. The secret weapons are: 1) Make performance explicit 2) Include performance testers in development teams 3) Base performance tests on customer requirements 4) Take a disciplined approach to experimentation and hypothesis testing 5) Start performance testing early in the development process 6) Iterate based on performance test results rather than just incrementally adding features 7) Automate all aspects of performance testing 8) Treat performance test code like any other code under test 9) Implement continuous performance testing 10) Get regular feedback on performance from stakeholders.
Continues Integration for Android
There are many tasks that need to be done. But why get bored by doing the exact same series of actions every time? Especially when a machine can do it faster and in a more reliable way! That's what incited us to automate the way we build, test, and deploy apps so we can focus on more creative tasks.
What's hot (20)
Agile Project Management: "How I Learned to Stop Worrying and Love Agile”
Agile Project Management: "How I Learned to Stop Worrying and Love Agile”
Implementing Test Automation: What a Manager Should Know
Implementing Test Automation: What a Manager Should Know
How to Reduce Time to Market Using Microsoft DevOps Solutions
How to Reduce Time to Market Using Microsoft DevOps Solutions
How to Go Codeless for Automated Mobile App Testing
How to Go Codeless for Automated Mobile App Testing
From Dev and Ops to DevOps - reconfiguring the plane in flight.
From Dev and Ops to DevOps - reconfiguring the plane in flight.
Top ten secret weapons for performance testing in an agile environment
Top ten secret weapons for performance testing in an agile environment
Viewers also liked
Test pyramid
The document discusses different types of software tests including unit tests, integration tests, service tests, and UI end-to-end tests. Unit tests check individual components, integration tests verify communication between components, service tests validate API requests and responses, and UI end-to-end tests simulate user interactions to check the full application. The document also provides an example of a student result service test response.
Inverting Test Pyramid - A First Hand Experience Report
Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.
Business Impact:
* Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.
* Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.
Reduced test execution time - Backend tests are much faster. Almost 7-10 times faster than UI Tests - improved build certification time.
* Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.
Details: http://confengine.com/agile-pune-2014/proposal/471/inverting-test-pyramid-a-first-hand-experience-report
Conference: http://pune.agileindia.org/
Build And Test Automation - Shortening the Feedback Loop
Agile teams embrace build and test automation to shorten the time between coding and testing feedback, gain productivity leverage, and lower the cost of change.
Explore the automation practices that Agile teams adopt.
Anand Bagmar - Behavior Driven Testing (BDT) in Agile
I delivered this talk in SiliconIndia's SoftTec 2012 on 14th July 2012. I introduce Behavior Driven Testing (BDT) with a couple of examples, the different ways of writing the tests in Imperative and Declarative style, the value proposition of BDT, and how BDT can help you build a very good safety net using Test Automation suite.
Inverting The Testing Pyramid
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.
Test Automation Pyramid
The Test Automation Pyramid is a useful model to help us understand and discuss automated testing efforts. Generally speaking it is a good practice to have lots of unit tests, fewer component integration tests, fewer API tests, and even fewer UI tests.
Viewers also liked (6)
Inverting Test Pyramid - A First Hand Experience Report
Inverting Test Pyramid - A First Hand Experience Report
Build And Test Automation - Shortening the Feedback Loop
Build And Test Automation - Shortening the Feedback Loop
Anand Bagmar - Behavior Driven Testing (BDT) in Agile
Anand Bagmar - Behavior Driven Testing (BDT) in Agile
Similar to Deliver anything, anywhere, anytime
Павел Чуняев - State of Continuous Delivery in 2015
Павел Чуняев - State of Continuous Delivery in 2015
#itspringby
https://www.youtube.com/watch?v=Q2XD9HnSzhk
Continuous everything
Key takeaways
- Continuous “everything” is at the heart of agile and devops
- Continuous activities result in faster delivery and higher quality
- Rapid feedback and practice are essential for confidence in your delivery process
View webinar recording - http://testhuddle.com/resource/continuous-everything/
Continuous Delivery Distilled
Matt Callanan takes the 15 chapters of the famous "Continuous Delivery" book by Jez Humble & Dave Farey and distills it down into 1 hour of convincing arguments, walking through the pieces involved to make it happen including cultural challenges, automated testing, automated deployment & deployment pipelines. Not sure how to get started with DevOps? Finding it hard to convince colleagues & managers that CD is the way forward? Matt has used this presentation to help facilitate enterprise-wide adoption of Continuous Delivery. Slides from a presentation given at DevOps Brisbane March 2014.
Continuous Development: Supporting a Release Model
This talk will explore whether Continuous Delivery as a methodology is applicable, even when the product delivery still requires a release model.
Backend Master | 3.4.1 Deploy - Deploy Automation
Backend Master | 3.4.1 Deploy - Deploy Automation
@author 유다슬
@date 18.07.08
# Study Curriculum : https://github.com/Backend-Masters/report
Introduction to continuous delivery
Continuous Delivery is a software development practice where code changes are automatically tested, built, and prepared for a release. The key principles are:
1) Make small, incremental code changes continuously that are always ready for production.
2) Automate testing, building, and deploying to reduce risk and make releases boring.
3) Use feature toggles to deploy incomplete features and control their rollout.
This allows software to be updated and released frequently in a sustainable way by catching issues early and improving quality. It is a cultural change that requires investment but provides benefits like faster feedback and the ability to respond quickly to demands.
Continuous Integration, Deploy, Test From Beginning To End 2014
Frank Cohen, CTO/Founder at Appvance, teaches developers and testers how to become more closely aligned with easily deployable and configurable tools such as Jenkins CI and performance testing platforms.
Learn how to:
* Merge Agile SDLC and Performance Testing
* Speed-up test operations by configuring Jenkins for automatic build, deploy, and tests
* Instantly identify functional and performance issues using Jenkins as a performance dashboard
* Use effective choices in Jenkins deployment – in the cloud, hosted, or in your datacenter
Dev ops != Dev+Ops
DevOps, sibling of Agile is born of the need to improve IT service delivery agility to the more stable environment.
DevOps movement emphasizes tearing the boundaries between makers (Development) & caretakers (Operations) of IT services/products.
CI/CD for mobile at HERE
This talk describes how we use a scaled approach for CI/CD. The system is set up for iOS and Android Apps but many of the concepts presented are applicable for any type of application. We will cover the different pipeline stages a change goes through, how we automate many levels of testing, treat our CI infrastructure as code, which key metrics we use and we track them on dashboards. All this demonstrates how we can get close to Continuous Delivery for platforms still ruled by App stores.
Testing in the new age of DevOps
- Introduction to DevOps.
- Glossary.
- Continuous testing.
- The DevOps lifecycle.
- Where does QA fit in DevOps.
- Test-Driven Development (TDD).
- References.
We thought we were doing continuous delivery and then...
Are you sure you are doing continuous delivery? Yeah right! We thought we were too. The journey to continuous delivery (CD) is long, winding and always evolving. Like with many things we thought we had achieved all we could with continuous delivery and then... our business model changed, and then...
Originally presented at QCon New York June 2016 https://qconnewyork.com/ny2016/ny2016/presentation/we-thought-we-were-doing-continuous-delivery-and-then.html
Road to Continuous Delivery - Wix.com
The document discusses Aviran Mordo's presentation on Wix's journey towards continuous delivery. Some key points:
- Wix has transitioned from traditional waterfall development to continuous delivery, deploying changes around 60 times per day.
- This was enabled by adopting DevOps practices like test-driven development, feature toggles, A/B testing, automated deployments, and monitoring.
- Tools like App-Info, New Relic, and custom deployment tools were crucial for implementing continuous delivery at Wix's scale across multiple data centers and cloud providers.
- Transitioning required cultural changes, empowering developers, and embracing risk and failure to improve continuously. Wix now develops and replaces infrastructure
what-is-devops.ppt
This document discusses DevOps, a methodology that combines software development (Dev) and IT operations (Ops). It describes how DevOps aims to improve collaboration between developers and operations teams to more quickly identify and solve problems, allowing for faster and more reliable software delivery. The document provides examples of how DevOps streamlines processes like continuous integration, delivery and deployment through automation and bringing the teams together into a single workflow.
Use Jenkins For Continuous Load Testing And Mobile Test Automation
The document discusses using Jenkins for continuous load testing and mobile test automation. It describes how Jenkins can be used to automate testing across sprints in an agile methodology. Specifically, it outlines how to leverage Jenkins to run functional tests continuously and repurpose those tests for performance and load testing. This helps ensure applications are thoroughly tested before each release.
NYC MeetUp 10.9
William Josephson is the co-founder of Solano Labs, which provides automated testing services. Solano Labs has helped several customers significantly reduce their testing times - for example, reducing tests that previously took 18 hours down to 13 minutes. Automated testing allows organizations to deploy code much more frequently and have fewer failures. It reduces costs by finding bugs quicker and allows engineers to make changes more freely.
Slow Down to Speed Up - Leveraging Quality to Enable Productivity and Speed w...
The document discusses how adopting quality practices can enable productivity and speed in software development. It argues that quality and speed are complementary, not opposing goals, and that taking time to implement quality measures like automated testing and continuous integration actually makes development faster overall by reducing bugs and technical debt. The document provides examples of how different organizations have evolved their quality and testing practices to fully integrate them into agile development teams and processes.
Shorten Business Life Cycle Using DevOps
This document discusses DevOps and continuous testing. It begins with defining DevOps as a process that increases communication between development and operations teams to automate and speed up software delivery. It then covers the benefits of DevOps like faster release cycles and time to market. Several case studies are presented showing how companies used DevOps and continuous testing to reduce testing time, increase coverage, and lower costs. The document concludes with a demo and opportunities for questions.
DevOps Overview in my own words
What is DevOps?
Why DevOps?
How DevOps works?
DevOps impacts in testing.
Continuous Delivery.
Continuous Integration.
Continuous Testing and Automated Deployment.
Dev/Test scenarios in DevOps world
Do you want a deep dive into the dev/test portion of DevOps and application lifecycle management (ALM)?
Do you want an overview of unit testing, functional UI testing and load testing?
Do you want to learn about continuous deployment?
Do you want to walk through how testers ensure that business value is delivered?
This session is for you.
Continuous Delivery: why ? where to start ? how to scale ?
This document provides an overview of continuous delivery and how to get started with it. It defines key terms like continuous integration, continuous delivery, and continuous deployment. It discusses the benefits of continuous delivery like delivering value faster and with higher quality. It then presents several maturity models for assessing an organization's continuous delivery capabilities. It provides recommendations for where to start the continuous delivery journey, such as focusing on automating deployments and environments first. Finally, it discusses challenges of scaling continuous delivery across large organizations.
Similar to Deliver anything, anywhere, anytime (20)
Павел Чуняев - State of Continuous Delivery in 2015
Павел Чуняев - State of Continuous Delivery in 2015
Continuous Development: Supporting a Release Model
Continuous Development: Supporting a Release Model
Continuous Integration, Deploy, Test From Beginning To End 2014
Continuous Integration, Deploy, Test From Beginning To End 2014
We thought we were doing continuous delivery and then...
We thought we were doing continuous delivery and then...
Use Jenkins For Continuous Load Testing And Mobile Test Automation
Use Jenkins For Continuous Load Testing And Mobile Test Automation
Slow Down to Speed Up - Leveraging Quality to Enable Productivity and Speed w...
Slow Down to Speed Up - Leveraging Quality to Enable Productivity and Speed w...
Continuous Delivery: why ? where to start ? how to scale ?
Continuous Delivery: why ? where to start ? how to scale ?
Recently uploaded
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.The Microsoft 365 Migration Tutorial For Beginner.pptx
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
"Choosing proper type of scaling", Olena Syrota
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Mutation Testing for Task-Oriented Chatbots
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
What is an RPA CoE? Session 1 – CoE Vision
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Dmitrii Kamaev, PhD
Senior Product Owner - QIAGEN
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
JavaLand 2024: Application Development Green Masterplan
My presentation slides I used at JavaLand 2024
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Recently uploaded (20)
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
The Microsoft 365 Migration Tutorial For Beginner.pptx
The Microsoft 365 Migration Tutorial For Beginner.pptx
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-Efficiency
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
JavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green Masterplan
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Deliver anything, anywhere, anytime
- 1. Deliver - Anything, Anywhere, Anytime - Poornima Sarangapani QA, Thoughtworks.
- 2. • Building, testing, and releasing software faster and more frequently. • Produce software in short cycles • Ensuring that the software can be reliably released at any time • Reduce the cost, time, and risk of delivering CD
- 3. Continuous delivery vs Continuous deployment
- 4. • IMVU, since 2009 (50 deployments/day) • Wealthfront, since 2010 • Etsy, since 2010 • DISQUS, since 2011 • Box, since 2013 • Hubspot, since 2013 (300 deployments/day) • Tesla and Adobe Continuous Deployment - Companies
- 5. How Does Continuous Delivery workHow Does Continuous Delivery Works
- 9. • The purpose of the deployment pipeline has three components: • Visibility • Feedback • Continually deploy Deployment Pipeline
- 10. No DownTime
- 11. RollBack
- 14. • Not a release time testing with bunch of features • Reduced Deployment Risk • Believable Progress -Improves customer satisfaction • User Feedback - building the right product • Improved product quality. Advantages
- 15. Q & AQ & A