Merge hells!! Feature toggles to the rescue - DevOpsDays Madison
1 like480 views
This document discusses using feature toggles to help manage merge conflicts and allow for continuous delivery of code changes. It notes that building features nobody wants is a waste of resources. Feature toggles allow code to be deployed without being released, avoiding rollback issues. They also enable options like A/B testing and canary releasing. The document recommends managing feature toggles through configuration files and designing systems to be failure-tolerant using circuit breakers. It suggests architectures like branch by abstraction and strangler patterns to help manage feature toggles. Overall, it advocates taking a lean approach by working in small batches to integrate changes continuously.
1 of 40
Download to read offline
Recommended
Continuous delivery for Android
Continuous delivery for AndroidLeena N Continuous delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. The idea is to make your software releasable at any moment of time by integrating it continuously and releasing it frequently to get early and frequent feedback.
Because of the approval process that exists in the release process of Android apps, Continuous Delivery is not easy for Android apps as compared to web application deployments. And it's also assumed that not much tools are available to enable Continuous Delivery.
Yes, its still not instant update to the app, but still things are better than how it has been in the past. This talk gives an overview of tools and techniques that can help us to create a pipeline to get fast and frequent feedback through continuous delivery.
How open source is driving DevOps innovation: CloudOpen NA 2015
How open source is driving DevOps innovation: CloudOpen NA 2015Gordon Haff It’s no coincidence that all the interest around DevOps today comes at a time when open source technologies and processes are so dominant in cloud computing, data storage and analysis, and--increasingly--in networking. Innovations in Linux and other projects, including containers, configuration management, and continuous integration, are what make DevOps workflows and portable application deployments possible. But it’s also the result of open source culture, practices, and the tools supporting those practices that have made iterative development and collaboration such a powerful model for creating great software in communities. And now, they’re also providing a template for how to develop and operate applications internally within enterprises. In this session, we will discuss how open source tools and practices can be applied to create effective DevOps workflows and practices.
Introduction to continuous delivery
Introduction to continuous deliveryLeena N Continuous delivery is a software development practice where software can be released to production at any time by building software in a way that enables frequent, automated releases. It involves practices like continuous integration, where code is automatically merged and tested frequently, automated testing and deployment, and using deployment pipelines and tools to streamline the release process. Many large tech companies practice continuous delivery, with some deploying new code in minutes or every 11 seconds to get changes to users quickly.
Continuous delivery of embedded systems embedded meetup
Continuous delivery of embedded systems embedded meetupMike Long Continuous Delivery is all the rage, but many of the practices are not applied in the embedded world because the literature seems to focus on the web development community. That is a great shame, because there is a great deal we can apply on our embedded software development projects. This talk will show you how to apply some of the key techniques, such as embedded versioning and software traceability, embedded continuous delivery pipelines, acceptance testing with hardware, automatic deployment to hardware, continuous deployment. Beyond that, the talk will show some real-life examples of companies who are at the leading edge of this adoption.
Talk given at the Oslo Embedded Software meetup group.
Merge hells - Feature Toggles to the rescue
Merge hells - Feature Toggles to the rescueLeena N The document discusses how feature toggles can help address "merge hells" that can occur with continuous integration. Feature toggles allow incomplete features to be deployed without being released, avoiding the need to rollback deployments. They enable options like A/B testing, canary releasing, and managing experimental and operations toggles. To manage feature toggles, teams should follow mainline development practices, use feature toggle tools, set expiry dates for toggles, and consider toggles as a first step towards continuous delivery.
How to pass a coding interview as an automation developer talk - Oct 17 2016
How to pass a coding interview as an automation developer talk - Oct 17 2016Thomas F. "T.J." Maher Jr. How to pass a coding interview as an automation developer
Oct 17 2016
T.J. Maher has been a software tester for twenty years, but only recently became an automation developer. March 2015 he went from one job executing other people's automated testplans to writing his own.
When he found himself needing to start job searching over a year later due to a switch in management, he found major changes to the interview process. This presentation describes T.J. Maher's job hunt, those changes, and how he managed to find a new position ... Not just as an automation developer, but as a Software Engineer in Test.
Mobile Quality Night Vienna 2015 - Mobile UI Testautomation mit Specflow
Mobile Quality Night Vienna 2015 - Mobile UI Testautomation mit SpecflowRudolf Grötz SpecFlow is a behavior-driven development tool for .NET that uses the Gherkin syntax. It allows users to write automated tests for mobile applications in a natural language format. SpecFlow+ is the commercial test runner product from TechTalk that supports running SpecFlow tests across different target environments. The benefits of SpecFlow include formulating tests in a problem domain language for easier customer discussion, writing reusable steps, and writing platform-independent scenarios for multiple test feedback.
Cross platform or native: how to decide?
Cross platform or native: how to decide?Jad Salhani This document compares native mobile app development versus cross-platform development. Native apps are developed separately for each platform and offer the fastest performance but take longer to develop. Cross-platform apps are developed using a single codebase but may encounter issues with varying hardware. The document recommends evaluating your resources and requirements to determine whether a native or cross-platform approach is best for your project.
Closer To the Metal - Why and How We Use XCTest and Espresso by Mario Negro P...
Closer To the Metal - Why and How We Use XCTest and Espresso by Mario Negro P...Sauce Labs In this SauceCon 2019 presentation, Mario describes the practices that ABN AMRO adopted in mobile teams when it comes to testing native applications on real devices. Since using Espresso and XCUITest is still relatively uncommon for large apps and there are various unique challenges due to being in an EU-regulated industry with various security restrictions, Mario will share the ABN AMRO team’s experiences, including:
- A brief architectural overview of the Mobile Banking app: why it is all native (Objective-C/Swift and Java/Kotlin), how it communicates with other apps and websites
- Why ABN AMRO choose to adopt Espresso and XCUITest: the advantages and the limitations of this choice
- How ABN AMRO runs their test pipelines to spread them across time and devices and prevent teams from being blocked
Introduction To Continuous Integration
Introduction To Continuous IntegrationChristopher Read This document discusses continuous integration (CI), including why it is important, how it works through its core practices, and how CI evolves over time. CI is meant to catch bugs early, reduce merge conflicts, and make development teams more efficient by implementing automated builds, testing, and code integration. The core practices involve using a single source code repository, automating builds and testing, and publishing the latest version. CI is an evolving practice that changes as tools, languages, and development approaches change over time.
DevOps Unicorns
DevOps UnicornsMatt O'Keefe Matt O'Keefe discusses DevOps terminology and roles. While "DevOps" should not appear in team names, it may be appropriate in some job titles. Job descriptions should definitely mention DevOps. DevOps is difficult to precisely define, but you know it when you see it. Full stack developers are also discussed as they relate to DevOps and agile testing. O'Keefe welcomes any questions.
Manufacturing Plus Open Source Equals DevOps
Manufacturing Plus Open Source Equals DevOpsGordon Haff From DevOps Summit Silicon Valley, November 2015
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration.
Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling. In this session, Red Hat’s Gordon Haff will discuss the lessons and processes that DevOps can apply from manufacturing using:
- Container-based platforms designed for modern application development and deployment.
- The ability to design microservices-based applications using modular and reusable parts.
- Iterative development, testing, and deployment using Platform-as-a-Service and integrated continuous delivery systems.
Delivery Free of Charge
Delivery Free of ChargeAll Things Open The document discusses how people build software and modern development processes. It describes a traditional agile development process with sprints, planning, integration, reviews and retrospectives. It then summarizes a modern CI/CD DevOps workflow with continuous collaboration, integration, deployment to production and issue closing. It also discusses tooling, architecture principles, DevOps, templates, orchestration, inventory, machine templates and application templates.
Pivotal Tracker Overview
Pivotal Tracker OverviewDan Podsedly Pivotal Tracker is a shared, predictive, collaborative to-do list and project management tool used by thousands of teams for agile software development. It automates aspects of the agile process like prioritizing work, estimating story points, tracking velocity, and integrating with source control systems. Stories represent features or bugs, are broken into tasks, and flow through a workflow as they are developed, tested, and accepted. The tool provides visibility into progress and predicts future iterations based on historical performance.
Simple Continous Integration
Simple Continous IntegrationRicky Martaputra Continuous integration (CI) is a software development practice where developers regularly merge their code changes into a central repository after which automated builds and tests are run. Without CI, projects can experience insufficient testing, slow release processes, and harder to fix issues which can lead to project delays and inflexible code bases. CI introduces a smoother integration process with automated testing, regular working releases, and the ability to find and fix issues faster by delivering code continuously and having QA teams test frequently.
DevOps and Continuous Delivery Reference Architectures (including Nexus and o...
DevOps and Continuous Delivery Reference Architectures (including Nexus and o...Sonatype There are numerous examples of DevOps and Continuous Delivery reference architectures available, and each of them vary in levels of detail, tools highlighted, and processes followed. Yet, there is a constant theme among the tool sets: Jenkins, Maven, Sonatype Nexus, Subversion, Git, Docker, Puppet/Chef, Rundeck, ServiceNow, and Sonar seem to show up time and again.
Software Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringAndy Maleh Software craftsmanship and software engineering both aim to deliver high-quality, reliable software, but differ in their approaches. Software engineering focuses on macro goals and processes, while craftsmanship emphasizes mastering skills through experience. Both are used at Groupon, where engineering practices like architecture, testing and iteration are combined with craftsmanship techniques including apprenticeships and pair programming.
An almost complete continuous delivery pipeline including configuration manag...
An almost complete continuous delivery pipeline including configuration manag...ulfmansson How we have created a build pipeline for continous delivery at Recorded Future. This includes also test of Chef cookbooks and configuration.
Presentation at
Config Management Camp 2014
Tech Talk #5 : CI/CD FOR MOBILE DEVELOPMENT - Đinh Ngọc Kiên
Tech Talk #5 : CI/CD FOR MOBILE DEVELOPMENT - Đinh Ngọc KiênNexus FrontierTech This document discusses CI/CD for mobile development. It begins by explaining that CI favors testing and reporting changes as they happen. It then outlines the typical steps in a CI process for mobile: code is pushed to a repository and undergoes static analysis; pre-deployment testing includes unit tests; code is packaged and deployed to a test environment; and post-deployment testing includes functional and integration tests. The document also discusses how continuous delivery aims to allow reliable releases at any time, while continuous deployment focuses on automatically deploying changes that pass QA to production.
Back to basic: continuous integration (Madrid DevOps)
Back to basic: continuous integration (Madrid DevOps)Sergio Navarro Pino La integración continua es una práctica de ingeniería de software que consiste en hacer integraciones automáticas de un proyecto lo más a menudo posible, para así poder detectar fallos cuanto antes.
Podríamos pensar que en 2020 todos lo equipos integran continuamente, pero conversando con diferentes profesionales podemos ver que no siempre es así.
En esta sesión revisitaremos esta importante práctica, clave en DevOps, que por ser una de las más básicas, damos demasiadas veces por superada.
Continuous integration & deployment
Continuous integration & deploymentAlan Harper The document discusses options for setting up continuous integration for native iOS applications. It explores unit testing libraries like Sentest and gh-unit, functional testing options like UIAutomation, iCuke, and Frank, and static analysis tools like scan-build. While many existing tools were found lacking or difficult to use in a CI environment, Frank was identified as an actively maintained and easy to run functional testing option. The document also mentions concerns about testing push notifications and API interactions that may break with changes.
AgileDC15 I'm Using Chef So I'm DevOps Right?
AgileDC15 I'm Using Chef So I'm DevOps Right?Rob Brown This document provides an overview of DevOps principles and practices. It discusses the rise of DevOps as a movement to improve collaboration between development and operations teams. Common DevOps misconceptions are addressed. The CALMS framework of culture, automation, lean, measurement, and sharing is introduced as guiding principles. A roadmap for DevOps adoption is presented, along with take-home activities. The document aims to educate about DevOps in 3 sentences or less.
Advanced deployment scenarios (netcoreconf)
Advanced deployment scenarios (netcoreconf)Sergio Navarro Pino This document summarizes a presentation about advanced deployment strategies including canary releases, deployment rings, and dark launches. The presentation covers:
- How canary releases work by deploying a new version to a subset of infrastructure initially before gradually routing more users to it while monitoring for issues
- Key considerations for canary releases like ensuring a consistent user experience and having a rollback path
- How deployment rings limit impact on users by gradually deploying and validating changes in production rings
- Dark launches where new code is executed silently before a full launch to test infrastructure changes before high traffic
Advanced deployment scenarios
Advanced deployment scenariosSergio Navarro Pino The document discusses advanced deployment strategies including canary releases, deployment rings, and dark launching. It defines canary releases as deploying a new version to a subset of infrastructure initially without routing live traffic to it. Benefits include reducing risk and allowing capacity testing in production. The document reviews how to implement canary releases by routing a percentage of users to the new version while monitoring for issues before routing all users. It also discusses using deployment rings to gradually rollout changes and limit impact, as well as dark launching where new code is executed silently before a full launch.
Benefits of using Flutter
Benefits of using FlutterLucaSnchezLenAmado Flutter has changed the game 勞
We have worked with several technologies before we met Flutter, but it was love at first sight once we come across this revolutionary tech 朗 While there has been a lot of attempts to solve this multi-platform challenge for app development, Flutter is the first one that truly cracked it
Google’s SDK has firmly established its position in the market and continues to rise at high speed The Flutter community is continuously growing and it's being trusted by top companies such as Google Ads, The New York Times, eBay, Square, Alibaba Group, BMW, Toyota, and many more
Check out Flutter’s main benefits and why it’s our chosen technology for productive, high-quality, and modern software development with reduced costs 六
Dublin Unity User Group Meetup Sept 2015
Dublin Unity User Group Meetup Sept 2015Dominique Boutin This document provides tips for organizing code in new Unity projects. It recommends using a hub manager script to organize logic into groups and namespaces. Script execution order and custom app flows using coroutines and events are also discussed. Code should be organized pragmatically with self-speaking names and smart commenting rather than following dogmas. Behavior trees and reactive patterns can help structure application logic and data flow.
Overview the Challenges and Limitations of Android App Automation with Espres...
Overview the Challenges and Limitations of Android App Automation with Espres...Sauce Labs During this SauceCon 2019 presentation, Jagmit demonstrates how to set up Espresso, develop/execute tests and identify elements, and execute the Espresso tests in a Continuous Integration environment using Jenkins and Firebase.
Waste Driven Development - Agile Coaching Serbia Meetup
Waste Driven Development - Agile Coaching Serbia MeetupLemi Orhan Ergin This document discusses lean thinking and waste-driven development for software developers. It argues that traditional software development practices lead to a lot of waste, including defects, rework, slow development cycles, and lack of value delivery to customers. It promotes applying lean principles from manufacturing to software development, such as focusing on value delivery, eliminating waste, keeping codebases small and modular, automating everything, having high transparency, and challenging common paradigms. Documentation is identified as a particular type of waste.
Merge hells!! feature toggles to the rescue
Merge hells!! feature toggles to the rescueLeena N Introducing Continuous Delivery practices to a team in trouble can be daunting. Where do you start ? What do you do first ? Which battle do you pick first ?
I’ll share my experience of guiding a team to achieve a higher degree of delivery maturity. This is a journey from a troublesome, struggling start of chaotic manual deployments, merge hell, regular production roll backs and lost code, to deliver a single commit to trunk automatically and reliably, under an hour, many times a day.
Merge hells!! feature toggles to the rescue - Presented @ Agile Toronto
Merge hells!! feature toggles to the rescue - Presented @ Agile TorontoLeena N Have you ever wondered how Amazon does deployments in every 11 seconds? Have you ever wondered how frequently Google Chrome updates?
Compare that with an enterprise product you are using or the banking application that you use, it takes weeks or even months for an update. The assumption is that frequent releases are possible for Googles or Amazons or Unicorns. It is not for others.
This talk is about why that assumption is wrong. It can be done anywhere, with enough focus and investment for the Continuous Delivery pipeline to make sure that every commit is releasable or deployable.
And fundamental to Continuous Delivery is Continuous Integration. Continuous Integration guarantees every change committed to the repository is tested and reported about production readiness. And Feature Toggle is for turning features on/off depending upon certain conditions. This opens the opportunity to test certain features quickly with few users for experimentation and learning.
Feature branching has been popular for long, but everyone knows about the “code merge hell”, a common issue because of long-lived branches or infrequent integration. If the team is spending time in fixing the merge hells and checking what part of the code needs to be merged, then it is not the efficient use of human talent.
More Related Content
What's hot (20)
Closer To the Metal - Why and How We Use XCTest and Espresso by Mario Negro P...
Closer To the Metal - Why and How We Use XCTest and Espresso by Mario Negro P...Sauce Labs In this SauceCon 2019 presentation, Mario describes the practices that ABN AMRO adopted in mobile teams when it comes to testing native applications on real devices. Since using Espresso and XCUITest is still relatively uncommon for large apps and there are various unique challenges due to being in an EU-regulated industry with various security restrictions, Mario will share the ABN AMRO team’s experiences, including:
- A brief architectural overview of the Mobile Banking app: why it is all native (Objective-C/Swift and Java/Kotlin), how it communicates with other apps and websites
- Why ABN AMRO choose to adopt Espresso and XCUITest: the advantages and the limitations of this choice
- How ABN AMRO runs their test pipelines to spread them across time and devices and prevent teams from being blocked
Introduction To Continuous Integration
Introduction To Continuous IntegrationChristopher Read This document discusses continuous integration (CI), including why it is important, how it works through its core practices, and how CI evolves over time. CI is meant to catch bugs early, reduce merge conflicts, and make development teams more efficient by implementing automated builds, testing, and code integration. The core practices involve using a single source code repository, automating builds and testing, and publishing the latest version. CI is an evolving practice that changes as tools, languages, and development approaches change over time.
DevOps Unicorns
DevOps UnicornsMatt O'Keefe Matt O'Keefe discusses DevOps terminology and roles. While "DevOps" should not appear in team names, it may be appropriate in some job titles. Job descriptions should definitely mention DevOps. DevOps is difficult to precisely define, but you know it when you see it. Full stack developers are also discussed as they relate to DevOps and agile testing. O'Keefe welcomes any questions.
Manufacturing Plus Open Source Equals DevOps
Manufacturing Plus Open Source Equals DevOpsGordon Haff From DevOps Summit Silicon Valley, November 2015
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration.
Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling. In this session, Red Hat’s Gordon Haff will discuss the lessons and processes that DevOps can apply from manufacturing using:
- Container-based platforms designed for modern application development and deployment.
- The ability to design microservices-based applications using modular and reusable parts.
- Iterative development, testing, and deployment using Platform-as-a-Service and integrated continuous delivery systems.
Delivery Free of Charge
Delivery Free of ChargeAll Things Open The document discusses how people build software and modern development processes. It describes a traditional agile development process with sprints, planning, integration, reviews and retrospectives. It then summarizes a modern CI/CD DevOps workflow with continuous collaboration, integration, deployment to production and issue closing. It also discusses tooling, architecture principles, DevOps, templates, orchestration, inventory, machine templates and application templates.
Pivotal Tracker Overview
Pivotal Tracker OverviewDan Podsedly Pivotal Tracker is a shared, predictive, collaborative to-do list and project management tool used by thousands of teams for agile software development. It automates aspects of the agile process like prioritizing work, estimating story points, tracking velocity, and integrating with source control systems. Stories represent features or bugs, are broken into tasks, and flow through a workflow as they are developed, tested, and accepted. The tool provides visibility into progress and predicts future iterations based on historical performance.
Simple Continous Integration
Simple Continous IntegrationRicky Martaputra Continuous integration (CI) is a software development practice where developers regularly merge their code changes into a central repository after which automated builds and tests are run. Without CI, projects can experience insufficient testing, slow release processes, and harder to fix issues which can lead to project delays and inflexible code bases. CI introduces a smoother integration process with automated testing, regular working releases, and the ability to find and fix issues faster by delivering code continuously and having QA teams test frequently.
DevOps and Continuous Delivery Reference Architectures (including Nexus and o...
DevOps and Continuous Delivery Reference Architectures (including Nexus and o...Sonatype There are numerous examples of DevOps and Continuous Delivery reference architectures available, and each of them vary in levels of detail, tools highlighted, and processes followed. Yet, there is a constant theme among the tool sets: Jenkins, Maven, Sonatype Nexus, Subversion, Git, Docker, Puppet/Chef, Rundeck, ServiceNow, and Sonar seem to show up time and again.
Software Craftsmanship VS Software Engineering
Software Craftsmanship VS Software EngineeringAndy Maleh Software craftsmanship and software engineering both aim to deliver high-quality, reliable software, but differ in their approaches. Software engineering focuses on macro goals and processes, while craftsmanship emphasizes mastering skills through experience. Both are used at Groupon, where engineering practices like architecture, testing and iteration are combined with craftsmanship techniques including apprenticeships and pair programming.
An almost complete continuous delivery pipeline including configuration manag...
An almost complete continuous delivery pipeline including configuration manag...ulfmansson How we have created a build pipeline for continous delivery at Recorded Future. This includes also test of Chef cookbooks and configuration.
Presentation at
Config Management Camp 2014
Tech Talk #5 : CI/CD FOR MOBILE DEVELOPMENT - Đinh Ngọc Kiên
Tech Talk #5 : CI/CD FOR MOBILE DEVELOPMENT - Đinh Ngọc KiênNexus FrontierTech This document discusses CI/CD for mobile development. It begins by explaining that CI favors testing and reporting changes as they happen. It then outlines the typical steps in a CI process for mobile: code is pushed to a repository and undergoes static analysis; pre-deployment testing includes unit tests; code is packaged and deployed to a test environment; and post-deployment testing includes functional and integration tests. The document also discusses how continuous delivery aims to allow reliable releases at any time, while continuous deployment focuses on automatically deploying changes that pass QA to production.
Back to basic: continuous integration (Madrid DevOps)
Back to basic: continuous integration (Madrid DevOps)Sergio Navarro Pino La integración continua es una práctica de ingeniería de software que consiste en hacer integraciones automáticas de un proyecto lo más a menudo posible, para así poder detectar fallos cuanto antes.
Podríamos pensar que en 2020 todos lo equipos integran continuamente, pero conversando con diferentes profesionales podemos ver que no siempre es así.
En esta sesión revisitaremos esta importante práctica, clave en DevOps, que por ser una de las más básicas, damos demasiadas veces por superada.
Continuous integration & deployment
Continuous integration & deploymentAlan Harper The document discusses options for setting up continuous integration for native iOS applications. It explores unit testing libraries like Sentest and gh-unit, functional testing options like UIAutomation, iCuke, and Frank, and static analysis tools like scan-build. While many existing tools were found lacking or difficult to use in a CI environment, Frank was identified as an actively maintained and easy to run functional testing option. The document also mentions concerns about testing push notifications and API interactions that may break with changes.
AgileDC15 I'm Using Chef So I'm DevOps Right?
AgileDC15 I'm Using Chef So I'm DevOps Right?Rob Brown This document provides an overview of DevOps principles and practices. It discusses the rise of DevOps as a movement to improve collaboration between development and operations teams. Common DevOps misconceptions are addressed. The CALMS framework of culture, automation, lean, measurement, and sharing is introduced as guiding principles. A roadmap for DevOps adoption is presented, along with take-home activities. The document aims to educate about DevOps in 3 sentences or less.
Advanced deployment scenarios (netcoreconf)
Advanced deployment scenarios (netcoreconf)Sergio Navarro Pino This document summarizes a presentation about advanced deployment strategies including canary releases, deployment rings, and dark launches. The presentation covers:
- How canary releases work by deploying a new version to a subset of infrastructure initially before gradually routing more users to it while monitoring for issues
- Key considerations for canary releases like ensuring a consistent user experience and having a rollback path
- How deployment rings limit impact on users by gradually deploying and validating changes in production rings
- Dark launches where new code is executed silently before a full launch to test infrastructure changes before high traffic
Advanced deployment scenarios
Advanced deployment scenariosSergio Navarro Pino The document discusses advanced deployment strategies including canary releases, deployment rings, and dark launching. It defines canary releases as deploying a new version to a subset of infrastructure initially without routing live traffic to it. Benefits include reducing risk and allowing capacity testing in production. The document reviews how to implement canary releases by routing a percentage of users to the new version while monitoring for issues before routing all users. It also discusses using deployment rings to gradually rollout changes and limit impact, as well as dark launching where new code is executed silently before a full launch.
Benefits of using Flutter
Benefits of using FlutterLucaSnchezLenAmado Flutter has changed the game 勞
We have worked with several technologies before we met Flutter, but it was love at first sight once we come across this revolutionary tech 朗 While there has been a lot of attempts to solve this multi-platform challenge for app development, Flutter is the first one that truly cracked it
Google’s SDK has firmly established its position in the market and continues to rise at high speed The Flutter community is continuously growing and it's being trusted by top companies such as Google Ads, The New York Times, eBay, Square, Alibaba Group, BMW, Toyota, and many more
Check out Flutter’s main benefits and why it’s our chosen technology for productive, high-quality, and modern software development with reduced costs 六
Dublin Unity User Group Meetup Sept 2015
Dublin Unity User Group Meetup Sept 2015Dominique Boutin This document provides tips for organizing code in new Unity projects. It recommends using a hub manager script to organize logic into groups and namespaces. Script execution order and custom app flows using coroutines and events are also discussed. Code should be organized pragmatically with self-speaking names and smart commenting rather than following dogmas. Behavior trees and reactive patterns can help structure application logic and data flow.
Overview the Challenges and Limitations of Android App Automation with Espres...
Overview the Challenges and Limitations of Android App Automation with Espres...Sauce Labs During this SauceCon 2019 presentation, Jagmit demonstrates how to set up Espresso, develop/execute tests and identify elements, and execute the Espresso tests in a Continuous Integration environment using Jenkins and Firebase.
Waste Driven Development - Agile Coaching Serbia Meetup
Waste Driven Development - Agile Coaching Serbia MeetupLemi Orhan Ergin This document discusses lean thinking and waste-driven development for software developers. It argues that traditional software development practices lead to a lot of waste, including defects, rework, slow development cycles, and lack of value delivery to customers. It promotes applying lean principles from manufacturing to software development, such as focusing on value delivery, eliminating waste, keeping codebases small and modular, automating everything, having high transparency, and challenging common paradigms. Documentation is identified as a particular type of waste.
Similar to Merge hells!! Feature toggles to the rescue - DevOpsDays Madison (20)
Merge hells!! feature toggles to the rescue
Merge hells!! feature toggles to the rescueLeena N Introducing Continuous Delivery practices to a team in trouble can be daunting. Where do you start ? What do you do first ? Which battle do you pick first ?
I’ll share my experience of guiding a team to achieve a higher degree of delivery maturity. This is a journey from a troublesome, struggling start of chaotic manual deployments, merge hell, regular production roll backs and lost code, to deliver a single commit to trunk automatically and reliably, under an hour, many times a day.
Merge hells!! feature toggles to the rescue - Presented @ Agile Toronto
Merge hells!! feature toggles to the rescue - Presented @ Agile TorontoLeena N Have you ever wondered how Amazon does deployments in every 11 seconds? Have you ever wondered how frequently Google Chrome updates?
Compare that with an enterprise product you are using or the banking application that you use, it takes weeks or even months for an update. The assumption is that frequent releases are possible for Googles or Amazons or Unicorns. It is not for others.
This talk is about why that assumption is wrong. It can be done anywhere, with enough focus and investment for the Continuous Delivery pipeline to make sure that every commit is releasable or deployable.
And fundamental to Continuous Delivery is Continuous Integration. Continuous Integration guarantees every change committed to the repository is tested and reported about production readiness. And Feature Toggle is for turning features on/off depending upon certain conditions. This opens the opportunity to test certain features quickly with few users for experimentation and learning.
Feature branching has been popular for long, but everyone knows about the “code merge hell”, a common issue because of long-lived branches or infrequent integration. If the team is spending time in fixing the merge hells and checking what part of the code needs to be merged, then it is not the efficient use of human talent.
AgileLINC Continous Slides by Daniel Harp
AgileLINC Continous Slides by Daniel HarpBarry Gavril This document discusses continuous integration practices. It defines continuous integration as an attitude rather than a tool. Key practices of continuous integration include: maintaining a single source repository, automating builds, keeping builds fast, making builds self-testing through automated tests, committing to the mainline daily to avoid branches, triggering a build on every commit through a build server, making every commit potentially shippable, ensuring binary integrity, testing in a clone of production, making the latest executable easily available, and enabling everyone to see what's happening. The document emphasizes focusing on organizational, architectural and process changes over tools when adopting continuous integration.
Scrum is not enough - being a successful agile engineer
Scrum is not enough - being a successful agile engineerAnton Keks The recipe for developers to perform in agile software development environment is to use technical practices, many of which are coming from XP.
Cloud-Native Fundamentals: Accelerating Development with Continuous Integration
Cloud-Native Fundamentals: Accelerating Development with Continuous IntegrationVMware Tanzu DevOps. Microservices. Containers. These terms have a lot of buzz for their role in cloud-native application development and operations. But, if you haven't automated your tests and builds with continuous integration (CI), none of them matter.
Continuous integration is the automation of building and testing new code. Development teams that use CI can catch bugs early and often; resulting in code that is always production ready. Compared to manual testing, CI eliminates a lot of toil and improves code quality. At the end of the day, it's those code defects that slip into production that slow down teams and cause apps to fall over.
The journey to continuous integration maturity has some requirements. Join Pivotal's James Ma, product manager for Concourse, and Dormain Drewitz, product marketing to learn about:
- How Test-Driven Development feeds the CI process
- What is different about CI in a cloud-native context
- How to measure progress and success in adopting CI
Dormain is a Senior Director of Product and Customer Marketing with Pivotal. She has published extensively on cloud computing topics for ten years, demystifying the changing requirements of the infrastructure software stack. She’s presented at the Gartner Application Architecture, Development, and Integration Summit; Open Source Summit; Cloud Foundry Summit, and numerous software user events.
James Ma is a product manager at Pivotal and is based out of their office in Toronto, Canada. As a consultant for the Pivotal Labs team, James worked with Fortune 500 companies to hone their agile software development practices and adopt a user-centered approach to product development. He has worked with companies across multiple industries including: mobile e-commerce, finance, heath and hospitality. James is currently a part of the Pivotal Cloud Foundry R&D group and is the product manager for Concourse CI, the continuous "thing do-er".
Presenters : Dormain Drewitz & James Ma, Pivotal
Containers: DevOp Enablers of Technical Solutions
Containers: DevOp Enablers of Technical SolutionsJules Pierre-Louis Containers, the next wave of virtualization, are changing everything! As companies learn about the value of DevOps practices and containerization they are flocking to containers. Now with Docker running on Windows and Docker Containers built into both Azure and Windows Server, containers are poised to take over the virtualization landscape. Come to the session to learn all about containers and how you can put these technologies to use in your organization. You will learn about DevOps, Docker Containers, Running Containers on Windows 10, Windows Server 2016 and Linux on-premises or in the Azure cloud. You will learn about the tools and practices for leveraging containers, deploying containers as well as how you can continue on your journey to becoming a container expert as you grow your technical career.
Do's and don'ts for continuous delivery
Do's and don'ts for continuous deliveryMichael Athiwat Wongwaisayawan This document discusses dos and don'ts for continuous delivery. It recommends automating deployment and provisioning processes, using the same mechanisms for all environments, checking all code into version control, and incrementally implementing continuous delivery practices. It also advises understanding why changes are needed, using short-lived branches, and understanding one's team capabilities.
Build software like a bag of marbles, not a castle of LEGO®
Build software like a bag of marbles, not a castle of LEGO®Hannes Lowette If you have ever played with LEGO®, you will know that adding, removing or changing features of a completed castle isn’t as easy as it seems. You will have to deconstruct large parts to get to where you want to be, to build it all up again afterwards. Unfortunately, our software is often built the same way. Wouldn’t it be better if our software behaved like a bag of marbles? So you can just add, remove or replace them at will?
Most of us have taken different approaches to building software: a big monolith, a collection of services, a bus architecture, etc. But whatever your large scale architecture is, at the granular level (a single service or host), you will probably still end up with tightly couple code. Adding functionality means making changes to every layer, service or component involved. It gets even harder if you want to enable or disable features for certain deployments: you’ll need to wrap code in feature flags, write custom DB migration scripts, etc. There has to be a better way!
So what if you think of functionality as loose feature assemblies? We can construct our code in such a way that adding a feature is as simple as adding the assembly to your deployment, and removing it is done by just deleting the file. We would open the door for so many scenarios!
In this talk, I will explain how to tackle the following parts of your application to achieve this goal: WebAPI, Entity Framework, Onion Architecture, IoC and database migrations. And most of all, when you would want to do this. Because… ‘it depends’.
Continuous Integration - What even is it?
Continuous Integration - What even is it?Rob Jacoby The document discusses continuous integration and continuous delivery. Continuous integration involves regularly merging code into a main branch and running automated tests after every commit. This prevents large, complex branches from developing. Continuous delivery aims to ensure code can be reliably released at any time by deploying code as soon as it is merged into the main branch. Best practices for continuous integration include maintaining a code repository, automating builds and tests, committing to the main branch daily, and making the build process fast. Continuous delivery best practices include automating all build, test and deployment scripts, and separating scripts for dependencies, testing, and deploying.
Continuous integration at CartoDB
Continuous integration at CartoDBJuan Ignacio Sánchez Lara This document discusses CartoDB's use of continuous integration and deployment practices. It defines continuous integration, delivery, and deployment. CartoDB breaks its codebase into components and products. It aims to reduce risk through practices like feature flags, canary releases, quick rollbacks, post-mortems, and smoke tests. Continuous deployment provides benefits like early issue detection but requires plans for risks like database locks and integration issues. It is not suitable for all organizations.
Continuous delivery applied (RJUG)
Continuous delivery applied (RJUG)Mike McGarr This document provides an overview of continuous delivery and deployment practices. It discusses concepts like continuous integration, deployment pipelines, automated testing, configuration management, and deploying software frequently and reliably to production. The presentation emphasizes automating processes, deploying software in small batches, keeping everything version controlled, and establishing a culture of continuous improvement.
DevOps - Introduction to data science
DevOps - Introduction to data scienceFrank Kienle Lecture: Introduction to Data Science
given 2017 at Technical University of Kaiserslautern, Germany
topic: DevOps and professional development
Evolving Services Into A Cloud Native World
Evolving Services Into A Cloud Native WorldIain Hull How Workday manage stateful services with a custom controller on Kubernetes?
Conference talk for CloudNative London 2018
https://skillsmatter.com/skillscasts/12106-evolving-services-into-the-cloud-native-world-how-workday-manage-stateful-services-with-a-custom-controller-on-kubernetes
Kubernetes and declarative infrastructure greatly simplify the way we deploy and manage software. Most services can be orchestrated with the control loops supplied by Kubernetes (deployments, stateful sets or jobs). Some stateful services in Workday require more advanced orchestration, and re-architecting them is not an easy option.
In this talk you will discover why some of our services require extra orchestration, and how we evolved an existing service into a control loop on top of Kubernetes. The control loop organises multiple services into groups these are dynamically created, deleted and scaled. It also orchestrates blue/green deployments of each group. Now we can adopt more kubernetes features and retire some of our old scheduling code. Finally you will learn the process we follow to evaluate and design our own control loops and when you might find them useful.
Bio
Iain is a principal software engineer at Workday using Kubernetes and Scala to deliver their next generation elastic grid. His twin passions are large scale distributed computing and applying clean code to complex problems. He is interested in good design and how this can improve system reliability and reduce friction during development.
He loves sharing his experiences as he learns and builds new systems. He regularly speaks at local meetups in Dublin and has presented at conferences including GotoConf, Scala Days, Functional Kats and Lambda World.
Docker adventures in Continuous Delivery - Alex Vranceanu
Docker adventures in Continuous Delivery - Alex VranceanuITCamp Implementing CI with Docker are the baby steps. The tricky one is CD through several environments. Architecture, demo and lessons learned. Target audience: 80% technical, 20% PM/architects/leaders
Build Time Hacking
Build Time HackingMohammed Tanveer Imagine we had the power to understand the code before its complied or embedding a backdoor or even stealing legitimate certificates of a well known vendor and using them to sign malware?
Join me in the journey of exploring security issues that tend to happen during Build Time in typical enterprise environments.
PittsburgJUG_Cloud-Native Dev Tools: Bringing the cloud back to earth
PittsburgJUG_Cloud-Native Dev Tools: Bringing the cloud back to earthGrace Jansen How can we effectively develop for the cloud, when we as developers are coding back down on earth? This is where effective cloud-native developer tools can enable us to either be transported into the cloud or alternatively, to bring the cloud back down to earth. But what tools should we be using for this? In this session, we’ll explore some of the useful OSS tools and technologies that can used by developers to effectively develop, design and test cloud-native Java applications.
Docker Meetup at Docker HQ: Docker Cloud
Docker Meetup at Docker HQ: Docker CloudDocker, Inc. Talk #1: Ryan Kennedy, CI: Build and Test in Docker Cloud
In this talk, Ryan Kennedy will present an overview of Docker Cloud and demonstrate how to configure a CI pipeline using the automated build and test capabilities. We will dive into the latest features available in Docker Cloud, including sharing repositories with teams and securing your application pipeline.
*
Talk #2: Bryan Lee and Alberto Megia, Deploying and Managing Applications in Docker Cloud
In this talk, Bryan Lee and Alberto Megia will demonstrate auto-deployment capabilities in Docker Cloud as well as how to deploy, manage, and scale container-based applications directly within the tool.
Xcode eXtreme Programming - #pragmamark 2014, Milan
Xcode eXtreme Programming - #pragmamark 2014, MilanGiulio Roggero Speed up the development and increase the app quality are the keywords for success. Good points, not so simple to achieve….
eXtreme Programming (XP) is an agile discipline of software development based on values of simplicity, communication, feedback, courage, and respect. The software is built around the needs of the customer through a continuous release of working software and creating a learning loop that dramatically improves the quality of the final product.
Some XP practices, like TDD and Continuous Integration, can benefit of the support of software tools and frameworks. In this session we will see how XCTest and Xcode Continuous Integration can streamline the process of the iOS XP team.
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as Code
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as CodeSteve Mercier Slides from my talk at ConFoo Montreal, February 2016. A presentation on how to apply configuration management (CM) principles for your various environments, to control changes made to them. You apply CM on your code, why not on your environments content? This presentation will present the infrastructure as code principles using Chef and/or Ansible. Topics discussed include Continuous Integration, Continuous Delivery/Deployment principles, Infrastructure As Code and DevOps.
Continuous integration (eng)
Continuous integration (eng)Anatoliy Okhotnikov What is continuous integration?
Building a feature with continuous integration
Practices of continuous integration
Benefits of continuous integration
Introducing continuous integration
Final thoughts
Continuous integration tools
More from Leena N (20)
The last mile problem
The last mile problemLeena N Have you ever asked a programmer how much longer “this” is going to take? Here goes another typical answer. I am done with most of the tasks, need extra time to finish the last few ones. And the “last few tasks” never ends or takes enormous amounts of time.
On the one hand, we all know that estimates always go wrong. But there is another aspect to this too, i.e. the last mile problem. It can be because of the “fear or shipping” or not applying the guideline “done is better than perfect”.
This talk is about a few tricks I tried not to get into the “perfection” mode; instead, get into the habit of “shipping”. Surprisingly, that helped me to avoid providing estimates :)
Expand Contract Pattern for Continuous Delivery of Databases
Expand Contract Pattern for Continuous Delivery of DatabasesLeena N This document discusses techniques for continuously delivering database changes, including database refactoring. It describes strategies like splitting tables and columns, adding transition periods, using versioning, automation with testing, and making changes incrementally and reversibly. Database refactoring includes structural, data quality, referential integrity, and transformation changes. Tools, strategies for low risk releases, and patterns like branch by abstraction and strangler are recommended to support evolutionary development and continuous delivery of database changes.
Sprinkle javascript using stimulus js
Sprinkle javascript using stimulus jsLeena N n this world of Microservices, I am building a Monolith app. In this world of React and Vue, am building a server-side rendered app.
However, I need Javascript. I can’t avoid that. I need some parts of the page updated dynamically. I need to show/hide certain parts of the page depending upon user actions.
I don’t want JQuery for the obvious reasons. Slow.., Heavy and then, of course, it can easily create spaghetti code.
That is when I came across Stimulus JS - a modest Javascript framework. It sprinkles Javascript to add behaviour to your HTML.
It has a controller, action and targets (i.e. the HTML elements). Moreover, it pairs well with Turbolinks. So I don’t need to do the circus of converting JSON to DOM.
I’ve been using Stimulus for over a year and its been quite good. This talk is about my experiences with Stimulus with a few examples. I will share recommendations on where it might be useful and where it is not.
Patterns and practices for evolvability - the key for technical agility
Patterns and practices for evolvability - the key for technical agilityLeena N Evolvability refers to the ability to adapt to market needs and the changing environment. Mainly two kinds of evolvability are needed: Product evolving as per the market needs to avoid Building something that nobody wants The architecture and the design of the software evolving to allow the team to make faster changes to the product without breaking things That is why it is crucial to build the right product and build it in the right way.
Expand contract pattern - Continuous Delivery for Databases - DevOpsDays Seattle
Expand contract pattern - Continuous Delivery for Databases - DevOpsDays SeattleLeena N Modifying the schema of a production database is *hard*. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Contract pattern is a blueprint for making the database migration. It makes the remodelling both reversible and safe. By *expanding* the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema
- Gain confidence that the migration is safe
We *contract* the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a **continuous delivery way**. Most importantly, without threatening the robustness of your production applications.
Expand contract pattern continuous delivery and databases
Expand contract pattern continuous delivery and databasesLeena N Modifying the schema of a production database is hard. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Collapse pattern is a blueprint for making the database migration and makes the remodelling both reversible and safe. By expanding the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema;
- Gain confidence that the migration is safe.
We contract the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a continuous delivery way. Most importantly, without threatening the robustness of your production applications.
Expand contract pattern - Continuous Delivery and Databases
Expand contract pattern - Continuous Delivery and DatabasesLeena N Modifying the schema of a production database is *hard*. If something goes wrong, the impact on both customers and the team can be enormous. And it can be hard or even impossible to rollback a database schema change if things go wrong. And the same is true for any architectural change for a production application.
The Branch by Abstraction and Strangler Pattern makes significant application changes easier. Are there any similar patterns we can use to make production database changes less risky?
Indeed, there are. The Expand/Contract pattern is a blueprint for making the database migration. It makes the remodelling both reversible and safe. By *expanding* the application to accommodate both the old and the new schemas in parallel, we can give ourselves time to:
- Migrate any downstream dependencies on the old database schema
- Gain confidence that the migration is safe
We *contract* the application to the new version, once we’ve satisfied that the old schema is no longer needed.
The pattern helps to make significant, but necessary refactorings to your data model in a **continuous delivery way**. Most importantly, without threatening the robustness of your production applications.
Importance of Showing Up
Importance of Showing UpLeena N The talk I gave @ Diversity Meetup [conducted by HasGeek on 7th April, 2018] @ Walmarl Labs.
https://rootconf.in/2018-diversity-meetup-walmart/
Growth
GrowthLeena N What does career growth mean? How does one grow in their career? How do you choose an organisation which allows one to grow?
One grows when the environment allows growing. I am not talking about the std. the corporate ladder. One can climb those automatically as the time passes. But all of us agree that it doesn't mean "growth".
The key ingredients for the actual growth is the following:
* Purpose - the intention to contribute to the well-being of others
* Practice - Consistent and deliberate practice
* Perseverance - Persistence to try out hard things
The talk is about examples and stories about these ingredients and what makes those who have these ingredients and those who don't.
TDD, Refactoring - Workshop
TDD, Refactoring - WorkshopLeena N This document discusses test-driven development (TDD) and refactoring using the Gilded Rose kata exercise. It provides rules for TDD, such as only writing production code with a failing test and refactoring code after each test. Simple design principles are outlined, like revealing intention and avoiding duplication. Extreme object-oriented programming rules are also listed, like limiting indentation and properties. The goal is to practice TDD and refactoring skills through the Gilded Rose kata.
Technical debt a catch all phrase--
Technical debt a catch all phrase--Leena N This talk is about bringing in the segregation to identify the debt and the tactics of paying off technical debt in a matured, sustainable manner. Yes, it can be paid off provided enough focus is given to it.
Developing, building, testing and deploying react native apps
Developing, building, testing and deploying react native appsLeena N React Native is gaining maturity as a cross-platform mobile app development solution. With a strong community around the ecosystem, mobile app development is all set to become simpler and enjoyable.
This talk is about various techniques and tools that are available for building, testing and deploying React Native apps for Android and iOS platforms.
Continuous delivery from the trenches
Continuous delivery from the trenchesLeena N This document discusses two companies' journeys to continuous delivery of software. The first story describes automating a loan processing platform that now processes close to $4 million in loans with a small team. The second story automated a mobile device management solution for healthcare. The document then outlines the continuous delivery process used, including practices like continuous integration, deployment pipelines and emphasizing delivering business value. Challenges discussed include balancing speed and quality while improving processes through retrospectives.
Deliver with impact
Deliver with impactLeena N This document discusses impact mapping as a technique for delivering projects with impact. It provides an example of impact mapping for an MDM (mobile device management) product. The key steps of impact mapping include: defining goals and who they impact; identifying desired behaviors and how to enable them; establishing metrics to measure impact; and planning milestones to test assumptions. Impact mapping focuses on creating actual behavioral change rather than just shipping software.
Learnings while building Mobile Device Management [MDM] ![Learnings while building Mobile Device Management [MDM]](https://cdn.slidesharecdn.com/ss_thumbnails/mobiledevicemanagementdroidconin2015v2-151218164812-thumbnail.jpg?width=560&fit=bounds)
Learnings while building Mobile Device Management [MDM] Leena N The presentation I gave DroidCon India '15 about building device management and our experiences/learnings with the same.
Javascript Testing Tools - Overview
Javascript Testing Tools - OverviewLeena N This document discusses different types of testing tools, including unit testing tools like Jasmine and Mocha that allow for quick feedback during test-driven development, end-to-end testing tools like Selenium and Protractor that simulate user interactions, contract testing tools like Pact that test design contracts, and screenshot comparison tools like Wraith and Resemble.js for visual regression testing. It also mentions that unit tests should have high value but low maintenance, end-to-end tests have high effort for maintenance, and that testing strategies should follow the testing pyramid with more unit and integration tests than end-to-end tests.
Continuous delivery using jenkins
Continuous delivery using jenkinsLeena N This document discusses the importance of continuous delivery using Jenkins. It introduces continuous integration and continuous delivery, explaining that continuous integration provides fast feedback on code changes while continuous delivery provides feedback on production readiness. It outlines how to set up a build pipeline in Jenkins to guarantee production readiness and make releases risk-free and automated. The document emphasizes that continuous delivery satisfies customers through early and frequent delivery of software and encourages teams to take responsibility for releases through continuous improvement.
Culture of Continuous Delivery
Culture of Continuous DeliveryLeena N This document discusses the culture of continuous delivery. It promotes building quality in from the start, keeping the build always deployable, and continuous improvement. Continuous delivery aspects include automating the build, having a deployable build, continuous integration, build pipelines, configuration management, release management, and using Kanban and feature toggles. Practicing continuous delivery leads to a great culture with values like delighted customers and software craftsmanship. It also discusses concepts from neuroscience like how the brain reacts to stress and rewards that relate to continuous delivery practices.
TDD with AngularJS
TDD with AngularJSLeena N This is the slides we used for AngularJS Workshop we did as part of AngularJS Miniconf 2014. https://metarefresh.in/2014/angularjs-miniconf
Droid con 2013 workshop unit testing in android [robolectirc]![Droid con 2013 workshop unit testing in android [robolectirc]](https://cdn.slidesharecdn.com/ss_thumbnails/droidcon2013workshop-unittestinginandroidrobolectirc-131127032715-phpapp02-thumbnail.jpg?width=560&fit=bounds)
Droid con 2013 workshop unit testing in android [robolectirc]Leena N This document discusses unit testing Android applications. It introduces Robolectric, an emulation framework that runs unit tests for Android apps on a Java Virtual Machine instead of an emulator or device. This allows tests to run much faster. Robolectric emulates the Android SDK and resources using shadow objects and view/resource loading. It is easy to extend and has good community support. While useful for unit testing, it cannot replace integrated tests that run on actual devices.
Recently uploaded (20)
Who Watches the Watchmen (SciFiDevCon 2025)
Who Watches the Watchmen (SciFiDevCon 2025)Allon Mureinik Tests, especially unit tests, are the developers’ superheroes. They allow us to mess around with our code and keep us safe.
We often trust them with the safety of our codebase, but how do we know that we should? How do we know that this trust is well-deserved?
Enter mutation testing – by intentionally injecting harmful mutations into our code and seeing if they are caught by the tests, we can evaluate the quality of the safety net they provide. By watching the watchmen, we can make sure our tests really protect us, and we aren’t just green-washing our IDEs to a false sense of security.
Talk from SciFiDevCon 2025
https://www.scifidevcon.com/courses/2025-scifidevcon/contents/680efa43ae4f5
Adobe Master Collection CC Crack Advance Version 2025
Adobe Master Collection CC Crack Advance Version 2025kashifyounis067 🌍📱👉COPY LINK & PASTE ON GOOGLE http://drfiles.net/ 👈🌍
Adobe Master Collection CC (Creative Cloud) is a comprehensive subscription-based package that bundles virtually all of Adobe's creative software applications. It provides access to a wide range of tools for graphic design, video editing, web development, photography, and more. Essentially, it's a one-stop-shop for creatives needing a broad set of professional tools.
Key Features and Benefits:
All-in-one access:
The Master Collection includes apps like Photoshop, Illustrator, InDesign, Premiere Pro, After Effects, Audition, and many others.
Subscription-based:
You pay a recurring fee for access to the latest versions of all the software, including new features and updates.
Comprehensive suite:
It offers tools for a wide variety of creative tasks, from photo editing and illustration to video editing and web development.
Cloud integration:
Creative Cloud provides cloud storage, asset sharing, and collaboration features.
Comparison to CS6:
While Adobe Creative Suite 6 (CS6) was a one-time purchase version of the software, Adobe Creative Cloud (CC) is a subscription service. CC offers access to the latest versions, regular updates, and cloud integration, while CS6 is no longer updated.
Examples of included software:
Adobe Photoshop: For image editing and manipulation.
Adobe Illustrator: For vector graphics and illustration.
Adobe InDesign: For page layout and desktop publishing.
Adobe Premiere Pro: For video editing and post-production.
Adobe After Effects: For visual effects and motion graphics.
Adobe Audition: For audio editing and mixing.
What Do Contribution Guidelines Say About Software Testing? (MSR 2025)
What Do Contribution Guidelines Say About Software Testing? (MSR 2025)Andre Hora Software testing plays a crucial role in the contribution process of open-source projects. For example, contributions introducing new features are expected to include tests, and contributions with tests are more likely to be accepted. Although most real-world projects require contributors to write tests, the specific testing practices communicated to contributors remain unclear. In this paper, we present an empirical study to understand better how software testing is approached in contribution guidelines. We analyze the guidelines of 200 Python and JavaScript open-source software projects. We find that 78% of the projects include some form of test documentation for contributors. Test documentation is located in multiple sources, including CONTRIBUTING files (58%), external documentation (24%), and README files (8%). Furthermore, test documentation commonly explains how to run tests (83.5%), but less often provides guidance on how to write tests (37%). It frequently covers unit tests (71%), but rarely addresses integration (20.5%) and end-to-end tests (15.5%). Other key testing aspects are also less frequently discussed: test coverage (25.5%) and mocking (9.5%). We conclude by discussing implications and future research.
Pixologic ZBrush Crack Plus Activation Key [Latest 2025] New Version![Pixologic ZBrush Crack Plus Activation Key [Latest 2025] New Version](https://cdn.slidesharecdn.com/ss_thumbnails/fashionevolution2-250322112409-f76abaa7-250428124909-b51264ff-250504160528-fc2bb1c5-thumbnail.jpg?width=560&fit=bounds)
Pixologic ZBrush Crack Plus Activation Key [Latest 2025] New Versionsaimabibi60507 Copy & Past Link👉👉
https://dr-up-community.info/
Pixologic ZBrush, now developed by Maxon, is a premier digital sculpting and painting software renowned for its ability to create highly detailed 3D models. Utilizing a unique "pixol" technology, ZBrush stores depth, lighting, and material information for each point on the screen, allowing artists to sculpt and paint with remarkable precision .
Douwan Crack 2025 new verson+ License code
Douwan Crack 2025 new verson+ License codeaneelaramzan63 Copy & Paste On Google >>> https://dr-up-community.info/
Douwan Preactivated Crack Douwan Crack Free Download. Douwan is a comprehensive software solution designed for data management and analysis.
Exploring Code Comprehension in Scientific Programming: Preliminary Insight...
Exploring Code Comprehension in Scientific Programming: Preliminary Insight...University of Hawai‘i at Mānoa This presentation explores code comprehension challenges in scientific programming based on a survey of 57 research scientists. It reveals that 57.9% of scientists have no formal training in writing readable code. Key findings highlight a "documentation paradox" where documentation is both the most common readability practice and the biggest challenge scientists face. The study identifies critical issues with naming conventions and code organization, noting that 100% of scientists agree readable code is essential for reproducible research. The research concludes with four key recommendations: expanding programming education for scientists, conducting targeted research on scientific code quality, developing specialized tools, and establishing clearer documentation guidelines for scientific software.
Presented at: The 33rd International Conference on Program Comprehension (ICPC '25)
Date of Conference: April 2025
Conference Location: Ottawa, Ontario, Canada
Preprint: https://arxiv.org/abs/2501.10037
WinRAR Crack for Windows (100% Working 2025)
WinRAR Crack for Windows (100% Working 2025)sh607827 copy and past on google ➤ ➤➤ https://hdlicense.org/ddl/
WinRAR Crack Free Download is a powerful archive manager that provides full support for RAR and ZIP archives and decompresses CAB, ARJ, LZH, TAR, GZ, ACE, UUE, .
Interactive odoo dashboards for sales, CRM , Inventory, Invoice, Purchase, Pr...
Interactive odoo dashboards for sales, CRM , Inventory, Invoice, Purchase, Pr...AxisTechnolabs Interactive Odoo Dashboard for various business needs can provide users with dynamic, visually appealing dashboards tailored to their specific requirements. such a module that could support multiple dashboards for different aspects of a business
✅Visit And Buy Now : https://bit.ly/3VojWza
✅This Interactive Odoo dashboard module allow user to create their own odoo interactive dashboards for various purpose.
App download now :
Odoo 18 : https://bit.ly/3VojWza
Odoo 17 : https://bit.ly/4h9Z47G
Odoo 16 : https://bit.ly/3FJTEA4
Odoo 15 : https://bit.ly/3W7tsEB
Odoo 14 : https://bit.ly/3BqZDHg
Odoo 13 : https://bit.ly/3uNMF2t
Try Our website appointment booking odoo app : https://bit.ly/3SvNvgU
👉Want a Demo ?📧 [email protected]
➡️Contact us for Odoo ERP Set up : 091066 49361
👉Explore more apps: https://bit.ly/3oFIOCF
👉Want to know more : 🌐 https://www.axistechnolabs.com/
#odoo #odoo18 #odoo17 #odoo16 #odoo15 #odooapps #dashboards #dashboardsoftware #odooerp #odooimplementation #odoodashboardapp #bestodoodashboard #dashboardapp #odoodashboard #dashboardmodule #interactivedashboard #bestdashboard #dashboard #odootag #odooservices #odoonewfeatures #newappfeatures #odoodashboardapp #dynamicdashboard #odooapp #odooappstore #TopOdooApps #odooapp #odooexperience #odoodevelopment #businessdashboard #allinonedashboard #odooproducts
Explaining GitHub Actions Failures with Large Language Models Challenges, In...
Explaining GitHub Actions Failures with Large Language Models Challenges, In...ssuserb14185 GitHub Actions (GA) has become the de facto tool that developers use to automate software workflows, seamlessly building, testing, and deploying code. Yet when GA fails, it disrupts development, causing delays and driving up costs. Diagnosing failures becomes especially challenging because error logs are often long, complex and unstructured. Given these difficulties, this study explores the potential of large language models (LLMs) to generate correct, clear, concise, and actionable contextual descriptions (or summaries) for GA failures, focusing on developers’ perceptions of their feasibility and usefulness. Our results show that over 80% of developers rated LLM explanations positively in terms of correctness for simpler/small logs. Overall, our findings suggest that LLMs can feasibly assist developers in understanding common GA errors, thus, potentially reducing manual analysis. However, we also found that improved reasoning abilities are needed to support more complex CI/CD scenarios. For instance, less experienced developers tend to be more positive on the described context, while seasoned developers prefer concise summaries. Overall, our work offers key insights for researchers enhancing LLM reasoning, particularly in adapting explanations to user expertise.
https://arxiv.org/abs/2501.16495
Adobe Illustrator Crack FREE Download 2025 Latest Version
Adobe Illustrator Crack FREE Download 2025 Latest Versionkashifyounis067 🌍📱👉COPY LINK & PASTE ON GOOGLE http://drfiles.net/ 👈🌍
Adobe Illustrator is a powerful, professional-grade vector graphics software used for creating a wide range of designs, including logos, icons, illustrations, and more. Unlike raster graphics (like photos), which are made of pixels, vector graphics in Illustrator are defined by mathematical equations, allowing them to be scaled up or down infinitely without losing quality.
Here's a more detailed explanation:
Key Features and Capabilities:
Vector-Based Design:
Illustrator's foundation is its use of vector graphics, meaning designs are created using paths, lines, shapes, and curves defined mathematically.
Scalability:
This vector-based approach allows for designs to be resized without any loss of resolution or quality, making it suitable for various print and digital applications.
Design Creation:
Illustrator is used for a wide variety of design purposes, including:
Logos and Brand Identity: Creating logos, icons, and other brand assets.
Illustrations: Designing detailed illustrations for books, magazines, web pages, and more.
Marketing Materials: Creating posters, flyers, banners, and other marketing visuals.
Web Design: Designing web graphics, including icons, buttons, and layouts.
Text Handling:
Illustrator offers sophisticated typography tools for manipulating and designing text within your graphics.
Brushes and Effects:
It provides a range of brushes and effects for adding artistic touches and visual styles to your designs.
Integration with Other Adobe Software:
Illustrator integrates seamlessly with other Adobe Creative Cloud apps like Photoshop, InDesign, and Dreamweaver, facilitating a smooth workflow.
Why Use Illustrator?
Professional-Grade Features:
Illustrator offers a comprehensive set of tools and features for professional design work.
Versatility:
It can be used for a wide range of design tasks and applications, making it a versatile tool for designers.
Industry Standard:
Illustrator is a widely used and recognized software in the graphic design industry.
Creative Freedom:
It empowers designers to create detailed, high-quality graphics with a high degree of control and precision.
Societal challenges of AI: biases, multilinguism and sustainability
Societal challenges of AI: biases, multilinguism and sustainabilityJordi Cabot Towards a fairer, inclusive and sustainable AI that works for everybody.
Reviewing the state of the art on these challenges and what we're doing at LIST to test current LLMs and help you select the one that works best for you
Why Orangescrum Is a Game Changer for Construction Companies in 2025
Why Orangescrum Is a Game Changer for Construction Companies in 2025Orangescrum Orangescrum revolutionizes construction project management in 2025 with real-time collaboration, resource planning, task tracking, and workflow automation, boosting efficiency, transparency, and on-time project delivery.
Get & Download Wondershare Filmora Crack Latest [2025]![Get & Download Wondershare Filmora Crack Latest [2025]](https://cdn.slidesharecdn.com/ss_thumbnails/revolutionizingresidentialwi-fi-250422112639-60fb726f-250429170801-59e1b240-thumbnail.jpg?width=560&fit=bounds)
Get & Download Wondershare Filmora Crack Latest [2025]saniaaftab72555 Copy & Past Link 👉👉
https://dr-up-community.info/
Wondershare Filmora is a video editing software and app designed for both beginners and experienced users. It's known for its user-friendly interface, drag-and-drop functionality, and a wide range of tools and features for creating and editing videos. Filmora is available on Windows, macOS, iOS (iPhone/iPad), and Android platforms.
Revolutionizing Residential Wi-Fi PPT.pptx
Revolutionizing Residential Wi-Fi PPT.pptxnidhisingh691197 Discover why Wi-Fi 7 is set to transform wireless networking and how Router Architects is leading the way with next-gen router designs built for speed, reliability, and innovation.
Landscape of Requirements Engineering for/by AI through Literature Review
Landscape of Requirements Engineering for/by AI through Literature ReviewHironori Washizaki Hironori Washizaki, "Landscape of Requirements Engineering for/by AI through Literature Review," RAISE 2025: Workshop on Requirements engineering for AI-powered SoftwarE, 2025.
Not So Common Memory Leaks in Java Webinar
Not So Common Memory Leaks in Java WebinarTier1 app This SlideShare presentation is from our May webinar, “Not So Common Memory Leaks & How to Fix Them?”, where we explored lesser-known memory leak patterns in Java applications. Unlike typical leaks, subtle issues such as thread local misuse, inner class references, uncached collections, and misbehaving frameworks often go undetected and gradually degrade performance. This deck provides in-depth insights into identifying these hidden leaks using advanced heap analysis and profiling techniques, along with real-world case studies and practical solutions. Ideal for developers and performance engineers aiming to deepen their understanding of Java memory management and improve application stability.
Top 10 Client Portal Software Solutions for 2025.docx
Top 10 Client Portal Software Solutions for 2025.docxPortli Discover the top 10 client portal software solutions for 2025. Streamline communication, ensure security, and enhance client experience.
Exceptional Behaviors: How Frequently Are They Tested? (AST 2025)
Exceptional Behaviors: How Frequently Are They Tested? (AST 2025)Andre Hora Exceptions allow developers to handle error cases expected to occur infrequently. Ideally, good test suites should test both normal and exceptional behaviors to catch more bugs and avoid regressions. While current research analyzes exceptions that propagate to tests, it does not explore other exceptions that do not reach the tests. In this paper, we provide an empirical study to explore how frequently exceptional behaviors are tested in real-world systems. We consider both exceptions that propagate to tests and the ones that do not reach the tests. For this purpose, we run an instrumented version of test suites, monitor their execution, and collect information about the exceptions raised at runtime. We analyze the test suites of 25 Python systems, covering 5,372 executed methods, 17.9M calls, and 1.4M raised exceptions. We find that 21.4% of the executed methods do raise exceptions at runtime. In methods that raise exceptions, on the median, 1 in 10 calls exercise exceptional behaviors. Close to 80% of the methods that raise exceptions do so infrequently, but about 20% raise exceptions more frequently. Finally, we provide implications for researchers and practitioners. We suggest developing novel tools to support exercising exceptional behaviors and refactoring expensive try/except blocks. We also call attention to the fact that exception-raising behaviors are not necessarily “abnormal” or rare.
Download Wondershare Filmora Crack [2025] With Latest![Download Wondershare Filmora Crack [2025] With Latest](https://cdn.slidesharecdn.com/ss_thumbnails/neo4j-howkgsareshapingthefutureofgenerativeaiatawssummitlondonapril2024-240426125209-2d9db05d-250419-250428115407-a04afffa-thumbnail.jpg?width=560&fit=bounds)
Download Wondershare Filmora Crack [2025] With Latesttahirabibi60507 Copy & Past Link 👉👉
http://drfiles.net/
Wondershare Filmora is a video editing software and app designed for both beginners and experienced users. It's known for its user-friendly interface, drag-and-drop functionality, and a wide range of tools and features for creating and editing videos. Filmora is available on Windows, macOS, iOS (iPhone/iPad), and Android platforms.
PDF Reader Pro Crack Latest Version FREE Download 2025
PDF Reader Pro Crack Latest Version FREE Download 2025mu394968 🌍📱👉COPY LINK & PASTE ON GOOGLE https://dr-kain-geera.info/👈🌍
PDF Reader Pro is a software application, often referred to as an AI-powered PDF editor and converter, designed for viewing, editing, annotating, and managing PDF files. It supports various PDF functionalities like merging, splitting, converting, and protecting PDFs. Additionally, it can handle tasks such as creating fillable forms, adding digital signatures, and performing optical character recognition (OCR).
Exploring Code Comprehension in Scientific Programming: Preliminary Insight...
Exploring Code Comprehension in Scientific Programming: Preliminary Insight...University of Hawai‘i at Mānoa
Merge hells!! Feature toggles to the rescue - DevOpsDays Madison
- 1. Merge Hells!! By @leenasn Feature Toggles to the Rescue
- 4. xTEAM
- 9. Familiar?
- 12. Building something nobody wants is the ultimate form of waste ~Eric Ries The Lean Startup
- 13. Think about how long would it take you to deliver a change of one line of code within your application to production ~Mary and Tom Poppendieck Lean Software Development, An Agile Toolkit
- 14. “Continuous Delivery is a software development discipline where you build software in such a way that the software can be released to production at any time.” http://martinfowler.com/bliki/ContinuousDelivery.html
- 16. “Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies to a shared mainline several times a day.”
- 19. Feature Toggles
- 22. ● Deploy != Release ● Avoid Rollback Hells Release Toggles
- 23. ● A/B Testing ● Canary Releasing Experimental Toggles
- 24. Ops Toggles ● Designing for failure ● Manage Circuit Breakers
- 25. Architecture?
- 28. https://www.martinfowler.com/articles/evodb.html Database Refactoring
- 29. The Dark Side
- 31. $$ Question How to manage it?
- 32. Expiry Date
- 34. Summary
- 36. Work in small batches
- 39. Leena S N @leenasn / [email protected] https://medium.com/@leenasn
- 40. References Feature Toggles - Martin Fowler's Bliki Continuous Delivery Trunk Based Development - Paul Hammant Merge Hells - Feature Toggles to the Rescue Devops Journey @ Capital One DevOps at Capital One: Focusing on Pipeline and Measurement The Death of Continuous Integration - by Steve Smith Enabling Continuous Delivery with DB - Pramod Sadalage Evolutionary Database Design - Martin Fowler, Pramod Sadalage