Buddy CI/CI
•Download as PPTX, PDF•
0 likes•32 views
The document discusses principles of continuous delivery including building quality in from the start, automating as much as possible, keeping everything in version control, testing in a production-like environment, and keeping the delivery process simple and repeatable. It emphasizes automating tests, releasing software frequently to get early feedback, being data-driven, and continuously improving processes over time through a plan-do-study-act approach. Continuous delivery helps reduce errors, lower stress for teams, and get useful feedback to build the right features.
Report
Share
Report
Share
Recommended
How I learned to stop worrying and love to deploy
An internal discussion around the type of practices an organisation needs to adopt to be able to move to continuous deployments
Sprint. Don't Waterfall
The document discusses how to avoid "waterfalling" work during a sprint in Scrum. It recommends splitting stories into smaller tasks, identifying independent tasks early, and "swarming" to complete higher priority tasks first before moving to the next. This allows delivering items earlier and prevents bottlenecks at the end of sprints where everything needs to be tested and completed at once. Key principles are smaller batches, less work in progress, and more parallel work through collaboration within cross-functional teams.
Cf objective2014 testing-testingeverywhere
This document discusses software testing strategies and techniques. It introduces testing pyramids that prioritize unit testing and outlines approaches for testing different parts of an application stack, including ColdFusion code, JavaScript, and databases. Specific testing methodologies like test-driven development (TDD) and behavior-driven development (BDD) are also covered. The document provides links to additional sessions at a software conference on testing JavaScript and ColdFusion applications.
Moving From Staged To Pervasive Testing
A Keynote I have delivered to EuroSTAR 2014 and Test+Verification Conference.
How did we move from yearly releases to weekly releases and how did our testing change.
Put "fast" back in "fast feedback"
One of the cornerstones in Agile development is fast feedback. For engineering, "fast" means "instantly" or "in 5 minutes", not "tomorrow" or "this week". Your engineering practices should ensure that you can answer yes to most of the following questions:
- Do we get all test results in less than 5 minutes after a commit?
- Is our code coverage more than 75% for both front-end and back-end?
- Can we start exploratory testing in less than 15 minutes after a commit?
- Do all our tests pass more than 90% of our commits?
This talk will give you practical advice on how to get to "yes, we get fast feedback".
Real world dev ops
The document discusses real world DevOps practices based on the author's experience. It defines DevOps as not being a job or department but rather a value system of collaboration across teams to provide faster feedback and achieve business goals. The author provides "Don'ts" and "Do's" for DevOps, advising against silos between teams and different goals for Dev and Ops, and recommending providing self-service tools, constant cross-training, keeping systems simple, and automating processes. The overall message is that collaboration, feedback, and customer focus should be the highest priorities.
TLC2018 Shyam Sunder: Legoizing Testing
This document discusses an approach called "Legoizing Testing" which breaks testing into reusable "blocks" or components. It presents problems with traditional scripting approaches where changes require rewriting many steps. The Legoizing approach involves identifying atomic, reusable test blocks and allowing testers to assemble scripts by selecting relevant blocks. A demo of a Lego testing tool is provided, showing how it can generate scripts in minutes by selecting scenarios and matching blocks. Feedback indicates the tool has helped reduce scripting time and increased stakeholder satisfaction on one project. The presentation concludes by recommending that others identify reusable testing blocks and provide a self-service tool to build scripts from those blocks.
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In AgileHo Chi Minh City Software Testing Club
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Nhat Do, Vu Duong
Context-Driven Testing (CDT) rejects the notion of generalized “best practices” that apply to all projects, and instead accepts that different practices work best under different circumstances. The third principle of the seven defined in CDT states that people are the most important part of any project’s context. Less of a focus on processes and tools, with more emphasis on people and their collaboration empowers testers with the freedom to make choices about how best to do their job without following a restrictive plan.
In joining the game of workshop and some theory sharing in slides, you will a better understanding of Context-Driven Testing practices, principles and its benefits as well as know how is a nice Marriage of Agile and Context-Driven Testing.Recommended
How I learned to stop worrying and love to deploy
An internal discussion around the type of practices an organisation needs to adopt to be able to move to continuous deployments
Sprint. Don't Waterfall
The document discusses how to avoid "waterfalling" work during a sprint in Scrum. It recommends splitting stories into smaller tasks, identifying independent tasks early, and "swarming" to complete higher priority tasks first before moving to the next. This allows delivering items earlier and prevents bottlenecks at the end of sprints where everything needs to be tested and completed at once. Key principles are smaller batches, less work in progress, and more parallel work through collaboration within cross-functional teams.
Cf objective2014 testing-testingeverywhere
This document discusses software testing strategies and techniques. It introduces testing pyramids that prioritize unit testing and outlines approaches for testing different parts of an application stack, including ColdFusion code, JavaScript, and databases. Specific testing methodologies like test-driven development (TDD) and behavior-driven development (BDD) are also covered. The document provides links to additional sessions at a software conference on testing JavaScript and ColdFusion applications.
Moving From Staged To Pervasive Testing
A Keynote I have delivered to EuroSTAR 2014 and Test+Verification Conference.
How did we move from yearly releases to weekly releases and how did our testing change.
Put "fast" back in "fast feedback"
One of the cornerstones in Agile development is fast feedback. For engineering, "fast" means "instantly" or "in 5 minutes", not "tomorrow" or "this week". Your engineering practices should ensure that you can answer yes to most of the following questions:
- Do we get all test results in less than 5 minutes after a commit?
- Is our code coverage more than 75% for both front-end and back-end?
- Can we start exploratory testing in less than 15 minutes after a commit?
- Do all our tests pass more than 90% of our commits?
This talk will give you practical advice on how to get to "yes, we get fast feedback".
Real world dev ops
The document discusses real world DevOps practices based on the author's experience. It defines DevOps as not being a job or department but rather a value system of collaboration across teams to provide faster feedback and achieve business goals. The author provides "Don'ts" and "Do's" for DevOps, advising against silos between teams and different goals for Dev and Ops, and recommending providing self-service tools, constant cross-training, keeping systems simple, and automating processes. The overall message is that collaboration, feedback, and customer focus should be the highest priorities.
TLC2018 Shyam Sunder: Legoizing Testing
This document discusses an approach called "Legoizing Testing" which breaks testing into reusable "blocks" or components. It presents problems with traditional scripting approaches where changes require rewriting many steps. The Legoizing approach involves identifying atomic, reusable test blocks and allowing testers to assemble scripts by selecting relevant blocks. A demo of a Lego testing tool is provided, showing how it can generate scripts in minutes by selecting scenarios and matching blocks. Feedback indicates the tool has helped reduce scripting time and increased stakeholder satisfaction on one project. The presentation concludes by recommending that others identify reusable testing blocks and provide a self-service tool to build scripts from those blocks.
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In AgileHo Chi Minh City Software Testing Club
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Nhat Do, Vu Duong
Context-Driven Testing (CDT) rejects the notion of generalized “best practices” that apply to all projects, and instead accepts that different practices work best under different circumstances. The third principle of the seven defined in CDT states that people are the most important part of any project’s context. Less of a focus on processes and tools, with more emphasis on people and their collaboration empowers testers with the freedom to make choices about how best to do their job without following a restrictive plan.
In joining the game of workshop and some theory sharing in slides, you will a better understanding of Context-Driven Testing practices, principles and its benefits as well as know how is a nice Marriage of Agile and Context-Driven Testing. Usa prácticas de integración continua y sobrevive para luchar otro día.
The document discusses continuous integration (CI) and continuous delivery (CD) practices. It defines CI as ensuring good health of the codebase through frequent commits and automated testing. CD is defined as reliably releasing new features to market frequently through deployment pipelines. The document provides benefits of CI/CD like improved quality and risk mitigation. It also gives best practices and lessons learned from implementing CI/CD in an e-commerce platform, such as knowing the product, not changing everything at once, being pragmatic, trusting the process, and making everyone responsible.
Teamleader testcon 2019
Testers, do you find yourself still siloed even after breaking down the “walls” between development and testing? Are you in a hole of never-ending test creation and maintenance, removing you from focusing on user experience? Does ad-hoc exploratory testing still happen because your tests aren’t stable enough to test the app before it gets to production?
When your team starts to adopt agile and DevOps development practices, how do you scale testing to keep up with higher release frequencies? Test automation is a big part of the solution. But beware that you’re doing it the wrong way.
In this talk I will explain how to reverse the negative impacts brought about from common – but not necessarily “good” – practices around automation tooling and QA hiring practices. I will talk about what changes you need to make to win back more time to develop and implement your test strategy. I will elevate your testing strategy from “surviving” to “thriving” in DevOps.
TDD
This document discusses the benefits of test-driven development (TDD) and unit testing over traditional approaches to coding without tests. It notes that coding without tests can lead to bugs that are difficult to fix and applications that are hard to update. TDD involves writing tests before production code to specify functionality, then writing just enough code to pass each test. This approach prevents bugs and ensures code quality and performance while improving maintainability. The key principle of TDD outlined is to not write any production code without a failing test first.
Software Quality for Developers
This document discusses software quality assurance and control for small development teams. It defines the differences between quality assurance, which ensures the development process is efficient, and quality control, which ensures the product meets requirements. Quality control has two components: validation, which checks the right product is built, and verification, which checks the product is built correctly. Validation involves getting complete requirements from customers and defining the problem being solved. Verification uses testing strategies like unit, integration, and system testing following a V-model approach. The document provides tips for testing, including change-related, integration, and ensuring independence between development and testing roles.
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...Ho Chi Minh City Software Testing Club
You want to integrate skilled testing and development work. But how do you accomplish this without developers accidentally subverting the testing process or testers becoming an obstruction? Efficient, deep testing requires “critical distance” from the development process, commitment and planning to build a testable product, dedication to uncovering the truth, responsiveness among team members, and often a skill set that developers alone—or testers alone—do not ordinarily possess. James Bach presents a model—a redesign of the famous Agile Testing Quadrants that distinguished between business vs. technical facing tests and supporting vs. critiquing―that frames these dynamics and helps teams think through the nature of development and testing roles and how they might blend, conflict, or support each other on an Agile project. James includes a brief discussion of the original Agile Testing Quadrants model, which the presenters believe has created much confusion about the role of testing in Agile.Converging the team
Just a few slides about how teams should act together to shorten feedback cycles. Presented in AgileJKL Meetup about Testing.
Stc chandan patary_ua_testing _ stc
This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.
First steps in Test Driven Development
Slides from a presentation given by Simon Lynch to a meeting of IIBA UK's South West branch on 15 March 2018.
Presentasjon til temakveld for Visma Consulting:Specification by example med ...
Presentasjon til temakveld for Visma Consulting.
Om temaet:
Specification by example er relevant for testere, arkitekter og utviklere. Det handler om å unngå funksjonelle gap og inkonsistens mellom spesifikasjoner og tester. Ved å utvide spesifikasjoner med eksempler lager man en ”single source of truth” for både utvikling og test, og ved å automatisere spesifikasjonene muliggjør man automatisert akseptansetestin
Meetup-Transition2AgileSHARE
The document provides 10 tips for conquering an agile transition: 1) Make a compelling case to business, 2) Invest in training for the entire team, 3) Make the transition everyone's problem by forming a transition team, 4) Use an agile approach to transition by applying scrum, 5) Document transition decisions, 6) Plan for distractions and events, 7) Bend rules judiciously, 8) Empower the transition team, 9) Anticipate staggered resistance to change, and 10) Set careful expectations balancing optimism and fear. The tips are based on the author's experience leading an agile transition at Oracle Corporation for a distributed team developing complex products.
Scrum master motivation role
This document discusses the role of a Scrum Master in motivating teams. It describes the author's background and experiences in quality assurance and test automation. The author believes that motivation relates to happiness, success, and winning for teams. As a Scrum Master, ways to motivate teams include leading by example, continuous improvements, mentoring the team, and focusing standups on progress rather than socializing. Motivation levels will fluctuate over time, so the Scrum Master should stay positive and encourage the team without trying to do everything themselves. Artifacts and planning activities should be optimized for engagement, such as using planning poker cards and providing food.
Agille Testing Meetup 1
This document summarizes the agenda and discussion at an Agile Testing meetup group. It introduces the purpose of the group as a place for testers to share experiences and learn new skills in Agile Testing. Key topics discussed include the benefits of testing earlier in the development cycle using automated tools. A demonstration was given of a keyword driven web testing solution using WebDriver and FitNesse. Attendees then shared challenges with testing in Agile and ideas for future meetup activities.
Effective QA in Scrum
This document discusses how testers can be effective in agile teams using Scrum. It begins by distinguishing quality assurance (QA) from quality control (QC) and outlines how testers can focus on helping teams achieve "done" by collaborating in backlog grooming and preventing bugs. The document recommends that testers work with rather than against developers by pairing, writing automated tests, and participating in code reviews. It also advocates for exploratory testing and emphasizes the importance of collaboration between testers, developers, analysts and product owners.
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Scrum Roles : Scrum Master | Product Owner |Team
The document describes the three core Scrum roles - Product Owner, Scrum Master, and Development Team - and two ancillary roles. The Product Owner represents stakeholders and ensures the product meets business needs. The Scrum Master coaches the team and removes impediments to workflow. The multi-functional Development Team is self-organizing and completes the work. The ancillary roles of customers and management provide feedback but are not directly involved in sprints.
From Zero to Agile: The Learnings of a First-time Quality Analyst
Coming from a predominantly traditional software development background, it is amazing to see the impact Agile Methodologies have on the processes, techniques, timelines, resources and strategies used to build software. This is especially true for the software testing practice, which has traditionally been treated as a gatekeeper role whose core value was quarantined to the later stages of a product’s lifecycle. However with the advent of Agile, the software testing practice has been totally turned around.
These are the slides for the talk I gave at Agile Brazil 2014 - based on the transition to Agile in the field of Software Quality Assurance.
Among the key takeaways are the proven notions that with the new Agile Approach:
- Testing and core development cannot be detached from one another.
- The quality of the end product is really the shared responsibly of the entire team
- Quality must be built in right from the start
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of TestingHo Chi Minh City Software Testing Club
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Copeland
Over the years writers have defined testing as a process of finding, a process of evaluating, a process of measuring, a process of improving. For a quarter of a century we as testers have been focused on the internal process of testing, while generally disregarding its real purpose. The real purpose of testing is to create information. James Bach nailed it when he wrote, “The ultimate reason testers exist is to provide information that others on the project use to create things of value.” That is why testing exists — to provide information of value. So, when managers complain that testing “costs too much” perhaps they are really trying to say, “I’m not getting enough valuable information to justify the cost of testing.” When testers say “my management doesn’t see the value in our work” perhaps they are really trying to say, “My management doesn’t value the information I’m providing to them.” To prove our worth, to increase the value of testing, we must first focus on testing’s purpose — providing valuable information — not its process. Join Lee as he discusses why quantifying the value of testing is difficult work — perhaps that’s why we concentrate so much on testing process—that’s much easier. But until we do this difficult work, until we prove our worth through quantifying our contribution, we should expect the bombardments to continue.Process under scale david subar
Scaling processes at companies requires separating infrastructure from development to allow dynamic and independent growth. Following Conway's Law, organizational structures will copy communication flows, so processes need separation of concerns between product engineering teams, infrastructure, and DevOps. Measurement of impact, uptime, and release cycles is also important for evaluating scaling effectiveness.
Practical Programming It Awareness Advocacy
Scrum is an agile framework for managing projects, especially software development. It uses short iterations called sprints to rapidly develop features. At the start of each sprint, a product backlog prioritizes features and the team selects what they can complete. Daily stand-up meetings help the team track progress and remove impediments. At the end of each sprint, working software is demonstrated for feedback before beginning the next sprint. Agile practices like Scrum aim to adapt quickly to changing requirements through transparency, inspection, and adaptation.
Introduction to CI/CD
This document provides an introduction to CI/CD (continuous integration/continuous delivery) processes. It defines key terms, describes how CI/CD works by automating the integration, building, testing and deployment of code changes. The benefits are listed as reducing errors, improving quality and enabling faster releases. Examples are given of tools that can be used and best practices like automating builds, testing in production-like environments and keeping everything in source control. A case study of Verizon's prepaid mobile app deployment is presented to illustrate how feature branches are merged after passing tests.
Developing Quality Products Quickly through a Culture of CI/CD
Teams are stuck at one to two week releases. Some invest in tech, others in culture. In order for teams to speed up their delivery teams must have alignment across culture, practices, and technology. Companies and teams that invest in continuous cultures will reduce the chances of being disrupted by competition.
Deploying ML models to production (frequently and safely) - PYCON 2018
1. The document discusses principles and practices for reliably and repeatedly deploying machine learning models from development to production.
2. It emphasizes the importance of frequent and safe deployment to iteratively improve models and correct any biases, and addresses challenges like deploying models that impact lives.
3. The talk provides an overview of continuous delivery principles for machine learning and demonstrates an automated pipeline for testing, versioning, and deploying models.
More Related Content
What's hot
Usa prácticas de integración continua y sobrevive para luchar otro día.
The document discusses continuous integration (CI) and continuous delivery (CD) practices. It defines CI as ensuring good health of the codebase through frequent commits and automated testing. CD is defined as reliably releasing new features to market frequently through deployment pipelines. The document provides benefits of CI/CD like improved quality and risk mitigation. It also gives best practices and lessons learned from implementing CI/CD in an e-commerce platform, such as knowing the product, not changing everything at once, being pragmatic, trusting the process, and making everyone responsible.
Teamleader testcon 2019
Testers, do you find yourself still siloed even after breaking down the “walls” between development and testing? Are you in a hole of never-ending test creation and maintenance, removing you from focusing on user experience? Does ad-hoc exploratory testing still happen because your tests aren’t stable enough to test the app before it gets to production?
When your team starts to adopt agile and DevOps development practices, how do you scale testing to keep up with higher release frequencies? Test automation is a big part of the solution. But beware that you’re doing it the wrong way.
In this talk I will explain how to reverse the negative impacts brought about from common – but not necessarily “good” – practices around automation tooling and QA hiring practices. I will talk about what changes you need to make to win back more time to develop and implement your test strategy. I will elevate your testing strategy from “surviving” to “thriving” in DevOps.
TDD
This document discusses the benefits of test-driven development (TDD) and unit testing over traditional approaches to coding without tests. It notes that coding without tests can lead to bugs that are difficult to fix and applications that are hard to update. TDD involves writing tests before production code to specify functionality, then writing just enough code to pass each test. This approach prevents bugs and ensures code quality and performance while improving maintainability. The key principle of TDD outlined is to not write any production code without a failing test first.
Software Quality for Developers
This document discusses software quality assurance and control for small development teams. It defines the differences between quality assurance, which ensures the development process is efficient, and quality control, which ensures the product meets requirements. Quality control has two components: validation, which checks the right product is built, and verification, which checks the product is built correctly. Validation involves getting complete requirements from customers and defining the problem being solved. Verification uses testing strategies like unit, integration, and system testing following a V-model approach. The document provides tips for testing, including change-related, integration, and ensuring independence between development and testing roles.
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...Ho Chi Minh City Software Testing Club
You want to integrate skilled testing and development work. But how do you accomplish this without developers accidentally subverting the testing process or testers becoming an obstruction? Efficient, deep testing requires “critical distance” from the development process, commitment and planning to build a testable product, dedication to uncovering the truth, responsiveness among team members, and often a skill set that developers alone—or testers alone—do not ordinarily possess. James Bach presents a model—a redesign of the famous Agile Testing Quadrants that distinguished between business vs. technical facing tests and supporting vs. critiquing―that frames these dynamics and helps teams think through the nature of development and testing roles and how they might blend, conflict, or support each other on an Agile project. James includes a brief discussion of the original Agile Testing Quadrants model, which the presenters believe has created much confusion about the role of testing in Agile.Converging the team
Just a few slides about how teams should act together to shorten feedback cycles. Presented in AgileJKL Meetup about Testing.
Stc chandan patary_ua_testing _ stc
This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.
First steps in Test Driven Development
Slides from a presentation given by Simon Lynch to a meeting of IIBA UK's South West branch on 15 March 2018.
Presentasjon til temakveld for Visma Consulting:Specification by example med ...
Presentasjon til temakveld for Visma Consulting.
Om temaet:
Specification by example er relevant for testere, arkitekter og utviklere. Det handler om å unngå funksjonelle gap og inkonsistens mellom spesifikasjoner og tester. Ved å utvide spesifikasjoner med eksempler lager man en ”single source of truth” for både utvikling og test, og ved å automatisere spesifikasjonene muliggjør man automatisert akseptansetestin
Meetup-Transition2AgileSHARE
The document provides 10 tips for conquering an agile transition: 1) Make a compelling case to business, 2) Invest in training for the entire team, 3) Make the transition everyone's problem by forming a transition team, 4) Use an agile approach to transition by applying scrum, 5) Document transition decisions, 6) Plan for distractions and events, 7) Bend rules judiciously, 8) Empower the transition team, 9) Anticipate staggered resistance to change, and 10) Set careful expectations balancing optimism and fear. The tips are based on the author's experience leading an agile transition at Oracle Corporation for a distributed team developing complex products.
Scrum master motivation role
This document discusses the role of a Scrum Master in motivating teams. It describes the author's background and experiences in quality assurance and test automation. The author believes that motivation relates to happiness, success, and winning for teams. As a Scrum Master, ways to motivate teams include leading by example, continuous improvements, mentoring the team, and focusing standups on progress rather than socializing. Motivation levels will fluctuate over time, so the Scrum Master should stay positive and encourage the team without trying to do everything themselves. Artifacts and planning activities should be optimized for engagement, such as using planning poker cards and providing food.
Agille Testing Meetup 1
This document summarizes the agenda and discussion at an Agile Testing meetup group. It introduces the purpose of the group as a place for testers to share experiences and learn new skills in Agile Testing. Key topics discussed include the benefits of testing earlier in the development cycle using automated tools. A demonstration was given of a keyword driven web testing solution using WebDriver and FitNesse. Attendees then shared challenges with testing in Agile and ideas for future meetup activities.
Effective QA in Scrum
This document discusses how testers can be effective in agile teams using Scrum. It begins by distinguishing quality assurance (QA) from quality control (QC) and outlines how testers can focus on helping teams achieve "done" by collaborating in backlog grooming and preventing bugs. The document recommends that testers work with rather than against developers by pairing, writing automated tests, and participating in code reviews. It also advocates for exploratory testing and emphasizes the importance of collaboration between testers, developers, analysts and product owners.
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Scrum Roles : Scrum Master | Product Owner |Team
The document describes the three core Scrum roles - Product Owner, Scrum Master, and Development Team - and two ancillary roles. The Product Owner represents stakeholders and ensures the product meets business needs. The Scrum Master coaches the team and removes impediments to workflow. The multi-functional Development Team is self-organizing and completes the work. The ancillary roles of customers and management provide feedback but are not directly involved in sprints.
From Zero to Agile: The Learnings of a First-time Quality Analyst
Coming from a predominantly traditional software development background, it is amazing to see the impact Agile Methodologies have on the processes, techniques, timelines, resources and strategies used to build software. This is especially true for the software testing practice, which has traditionally been treated as a gatekeeper role whose core value was quarantined to the later stages of a product’s lifecycle. However with the advent of Agile, the software testing practice has been totally turned around.
These are the slides for the talk I gave at Agile Brazil 2014 - based on the transition to Agile in the field of Software Quality Assurance.
Among the key takeaways are the proven notions that with the new Agile Approach:
- Testing and core development cannot be detached from one another.
- The quality of the end product is really the shared responsibly of the entire team
- Quality must be built in right from the start
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of TestingHo Chi Minh City Software Testing Club
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Copeland
Over the years writers have defined testing as a process of finding, a process of evaluating, a process of measuring, a process of improving. For a quarter of a century we as testers have been focused on the internal process of testing, while generally disregarding its real purpose. The real purpose of testing is to create information. James Bach nailed it when he wrote, “The ultimate reason testers exist is to provide information that others on the project use to create things of value.” That is why testing exists — to provide information of value. So, when managers complain that testing “costs too much” perhaps they are really trying to say, “I’m not getting enough valuable information to justify the cost of testing.” When testers say “my management doesn’t see the value in our work” perhaps they are really trying to say, “My management doesn’t value the information I’m providing to them.” To prove our worth, to increase the value of testing, we must first focus on testing’s purpose — providing valuable information — not its process. Join Lee as he discusses why quantifying the value of testing is difficult work — perhaps that’s why we concentrate so much on testing process—that’s much easier. But until we do this difficult work, until we prove our worth through quantifying our contribution, we should expect the bombardments to continue.Process under scale david subar
Scaling processes at companies requires separating infrastructure from development to allow dynamic and independent growth. Following Conway's Law, organizational structures will copy communication flows, so processes need separation of concerns between product engineering teams, infrastructure, and DevOps. Measurement of impact, uptime, and release cycles is also important for evaluating scaling effectiveness.
Practical Programming It Awareness Advocacy
Scrum is an agile framework for managing projects, especially software development. It uses short iterations called sprints to rapidly develop features. At the start of each sprint, a product backlog prioritizes features and the team selects what they can complete. Daily stand-up meetings help the team track progress and remove impediments. At the end of each sprint, working software is demonstrated for feedback before beginning the next sprint. Agile practices like Scrum aim to adapt quickly to changing requirements through transparency, inspection, and adaptation.
What's hot (19)
Usa prácticas de integración continua y sobrevive para luchar otro día.
Usa prácticas de integración continua y sobrevive para luchar otro día.
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...
The New Agile Testing Quadrants: Bringing Skilled Testers and Developers Toge...
Presentasjon til temakveld for Visma Consulting:Specification by example med ...
Presentasjon til temakveld for Visma Consulting:Specification by example med ...
From Zero to Agile: The Learnings of a First-time Quality Analyst
From Zero to Agile: The Learnings of a First-time Quality Analyst
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing
Similar to Buddy CI/CI
Introduction to CI/CD
This document provides an introduction to CI/CD (continuous integration/continuous delivery) processes. It defines key terms, describes how CI/CD works by automating the integration, building, testing and deployment of code changes. The benefits are listed as reducing errors, improving quality and enabling faster releases. Examples are given of tools that can be used and best practices like automating builds, testing in production-like environments and keeping everything in source control. A case study of Verizon's prepaid mobile app deployment is presented to illustrate how feature branches are merged after passing tests.
Developing Quality Products Quickly through a Culture of CI/CD
Teams are stuck at one to two week releases. Some invest in tech, others in culture. In order for teams to speed up their delivery teams must have alignment across culture, practices, and technology. Companies and teams that invest in continuous cultures will reduce the chances of being disrupted by competition.
Deploying ML models to production (frequently and safely) - PYCON 2018
1. The document discusses principles and practices for reliably and repeatedly deploying machine learning models from development to production.
2. It emphasizes the importance of frequent and safe deployment to iteratively improve models and correct any biases, and addresses challenges like deploying models that impact lives.
3. The talk provides an overview of continuous delivery principles for machine learning and demonstrates an automated pipeline for testing, versioning, and deploying models.
Continuous Testing in DevOps
This document provides an overview of continuous testing in DevOps presented by Michael Hackett of LogiGear Corporation. It discusses what DevOps is and how testing fits into the continuous delivery pipeline. It emphasizes the need for testing at every step of development and deployment through test automation. It also provides examples of challenges companies face in implementing continuous testing and DevOps practices.
Deploying ML models to production (frequently and safely) - PYCON 2018
1. The document discusses principles and practices for reliably and repeatedly deploying machine learning models from development to production.
2. It recommends adopting continuous delivery practices like automating environment setup, implementing a testing pyramid, and setting up continuous integration and delivery pipelines to enable frequent, safe model iterations.
3. The talk provides demonstrations of these techniques and emphasizes the importance of cross-functional teams, starting simply, and continuously improving data and processes.
How to test a Mainframe Application
This document provides an overview of testing methods for mainframe applications. It discusses how testing needs have changed from the past where testing involved examining batch job outputs or online screen outputs, to modern approaches like test automation, virtualization, and DevOps. It covers different levels of testing maturity and factors to consider when planning tests. Black box and white box testing techniques are described, such as model-based testing, use case testing, and debugging. The presentation emphasizes the importance of testing to ensure stability, reliability, and compliance with changing requirements.
Deploying Fearlessly in a Continuous World
The document discusses techniques for continuously deploying software updates including automated testing, staged releases, blue-green deployments, and feature flags. It provides examples of how Optimizely uses these techniques including feature flags for A/B tests and staged rollouts. Best practices are outlined such as regularly reviewing flags to avoid technical debt, having a code ownership strategy, employing proper testing and QA, and embracing feature flag-driven development.
DevTestOps
This document provides an overview of DevTestOps. It begins with defining DevTestOps as bringing together DevOps principles with a focus on quality assurance. It discusses key aspects like risk appetites, strategic objectives, paths of communication, and testing practices at different stages. These include unit, integration, end-to-end testing as well as monitoring, logging and testing in production. It emphasizes implementing testing practices throughout the DevOps pipeline and describes different types of tests within a DevOps process like orchestration testing. The document aims to help understand where testing fits in DevOps and how to become a competent DevTestOps team member.
Drive Continuous Delivery With Continuous Testing
Silos. Lack of visibility. Some agile teams… some not. Manual handoffs. Bottlenecks.
This summer, it’s time to get outside (your old processes) and take some time off (your application release cycle). Take back your weekends and spend more time by the pool. We’ll show you how to automate, orchestrate, and facilitate continuous everything – and that includes continuous testing – one of the biggest bottlenecks of all.
You’ll learn how to:
Automatically shift quality left: Orchestrate and automate testing in every phase of the SDLC with automated promotion and feedback loops
Accelerate testing in the cloud: Test web and mobile apps in parallel – achieve up to 10X improvement in testing time. Use tools of choice while optimizing every aspect of your complex, interdependent multi-application pipelines.
Get started in less than 1 hour…. and for free! Achieve truly automated, continuous delivery (including continuous testing!!!) in the cloud with CA and Sauce Labs.
Try Continuous Delivery Director free:
https://cddirector.io/#/home
Try Sauce Labs free:
https://saucelabs.com/
Devops, Secops, Opsec, DevSec *ops *.* ?
This document discusses the DevOps movement and related concepts. It provides background on how development and operations teams historically worked separately ("Devs vs Ops") and the problems that caused. DevOps aims to break down barriers between teams through practices like automation, continuous integration/delivery, infrastructure as code, and collaboration between teams from the beginning of a project. The document outlines problems DevOps aims to solve and gives examples of tools and approaches for bringing development and operations cultures together.
NextBuild 2015 - Swimming upstream in the container revolution
Bert Jan Schrijver presented on Malmberg's journey to continuous delivery using open source tools and cloud services. Malmberg is an educational publisher that builds e-learning applications using Java, Vert.x, AngularJS and MongoDB on Amazon cloud services. They faced issues with slow development and operations communication and difficult production problem analysis using a traditional model. To address this, Malmberg established an expert DevOps team, defined key principles like keeping the master branch releasable at all times and managing all automation through Jenkins, and overcame challenges like gaining developer skills and hitting AWS limits to achieve benefits like increased agility, availability and cost reductions.
Software Development 2020 - Swimming upstream in the container revolution
Bert Jan Schrijver presented on Malmberg's journey to continuous delivery using open source tools and cloud services. Malmberg is an educational publisher that builds e-learning applications using Java, Vert.x, AngularJS and MongoDB on Amazon cloud services. They faced issues with slow development and operations communication and difficult production problem analysis using a traditional model. To address this, Malmberg established an expert DevOps team, defined key principles like keeping the master branch releasable at all times and managing all processes through Jenkins, and overcame challenges like gaining developer skills and infrastructure limits in transitioning to a self-service continuous delivery model. This approach improved agility, availability, cost reduction and problem resolution for Mal
Swimming upstream in the container revolution
Bert Jan Schrijver presented on Malmberg's journey to continuous delivery using open source tools and cloud services. Malmberg is an educational publisher that builds e-learning applications using Java, Vert.x, AngularJS and MongoDB on Amazon cloud services. They faced issues with slow development and operations communication and difficult production problem analysis using a traditional model. To address this, Malmberg established an expert DevOps team, defined key principles like keeping the master branch releasable at all times and managing all automation through Jenkins, and overcame challenges like gaining developer skills and hitting AWS limits to achieve benefits like increased agility, availability and cost reductions.
JavaOne 2015 - Swimming upstream in the container revolution
Bert Jan Schrijver discusses Malmberg's transition from traditional operations to a containerless continuous delivery model using DevOps principles. Some key challenges included cultural resistance to change, infrastructure limits with Amazon, and ensuring proper testing environments. The approach established expert teams, defined clear principles like infrastructure as code and no downtime, and benefited the business through increased agility, availability, and cost reductions. Areas of ongoing focus include monitoring, performance and security testing, and automated resilience testing.
Test Driven Development & CI/CD
This document provides an overview of test driven development (TDD), continuous integration (CI), continuous delivery (CD) and continuous deployment. It defines TDD as writing tests before code to guide development. CI involves integrating code into a shared repository daily and automating builds and testing. CD allows software to be released to production at any time if all tests pass. Continuous deployment automatically deploys software to production whenever changes are merged into the main branch. The document discusses benefits like higher quality, faster delivery and flexibility, and recommends automating everything and having developers and operations work together.
Java Forum Nord 2015 - Swimming upstream in the container revolution
Bert Jan Schrijver discusses how educational publisher Malmberg transitioned from a traditional operations model to a container-based continuous delivery model. Key points include establishing expert DevOps teams, defining principles like keeping the master branch releasable at all times and implementing infrastructure as code, and addressing challenges like cultural resistance to change and ensuring availability without depending on external operations experts. Benefits of the new approach include increased agility, continuity, and cost reductions through higher levels of automation and monitoring.
Geecon Microservices 2015 - Swimming upstream in the container revolution
Bert Jan Schrijver presented on Malmberg's transition to containerless continuous delivery. Key points include:
1) Malmberg faced issues with slow communication between development and operations due to differences in infrastructure and culture.
2) They established an expert DevOps team and defined 10 principles to guide their approach, such as ensuring the master branch is always releasable and using infrastructure as code.
3) Challenges in the transition included resistance to change and scaling infrastructure limits. Lessons focused on communication, automation, and giving teams freedom.
4) Benefits of the new approach included increased agility, availability, and cost reductions through automation and scaling. The presentation concluded with ideas
Devoxx BE 2015 - Swimming upstream in the container revolution
Bert Jan Schrijver discusses Malmberg's transition from traditional operations to a DevOps model with container-based continuous delivery. Key challenges included slow communication between development and operations, difficulty analyzing production issues, and long release cycles. Malmberg addressed this by building a dedicated DevOps team, defining principles like infrastructure as code and no downtime updates, and automating testing, builds, deployments and monitoring. This has led to benefits like increased agility, availability, cost savings and faster problem solving for Malmberg.
EuregJUG 2016-01-07 - Swimming upstream in the container revolution
Malmberg, an educational publisher, wanted to improve the speed and efficiency of releasing new features. They transitioned to a container-based continuous delivery model where development and operations teams work together through all stages of the product lifecycle. Key principles of their approach include having an automatically releasable master branch, extensive automated testing of all code changes, and treating infrastructure as code. This has led to benefits like increased agility through faster release cycles and availability through auto-scaling and proactive monitoring.
CI/CD and automated Test
This document discusses CI/CD pipelines and automated testing. It defines what a CI/CD pipeline is and provides a typical pipeline structure. It then discusses characteristics of a good pipeline, including speed, accuracy, reliability and comprehension. The document also discusses different types of automated tests like unit tests, integration tests and end-to-end tests. It introduces the test automation pyramid and emphasizes building a foundation of unit tests to enable quality and speed. Finally, it discusses challenges with automated testing like maintainability and generating test suites.
Similar to Buddy CI/CI (20)
Developing Quality Products Quickly through a Culture of CI/CD
Developing Quality Products Quickly through a Culture of CI/CD
Deploying ML models to production (frequently and safely) - PYCON 2018
Deploying ML models to production (frequently and safely) - PYCON 2018
Deploying ML models to production (frequently and safely) - PYCON 2018
Deploying ML models to production (frequently and safely) - PYCON 2018
NextBuild 2015 - Swimming upstream in the container revolution
NextBuild 2015 - Swimming upstream in the container revolution
Software Development 2020 - Swimming upstream in the container revolution
Software Development 2020 - Swimming upstream in the container revolution
JavaOne 2015 - Swimming upstream in the container revolution
JavaOne 2015 - Swimming upstream in the container revolution
Java Forum Nord 2015 - Swimming upstream in the container revolution
Java Forum Nord 2015 - Swimming upstream in the container revolution
Geecon Microservices 2015 - Swimming upstream in the container revolution
Geecon Microservices 2015 - Swimming upstream in the container revolution
Devoxx BE 2015 - Swimming upstream in the container revolution
Devoxx BE 2015 - Swimming upstream in the container revolution
EuregJUG 2016-01-07 - Swimming upstream in the container revolution
EuregJUG 2016-01-07 - Swimming upstream in the container revolution
Recently uploaded
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
20 Comprehensive Checklist of Designing and Developing a Website
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Building RAG with self-deployed Milvus vector database and Snowpark Container...
This talk will give hands-on advice on building RAG applications with an open-source Milvus database deployed as a docker container. We will also introduce the integration of Milvus with Snowpark Container Services.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Recently uploaded (20)
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Building RAG with self-deployed Milvus vector database and Snowpark Container...
Building RAG with self-deployed Milvus vector database and Snowpark Container...
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Buddy CI/CI
- 2. ● About me ● About us ● Testing and Delivery (demo) ● Data driven development ● Q & A Agenda
- 4. About Buddy ● CI/CD as a service ● > 10k users daily from 72 countries
- 5. Build, TEST, deploy, MEASURE and REPEAT
- 6. Build quality in testing is not a phase. Testing is not the domain of testers. 1/7 quality
- 7. Automate everything almost everything. There are same things it is impossible to automate. 2/7 automation
- 8. Git branching successful model https://nvie.com/posts/a-successful-git-branching-model/Vincent Driessen 2011
- 9. Lessons learned 1.Build quaility in 2.Automate everything 3.Keep everything in Version Control 4.Test on a production-like environment 5.Keep the delivery process simply boring
- 10. Do it more often if something is difficult or painful. Tests are important but they do not give you 100% confidence 6/7 frequency
- 11. Flicker case - throughput vs stability
- 12. Release Frequency vs. Risk
- 13. Plan, do, study, act all processes evolve. First release of an application is just first stage in its life 7/7 continuous improvement
- 14. Why should we care about Continuous Delivery? Reducing errors Lowering stress Getting feedback
- 15. Build the right thing 64% of functionality in software is rarely or never used. Chaos Report by Standish Group
- 18. Lean Startup
- 19. Test and Measure -> Be data-driven Christian Nilsson at the AWS Summit in Berlin on February 27, 2019
- 20. Books
- 21. CI/CD/CD BuildCode Integrate Release Deploy Continuous Integration Continuous Delivery Continuous Deployment STOP
Editor's Notes
- Nic nowego, wszystko o czym będę mowil widomo wielu lat. Deming, Toyota 1965 Agile manifesto 2001
- Każdy jest odpowiedzialny za jakość kodu Kolejnym anty pattern -> testujemy tylko zmiany w kod aplikacji. Powinnismy testować tak samo zmiany w konfiguracji, zmiany w zmiennych srodowiskowych Przekazywanie kodu pomiędzy silosami (kto pamięta co robil tydzień temu) Responsibility -> AdWeb 2016
- Build Testy Release Deployment Migracje baz danych Prowizjonowanie infrastruktury Nie da się zautomatyzować usability testow i testy eksploracyjne SSH – gitlab 2017
- Fail Fast, Minimalizacja czasu restorowania systemu
- 2011 IMVU Najdrozszym sposobem na sprawdzenie idei jest zbudowanie systemu informatycznego MVP Dostarczyc Zmierzyc Wyciagnac wnisoki