Testing in production with feature flags

May 26, 2018Download as pptx, pdf0 likes527 views

VSTS Community MSFT

Adopting feature flags with Visual Studio Team Services (VSTS), Azure DevOps solution, and VSTS Extensions.

Testing in production with feature flags

Init (user + hash)
getHashKey (token, vstsaccount)
hash
checkToken
getHashKey
return all user flags

ISSUE
VALUE test
if ( flag )
else
LaunchDarkly
VSTS Service
EndPoint
VSTS Extension
get flagquery flagON
OFF
SaaS Management

ISSUE
VALUE
if ( flag )
else
LaunchDarkly
VSTS Service
EndPoint
VSTS Extension
get flagquery flagON
OFF
SaaS Management

testing
ISSUE
VALUE
if ( flag )
else
ON
OFF
SaaS Management
LaunchDarkly
VSTS Service
EndPoint
VSTS Extension
get flag
Azure
Function
set flag
query flag
REST API calls

testing production
A|B testing production
Symbiosis production
FF FF

HYPOTHESIS - We believe that LaunchDarkly will … VALIDATED?
Integrate seamlessly into our VSTS extensions  Validated
Enable us to decouple deployment and exposure of extension features  Validated
Enable us to provide control down to individual user for ext. features  Validated
Enable us to make changes without deploying our extensions  Validated
Support the OSS community  Validated
Allow us to quickly switch off / revert an extension feature  Validated
Enable us to support early testing, feedback, and experimentation of
extension features
 Validated

aka.ms/vsar
@almrangers
@wpschaub
willys@microsoft.com
aka.ms/bh-ff-sos
aka.ms/vsar-launchdarkly
aka.ms/vsar-cicd-ff

Quick Reference Poster based on the DevOps @ Microsoft transformation story (https://aka.ms/devops), focused on the five habits: Customer Focus, Production First Mindset, Team Autonomy + Enterprise Alignment, Shift Left Quality, and Infrastructure as a Flexible Resource. We recommend you use the following to print the poster: - Paper: (1) Satin 160 gsm (Standard) (White) - All Pages - Page Size: Custom (16.5417 x23.3889) - Final Size: Print on 16.54 x 23.39

Poster - DevOps Planning @ MicrosoftVSTS Community MSFT

[Vssummit] DevOps - Release Management VSTSLeandro Prado

Continuous Integration and Continuous Deployment in Enterprise scenarioDavide Benvegnù

CICD by TeerapatTroublemaker Khunpech

This document discusses continuous integration and continuous delivery (CI/CD) practices. It explains that CI/CD involves automating the build, testing, and deployment process through the use of a single source repository, build automation, and self-testing to find and address problems quickly. The goal is to continuously deliver high quality software to production by building, testing, and releasing software frequently in a automated way.

How Vanguard Got to a CD-CD World by Craig SchwarzwaldSauce Labs

In this SauceCon 2019 presentation, Craig Schwarzwald discusses the main phases Vanguard software testing has undergone over the last 10+ years, from thousands of manual tests, to thousands of automated tests with Selenium, to Shifting Left, and to now focusing on Contract Testing. He discusses what Contract Testing is and talks about its importance in the CI/CD pipeline (giving the team virtually E2E coverage at the speed of Unit tests).

Accelerating DevOps Collaboration with Sauce Labs and JIRASauce Labs

How to Measure Success in Continuous Testing by Fernando Vidal and Amir Rozen...Sauce Labs

In this SauceCon 2019 talk, Fernando and Amir use observations from running 2 billion tests for thousands of Sauce Labs customers to outline the the key drivers of success in continuous testing and an provide an actionable way to see how organizations are doing relative to other successful testers. They discuss a new index which can be used by any organization to evaluate their progression towards continuous testing, and cover the components of the new continuous testing index, what makes these components such strong maturity indicators, how organizations can improve on each of the metrics, and what happens organizationally when those metrics are improved

Rapid Agile Delivery: Stories from Stash on Shipping Product More Frequentlycolleenfry

The document discusses Atlassian Stash's approach to rapid and frequent product delivery. Stash releases new versions every 5-7 weeks on average by using agile development practices like developer ownership of features, continuous integration, performance monitoring, and automating processes. Releasing often provides value to customers and feedback for developers, while maintaining quality and productivity through techniques like feature branching in git and pull requests for code reviews.

10 Deployments a day - A brief on extreme release protocolsVivek Parihar

A reflection on how we migrated from an era of production deployments once a week to more than 10 deployments a day. The story of transforming a mere sys-admin to super sophisticated DevOps team, armed with multiple tools, scripts and plugins for achieving automations, accuracy and invincible agility. As we continue on our endeavor for further improvisation, I believe its worth sharing the experience with community. Tentative topics outline: 1.Arming teams for their transformation to DevOps from mere sys-admins. 2.Killing manual deployments (manual deployment->capistrano->webistrano) 3.Automation (for daily backups,monitoring applications and servers deploying dependencies) 4.Saving up time on setting up new instances(using golden image). 5.Using LDAP to maintain servers with public key(avoiding individual logins to every server makes it less messy) 6.Using Puppet for instantiating multiple servers at once. 7.Commissioning our own Cloud Infrastructure.

Overview the Challenges and Limitations of Android App Automation with Espres...Sauce Labs

DevOps with Visual studio Release Management (Pieter Gheysens)Visug

Are you looking for an efficient way to dev/test your applications in Windows Azure and you want to track your release process by automating your deployments for repeatable success? Are you struggling with a manual and error-prone deployment process which frustrates you every day? Are you looking for automation that is the same across different environments (Dev-Test-Acceptance-Production)? Do you need to build/package your application only once and deploy it with the exact same bits to any provisioned environment? Do you want to setup a formal approval workflow to promote a release to the next stage? If so, come and learn about the new release management features in Visual Studio Team Services.

Continuous Deployment Pipeline for Systems at Cascadia IT Conference - 2017-0...garrett honeycutt

Don’t Settle for Old-school SCM: Fail Faster? How about Don’t Fail at All?Compuware

Can your Source Code Management (SCM) tool help your business compete in the digital economy? Why settle for old-school SCM when you don’t have to? In this brief webcast, our experts demo a copybook change within ISPW, highlighting: - Impact Analysis with rich visualization. See how a code change might impact the rest of the mainframe environment, saving you from rework. - Topaz integration. With access to Topaz for Program Analysis through the Topaz Workbench, you can dig deeper into code details to better understand complex application logic. Our experts also show how generating, promoting, testing and approving code is made easier and more efficient with ISPW.

Práticas, Técnicas e Ferramentas para Continuous Delivery com ALMMarcelo Sousa Ancelmo

DevOps and Continuous Delivery with Visual Studio 2015 and VSTSSolidify

Som utvecklare är det ofta självklart att kodandet är den viktigaste aktiviteten i projektet. Men om inte funktioner för releaseplanering, källkodshantering, deployment och testning finns på plats så är det vanligt att dessa aktiviteter tar en stor del av utvecklingsarbetet. DevOps och Continuous Delivery är synsätt som vi använder för att säkerställa snabba leveranser av god kvalitet. Microsoft Azure och Visual Studio har mängder av funktioner som underlättar arbetet så att arbetssätt och verktyg samverkar på ett effektivt sätt. I detta seminarium kommer vi att förklara vad DevOps är för något och hur detta synsätt kan användas för att säkerställa snabba leveranser med god kvalitet. DevOps hjälper oss överbrygga arbetet i utveckling och drift med fokus på att säkerställa leverenspresision och kvalitet, bland annat genom att se till att bra lösningar för applikationsövervakning, felrapportering, paketering och deployment finns på plats. Den andra delen vi kommer fokusera på är Continuous Delivery. Med den senaste versionen av Visual Studio Release Management visar vi vad Continuous Delivery är genom att sätta upp en komplett lösning som automatiskt tar kod till produktion. I Visual Studio 2015 sviten har vi ett helt nytt byggsystem och väl integrerade lösningar kring release management, deployment och automatiserad testning som gör plattformen förträfflig för att implementera en continuous delivery process. För att så snabbt och enkelt som möjligt tillgodogöra oss dessa koncept kommer vi använda molnplattformarna Azure och Visual Studio Online, med dessa kan vi flytta utvecklingsplattformen till molnet och få helt nya förutsättningar för snabbare releaser. Så missa inte denna chans att vara en av de första att se en komplett Continuous Delivery-lösning byggd på den senaste Microsofttekniken!

DevOps and All the Continuouses w/ Helen BealSonatype

DevOps promises to make better software faster and more safely and many organizations begin by practicing Continuous Integration and moving on to Continuous Delivery and sometimes even extending as far as Continuous Deployment - but this is only the tip of the iceberg. DevOps demands a fundamental shift in the way we work and requires all participants in an organization to live its principles. It’s much more than a tool chain. When you are delivering software in an Agile manner in fortnightly sprints, are you still funding in an annual manner? Are you adhering to The Third Way? I.e. are you practicing Continuous Experimentation? Continuous Learning? How are you doing Continuous Testing? Are you including security in that? Have you have Continuous Improvement in your organization for years? When does Continuous Everything turn into Continuous Apathy?

The Push From Within - A Journey of Transformation at Walmart Labs by Claude ...Sauce Labs

Claude Jones, Sr. Director of Engineering at Walmart Labs, provides an inside look of what it took to push from within and help one of the world’s largest companies adopt a culture of quality. His presentation covers identifying the right project, building the right team structure, removing the fear of change, providing value with the right metrics, making testing fun and reinforcing the benefits. This case study will challenge you to re-think your approach or empower you to stay on your current path of adopting a culture of quality.

Automated Testing at The Speed of Headless by Alissa Lydon and Samantha CoffmanSauce Labs

In this SauceCon 2019 presentation, Samantha Coffman, Product Manager at Sauce Labs, and Alissa Lydon, Product Marketing Manager at Sauce Labs, discuss Sauce Headless, the industry’s first cloud-based headless testing solution, making it a fast and affordable option for early pipeline testing at scale. They will cover the benefits of using Sauce Headless in conjunction with Sauce Labs traditional VM offering to increase the release velocity, as well as examples of customers who are experiencing upwards of 50% faster test times using Sauce Headless.

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 Delivery with TFS msbuild msdeployPeter Gfader

This document discusses automating software deployments using tools like msbuild and msdeploy to enable continuous deployment and delivery. It outlines the pain points of manual deployments and goals of automating deployments. It provides guidance on setting up continuous integration, automated testing, packaging, and configuration for both new systems and existing environments. It also lists best practices like deploying early, having rollback plans, logging builds, and automating as much as possible.

Qa in CI/CDAdsmurai

The document discusses continuous integration (CI), continuous delivery (CD), and the QA perspective in CI/CD processes. It provides the following key points: 1. CI involves integrating code into a shared repository multiple times per day and running automated builds and tests on each check-in to detect problems early. CD aims to reliably and quickly deploy changes to production or users. 2. From a QA perspective, traditional CI approaches find defects late as testing is manual, while CI/CD aims to automatically deploy and test on each build to provide faster feedback. 3. Automated testing is critical, including unit, integration, and regression tests run in environments similar to production to ensure quality with each build.

How To Use Jenkins for Continuous Load and Mobile Testing with SOASTA & Cloud...SOASTA

How to use Jenkins for Continuous Load Testing and Mobile Automation Today’s rapid development pace demands continuous testing, and Jenkins, the leading open source automation platform, has emerged as the hub of continuous delivery. SOASTA and CloudBees have tapped Jenkins to enable more test types and approaches that utilize cloud and agile processes for higher quality apps. Join this free webinar and learn: How to use Jenkins for continuous delivery and load testing of mobile applications How to incorporate cloud resources into your development and test environments Using the largest global test cloud for load generation CloudBees’ on premise, in the cloud and hybrid solutions for continuous delivery with Jenkins SOASTA’s Jenkins plugins for testing with real mobile devices and tracking performance baselines Experts from both companies will share stories and demonstrations that will help you implement a continuous approach to quality.

Continuous delivery in QbonJaric Kuo

The document discusses continuous delivery (CD) and how it is implemented. CD aims to enable constant changes to production via an automated software production line. Key aspects of the implementation include: extensive unit and functional testing covering at least 70% code coverage; testing in all environments before deployment; automated checks for coding style, syntax and copy/paste detection during development; merging and deploying through automated pipelines triggered by code changes; using tools like Runscope for API testing across environments with assertions; and deploying to environments like integration, staging and production through one-click deployment. The approach has led to deployments three times a day compared to every two weeks previously, and fewer production issues.

Microsoft app centerSuki Huang

Continuous integration - main principlesLena Petsenchuk

This document discusses continuous integration (CI), including an overview of CI, its principles, and advantages and disadvantages. CI is a software development practice where developers regularly merge code changes into a central repository, which then triggers an automated build and test of the code. The principles of CI are to maintain a code repository, automate builds and deployments, make builds self-testing, commit to mainline daily, build every commit, keep builds fast, test in a production-like environment, and make builds easily accessible. Advantages are easy code reversion, early issue detection, immediate testing and feedback, while disadvantages are initial setup time and needing a test suite.

Introduction to Application insightsGian Maria Ricci

This document discusses Application Insights, a service that provides automatic instrumentation of applications to monitor application health and performance. It provides an overview of logging benefits, costs of logging, and how Application Insights addresses these. The document outlines how Application Insights can instrument applications automatically or with custom logging, and demonstrates setting up synthetic monitors and custom logging.

Top 8 mistakes developer teams make in their first serverless projectPaul Swail

vCenter Orchestrator APIsPablo Roesch

This document provides an overview of integrating with VMware vCenter Orchestrator (vCO). It discusses what orchestration is and the benefits it provides. It describes how vCO is distributed and its architecture. It covers the two main ways to integrate with vCO: the web service API and the plugin API. The web service API allows remote workflow execution and status checks. The plugin API allows exposing external systems for use in vCO workflows. It provides examples of using the Java bindings for the web service API and discusses the structure of a vCO plugin.

From Web App Model Design to Production with WakandaAlexandre Morgaut

There is many interesting platforms out there to develop Web applications, like .NET, Spring, ruby on rails, Django, LAMP, Meteor, and so on. In this presentation, you will discover Wakanda a Model driven NoSQL / SSJS platform built on Web standards. You will see how a project starts, can be designed, tested, developed by a team, debugged, administrated, maintained, and then how to update it in the future. We will compare to some existing platforms and why Wakanda could make you more efficient.

More Related Content

What's hot (20)