This talk covers the importance of automated testing in the proper Continuous Delivery process. Different types of testing are covered in the talk along with how to apply them.
Versioning schemes and branching models for Continuous Delivery - Continuous ...Pavel Chunyayev
There are many different versioning schemes and branching models. Although there’s no golden standard, some of them suit Continuous Delivery more than others. Both branching and versioning are fundamental to the software development life cycle and
I discussed different methods that communities developed over years along with their advantages and disadvantages.
This document discusses feedback in the continuous delivery process. It notes that feedback is information about actions that is returned to the source of those actions. In continuous delivery, there are several types of testing that provide important feedback, including unit, integration, contract, end-to-end, performance, exploratory, and resilience testing. Tests should be created by both developers and testers to catch bugs and ensure stability as code is delivered frequently. Continuous feedback allows for continuous improvement of developing and releasing high quality software.
DOES SFO 2016 - Ray Krueger - Speed as a Prime DirectiveGene Kim
Speed as a Prime Directive
Ray Krueger, Vice President of Engineering, Hyatt Hotels Corporation
Hyatt is transforming into a technology company that delivers digital experiences in the Hospitality industry. We're applying Continuous Delivery in order to achieve our goals faster. In the process, we are simplifying and abstracting legacy environments and building a hospitality technology platform.
Tries to evoke some interest in EVM w.r.t agile values and principles based software delivery. Intention is only to invoke curiosity and aid further R&D.
The document discusses building a high-performance testing team. It recommends assembling a team that includes a performance architect, senior performance engineer, and performance engineer. The team should focus on skills like testing, architecture, and requirements rather than just tools. The document outlines a four-level approach to performance testing: 1) coding for performance, 2) attacking service levels, 3) end-to-end business process testing, and 4) full site testing with monitoring of key performance indicators.
O'Reilly Webcast: How Nordstrom Prepares Its Site for Holidays and Major EventsSOASTA
This document discusses how to prepare a website for holidays and major events by focusing on performance. It recommends taking a continuous improvement approach of analyzing site usage data, testing for performance issues, and monitoring site performance during events. Key steps include studying past events to understand customer impacts, projecting future usage, contingency planning, and building a feedback loop between development, product management, and engineering. The goal is to adopt a culture where performance is a key feature and the site is always being prepared through continuous delivery, instrumentation, and addressing issues before they affect customers.
Versioning schemes and branching models for Continuous Delivery - Continuous ...Pavel Chunyayev
There are many different versioning schemes and branching models. Although there’s no golden standard, some of them suit Continuous Delivery more than others. Both branching and versioning are fundamental to the software development life cycle and
I discussed different methods that communities developed over years along with their advantages and disadvantages.
This document discusses feedback in the continuous delivery process. It notes that feedback is information about actions that is returned to the source of those actions. In continuous delivery, there are several types of testing that provide important feedback, including unit, integration, contract, end-to-end, performance, exploratory, and resilience testing. Tests should be created by both developers and testers to catch bugs and ensure stability as code is delivered frequently. Continuous feedback allows for continuous improvement of developing and releasing high quality software.
DOES SFO 2016 - Ray Krueger - Speed as a Prime DirectiveGene Kim
Speed as a Prime Directive
Ray Krueger, Vice President of Engineering, Hyatt Hotels Corporation
Hyatt is transforming into a technology company that delivers digital experiences in the Hospitality industry. We're applying Continuous Delivery in order to achieve our goals faster. In the process, we are simplifying and abstracting legacy environments and building a hospitality technology platform.
Tries to evoke some interest in EVM w.r.t agile values and principles based software delivery. Intention is only to invoke curiosity and aid further R&D.
The document discusses building a high-performance testing team. It recommends assembling a team that includes a performance architect, senior performance engineer, and performance engineer. The team should focus on skills like testing, architecture, and requirements rather than just tools. The document outlines a four-level approach to performance testing: 1) coding for performance, 2) attacking service levels, 3) end-to-end business process testing, and 4) full site testing with monitoring of key performance indicators.
O'Reilly Webcast: How Nordstrom Prepares Its Site for Holidays and Major EventsSOASTA
This document discusses how to prepare a website for holidays and major events by focusing on performance. It recommends taking a continuous improvement approach of analyzing site usage data, testing for performance issues, and monitoring site performance during events. Key steps include studying past events to understand customer impacts, projecting future usage, contingency planning, and building a feedback loop between development, product management, and engineering. The goal is to adopt a culture where performance is a key feature and the site is always being prepared through continuous delivery, instrumentation, and addressing issues before they affect customers.
The document discusses load testing best practices for peak seasons. It recommends measuring site performance now, prioritizing issues, and optimizing the site. Key things to test include popular session paths and peak load times. Testing should start early and continue through development, staging, and production. Automated testing allows for continuous testing. The goal is to measure, optimize, and repeat testing to ensure peak performance.
QASymphony Atlanta Customer User Group Fall 2017QASymphony
Thanks to all who came out and were part of our first customer user group! All our expectations for the day were exceeded and we hope you feel the same way.
If you weren't able to make it, here's what you missed:
Judy Chung, Product Manager, gave a summary of recent and upcoming features (site level fields, new UI of TestPad) as well as a sneak preview of our newest product (codename: Automation Hub).
Elise Carmichael, VP of Quality, demo-ed several best practice topics, ranging from organizing your qTest repository to reviewing the different automation integration options.
Erika Chestnut, Director of QA at Sterling Talent Solutions, shared her story as a QASymphony customer who recently replaced HP Quality Center with qTest and provided insight into leading change management across her organization.
Augmenting Regression Testing in Agile TeamsTechWell
Today, three things are undeniable facts of business—projects are becoming more agile, teams are learning to function well remotely, and the tester’s role is evolving. Mike Hrycyk believes that testers in agile teams face daunting challenges and often struggle to keep up with the pace of new feature development while performing all the needed regression testing activities. Mike offers a strategy as an alternate path: the creation of a regression testing team to augment feature teams, one that works in parallel, handling the testing regression cycle while the feature teams—developers and testers—continue to work through new development. Mike offers tips for successful feature handoff, intra-team communication, and troubleshooting hurdles that will be encountered. Although augmented regression testing is at odds with the advice of many agile “experts,” it enabled their agile development to achieve higher velocity.
This presentation discusses continuous database deployments. It begins with an introduction of the presenter and an overview of topics to be covered. It then contrasts manual database change management with continuous deployment. The main methods covered are schema-based, using the database schema in source control; script-based, using change scripts; and code-based, coding database changes. Benefits include reduced errors and faster releases. Best practices discussed include backing up data and deploying breaking changes in steps. The presentation concludes with a call for questions.
Addressing the elephant through persistence and perseveranceRanjeet Pethe
This is the presentation from the #lastconf 2017 enjoy and please feedback. I talk about 3 big elephants which we finally tamed...automated testing, CI and CD in a datawarehouse project
SPSOttawa Release Pipepline for SharePoint office 365 in AzureVincent Biret
This document summarizes a presentation on setting up a release pipeline for SharePoint projects in Azure. The presentation covered topics like introducing software lifecycles and tools like Visual Studio Team Services and Azure. It discussed setting up automated builds, deployments with Release Management and testing at different stages. It also touched on managing technical debt through practices like code reviews, static analysis and rewriting code. The presentation included demos of building, deploying and testing a SharePoint project hosted in Azure.
The document discusses continuous testing in DevOps. It introduces SOASTA and their products for load and performance testing (CloudTest) and mobile functional test automation (TouchTest). SOASTA advocates for continuous integration with small batches, version control, automation, and continuous feedback to align development and testing teams. The presentation provides examples of how SOASTA's clients implement continuous integration by running unit tests and load tests on every code change through Jenkins and addressing issues before deployment.
Building Better Collaboration Between Development and Testing in a DevOps WorldQASymphony
This document discusses collaboration between development and testing teams in DevOps. It notes that most organizations now practice agile development and many are adopting DevOps. When testing is integrated into frequent code deployments, it allows for much higher performance. The document advocates for promoting collaboration across teams through practices like clarifying requirements upfront, adopting test-first approaches using behavior-driven development, and integrating testing feedback directly into builds for continuous feedback. It discusses capabilities needed like visibility into testing, consolidated dashboards, and integration with version control systems. The goal is to move testing earlier in the process and continuously deliver high quality software through better collaboration.
Agile without DevOps is incomplete as DevOps helps align development and operations teams to improve customer experiences and respond faster to business needs. DevOps utilizes automation, collaboration between teams, and continuous delivery to support Agile principles like iterative delivery and adapting to change. Specifically, DevOps automates testing, deployment, monitoring and other processes to enable Agile teams to release working software more frequently with high quality and reliability.
Moving QA from Reactive to Proactive with qTestQASymphony
This document discusses moving quality assurance from a reactive to a proactive approach using qTest. It outlines some of the challenges with the current reactive approach, such as crashes occurring and teams blaming the QA team. It then discusses how to take a more proactive approach by efficiently creating and organizing tests, monitoring tests, reusing tests and parameters, consolidating results, and defining test scenarios before coding using behavior driven development. The key recommendations are to record manual and exploratory tests, use a test management system that promotes reuse, radiate test results to development systems, build combined testing dashboards, and use BDD to ensure early test planning.
This document outlines a webinar presentation on performance testing. It discusses how performance testing needs to change to keep up with trends like increased application development, continuous delivery, and more demanding users. Traditional approaches using siloed teams and infrequent testing are outdated. The presentation provides tips on breaking the status quo by increasing test frequency, embracing mobile applications, and integrating performance testing into agile development teams throughout the software lifecycle. Distributed, collaborative performance testing driven by real user data is presented as the new modern approach.
Integrating Cloud-based performance test in VSTS with SOASTA CloudTestJennifer Finney
Being ready for peak traffic requires testing at scale, and there is no better place to do that than from the cloud. With the Azure cloud's worldwide network of data centers, and CloudTest from SOASTA, you can generate realistic load against your site to ensure that it can handle expected traffic, and beyond, and perform well. Learn how to move your performance testing to CloudTest and test at scale in the Azure cloud with the virtual machine from the Azure Marketplace.
A Blueprint for a Successful DevOps MetamorphosisXebiaLabs
The document discusses a customer's challenges in adopting DevOps practices and how they were able to successfully implement a DevOps transformation. Some of the key challenges included developers spending too much time setting up environments and a lack of standardized processes. The customer implemented a new code delivery framework using a cloud-agnostic architecture and automation to achieve continuous delivery. This allowed two satellites to be launched within a year, significantly faster than the previous 3 year timeframe. The document provides recommendations around toolchain strategy, governance, practices like continuous integration, and areas of focus like automation.
What we've learnt and what we want to put in practice from recent conferences. A summary by Neil Frawley, Sam Thwaites and Shaw Innes about a trip to the 2016 DevOps Enterprise Summit in San Francisco.
Presented at the January 2017 Brisbane DevOps Meetup Group
DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...Gene Kim
Lessons Learned from a Parallel Universe
David N. Blank-Edelman, Technical Evangelist, Apcera
Just within the last ten or so years, we have seen at least two separate communities evolve at the crossroads of development and operations. The first—DevOps—grew up very much in public, the second matured sequestered within the halls of “special” companies like Google and Facebook and is only now starting to gain visibility and traction in the wider world. The DevOps and Site Reliability Engineering (SRE) communities barely speak, yet both have common ancestors and much to offer each other. Let’s look at what they have in common, how they differ, and what are the key things we can learn from both.
DevOps Enterprise Summit San Francisco 2016
Product Managers are from Pluto and UXers are from UranusProduct Anonymous
Product Managers are from Pluto* and UXers are from Uranus - a practical guide for improving communication and getting what you want from your relationships.
Session approach:
There are a lot of similarities between Product Managers and UXers in how we think and the work we do but we also see things differently. Hear from a panel of Product & UX folks and their secrets of working collaboratively with each other including:
• How they work together as a team
• What works? What doesn't?
• Where are the potential conflict points between Product & UX - and how to prevent them!
• How they've changed their approach over time
Panel members:
- Aconex – Mark Smith / Senior Product Manager & David McNamara / UX Designer
- MYOB – Russell Kallman / Senior Product Manager & Scott Turner / UX Design Lead
- Seek – Nicole Brolan / Product Manager & Vedran Arnautovic / Senior User Experience Designer
- REA - Chris Kwan / Consumer Product Manager & Ricky Synnot / Senior Experience Designer
*The 'object' formerly known as the Planet
Using JMeter in CloudTest for Continuous TestingSOASTA
The document discusses SOASTA's Spring Release of their CloudTest product. Some key highlights include new features like network emulation, version control integration, and first class support for the popular open source load testing tool JMeter. It also covers trends around shifting performance testing left into development and right from development into production environments.
What Retailers Know About Performance and User ExperienceSOASTA
The document discusses a presentation by SOASTA on optimizing retail website performance. It outlines the agenda which includes retail case studies, considerations from optimizing performance, and SOASTA's solutions for measuring and testing user performance. It then shares case studies of retailers who worked with SOASTA to test and improve their websites, reducing issues and increasing sales.
Final tips holiday readiness 2015 for slide shareSOASTA
Join us for this fast-paced webinar as two web and mobile performance experts share five tactics you can deploy immediately do squeeze the most out of the applications and infrastructure you already have.
• How government agencies have an increased opportunity to engage their citizens by adopting open source solutions
• How agencies can remove blockers and enable more engaging digital services
Leveraging open government platforms to foster better dialog and engage citizens at a far deeper level than is currently possible
The document discusses load testing best practices for peak seasons. It recommends measuring site performance now, prioritizing issues, and optimizing the site. Key things to test include popular session paths and peak load times. Testing should start early and continue through development, staging, and production. Automated testing allows for continuous testing. The goal is to measure, optimize, and repeat testing to ensure peak performance.
QASymphony Atlanta Customer User Group Fall 2017QASymphony
Thanks to all who came out and were part of our first customer user group! All our expectations for the day were exceeded and we hope you feel the same way.
If you weren't able to make it, here's what you missed:
Judy Chung, Product Manager, gave a summary of recent and upcoming features (site level fields, new UI of TestPad) as well as a sneak preview of our newest product (codename: Automation Hub).
Elise Carmichael, VP of Quality, demo-ed several best practice topics, ranging from organizing your qTest repository to reviewing the different automation integration options.
Erika Chestnut, Director of QA at Sterling Talent Solutions, shared her story as a QASymphony customer who recently replaced HP Quality Center with qTest and provided insight into leading change management across her organization.
Augmenting Regression Testing in Agile TeamsTechWell
Today, three things are undeniable facts of business—projects are becoming more agile, teams are learning to function well remotely, and the tester’s role is evolving. Mike Hrycyk believes that testers in agile teams face daunting challenges and often struggle to keep up with the pace of new feature development while performing all the needed regression testing activities. Mike offers a strategy as an alternate path: the creation of a regression testing team to augment feature teams, one that works in parallel, handling the testing regression cycle while the feature teams—developers and testers—continue to work through new development. Mike offers tips for successful feature handoff, intra-team communication, and troubleshooting hurdles that will be encountered. Although augmented regression testing is at odds with the advice of many agile “experts,” it enabled their agile development to achieve higher velocity.
This presentation discusses continuous database deployments. It begins with an introduction of the presenter and an overview of topics to be covered. It then contrasts manual database change management with continuous deployment. The main methods covered are schema-based, using the database schema in source control; script-based, using change scripts; and code-based, coding database changes. Benefits include reduced errors and faster releases. Best practices discussed include backing up data and deploying breaking changes in steps. The presentation concludes with a call for questions.
Addressing the elephant through persistence and perseveranceRanjeet Pethe
This is the presentation from the #lastconf 2017 enjoy and please feedback. I talk about 3 big elephants which we finally tamed...automated testing, CI and CD in a datawarehouse project
SPSOttawa Release Pipepline for SharePoint office 365 in AzureVincent Biret
This document summarizes a presentation on setting up a release pipeline for SharePoint projects in Azure. The presentation covered topics like introducing software lifecycles and tools like Visual Studio Team Services and Azure. It discussed setting up automated builds, deployments with Release Management and testing at different stages. It also touched on managing technical debt through practices like code reviews, static analysis and rewriting code. The presentation included demos of building, deploying and testing a SharePoint project hosted in Azure.
The document discusses continuous testing in DevOps. It introduces SOASTA and their products for load and performance testing (CloudTest) and mobile functional test automation (TouchTest). SOASTA advocates for continuous integration with small batches, version control, automation, and continuous feedback to align development and testing teams. The presentation provides examples of how SOASTA's clients implement continuous integration by running unit tests and load tests on every code change through Jenkins and addressing issues before deployment.
Building Better Collaboration Between Development and Testing in a DevOps WorldQASymphony
This document discusses collaboration between development and testing teams in DevOps. It notes that most organizations now practice agile development and many are adopting DevOps. When testing is integrated into frequent code deployments, it allows for much higher performance. The document advocates for promoting collaboration across teams through practices like clarifying requirements upfront, adopting test-first approaches using behavior-driven development, and integrating testing feedback directly into builds for continuous feedback. It discusses capabilities needed like visibility into testing, consolidated dashboards, and integration with version control systems. The goal is to move testing earlier in the process and continuously deliver high quality software through better collaboration.
Agile without DevOps is incomplete as DevOps helps align development and operations teams to improve customer experiences and respond faster to business needs. DevOps utilizes automation, collaboration between teams, and continuous delivery to support Agile principles like iterative delivery and adapting to change. Specifically, DevOps automates testing, deployment, monitoring and other processes to enable Agile teams to release working software more frequently with high quality and reliability.
Moving QA from Reactive to Proactive with qTestQASymphony
This document discusses moving quality assurance from a reactive to a proactive approach using qTest. It outlines some of the challenges with the current reactive approach, such as crashes occurring and teams blaming the QA team. It then discusses how to take a more proactive approach by efficiently creating and organizing tests, monitoring tests, reusing tests and parameters, consolidating results, and defining test scenarios before coding using behavior driven development. The key recommendations are to record manual and exploratory tests, use a test management system that promotes reuse, radiate test results to development systems, build combined testing dashboards, and use BDD to ensure early test planning.
This document outlines a webinar presentation on performance testing. It discusses how performance testing needs to change to keep up with trends like increased application development, continuous delivery, and more demanding users. Traditional approaches using siloed teams and infrequent testing are outdated. The presentation provides tips on breaking the status quo by increasing test frequency, embracing mobile applications, and integrating performance testing into agile development teams throughout the software lifecycle. Distributed, collaborative performance testing driven by real user data is presented as the new modern approach.
Integrating Cloud-based performance test in VSTS with SOASTA CloudTestJennifer Finney
Being ready for peak traffic requires testing at scale, and there is no better place to do that than from the cloud. With the Azure cloud's worldwide network of data centers, and CloudTest from SOASTA, you can generate realistic load against your site to ensure that it can handle expected traffic, and beyond, and perform well. Learn how to move your performance testing to CloudTest and test at scale in the Azure cloud with the virtual machine from the Azure Marketplace.
A Blueprint for a Successful DevOps MetamorphosisXebiaLabs
The document discusses a customer's challenges in adopting DevOps practices and how they were able to successfully implement a DevOps transformation. Some of the key challenges included developers spending too much time setting up environments and a lack of standardized processes. The customer implemented a new code delivery framework using a cloud-agnostic architecture and automation to achieve continuous delivery. This allowed two satellites to be launched within a year, significantly faster than the previous 3 year timeframe. The document provides recommendations around toolchain strategy, governance, practices like continuous integration, and areas of focus like automation.
What we've learnt and what we want to put in practice from recent conferences. A summary by Neil Frawley, Sam Thwaites and Shaw Innes about a trip to the 2016 DevOps Enterprise Summit in San Francisco.
Presented at the January 2017 Brisbane DevOps Meetup Group
DOES16 San Francisco - David Blank-Edelman - Lessons Learned from a Parallel ...Gene Kim
Lessons Learned from a Parallel Universe
David N. Blank-Edelman, Technical Evangelist, Apcera
Just within the last ten or so years, we have seen at least two separate communities evolve at the crossroads of development and operations. The first—DevOps—grew up very much in public, the second matured sequestered within the halls of “special” companies like Google and Facebook and is only now starting to gain visibility and traction in the wider world. The DevOps and Site Reliability Engineering (SRE) communities barely speak, yet both have common ancestors and much to offer each other. Let’s look at what they have in common, how they differ, and what are the key things we can learn from both.
DevOps Enterprise Summit San Francisco 2016
Product Managers are from Pluto and UXers are from UranusProduct Anonymous
Product Managers are from Pluto* and UXers are from Uranus - a practical guide for improving communication and getting what you want from your relationships.
Session approach:
There are a lot of similarities between Product Managers and UXers in how we think and the work we do but we also see things differently. Hear from a panel of Product & UX folks and their secrets of working collaboratively with each other including:
• How they work together as a team
• What works? What doesn't?
• Where are the potential conflict points between Product & UX - and how to prevent them!
• How they've changed their approach over time
Panel members:
- Aconex – Mark Smith / Senior Product Manager & David McNamara / UX Designer
- MYOB – Russell Kallman / Senior Product Manager & Scott Turner / UX Design Lead
- Seek – Nicole Brolan / Product Manager & Vedran Arnautovic / Senior User Experience Designer
- REA - Chris Kwan / Consumer Product Manager & Ricky Synnot / Senior Experience Designer
*The 'object' formerly known as the Planet
Using JMeter in CloudTest for Continuous TestingSOASTA
The document discusses SOASTA's Spring Release of their CloudTest product. Some key highlights include new features like network emulation, version control integration, and first class support for the popular open source load testing tool JMeter. It also covers trends around shifting performance testing left into development and right from development into production environments.
What Retailers Know About Performance and User ExperienceSOASTA
The document discusses a presentation by SOASTA on optimizing retail website performance. It outlines the agenda which includes retail case studies, considerations from optimizing performance, and SOASTA's solutions for measuring and testing user performance. It then shares case studies of retailers who worked with SOASTA to test and improve their websites, reducing issues and increasing sales.
Final tips holiday readiness 2015 for slide shareSOASTA
Join us for this fast-paced webinar as two web and mobile performance experts share five tactics you can deploy immediately do squeeze the most out of the applications and infrastructure you already have.
• How government agencies have an increased opportunity to engage their citizens by adopting open source solutions
• How agencies can remove blockers and enable more engaging digital services
Leveraging open government platforms to foster better dialog and engage citizens at a far deeper level than is currently possible
fondo emprendedor sena Carla Juliana vargas _1004Carla Rodriguez
El Fondo Emprender es un fondo de capital semilla independiente adscrito al Servicio Nacional de Aprendizaje (SENA) que financia iniciativas empresariales desarrolladas por alumnos del SENA que han finalizado su etapa lectiva. El fondo fue creado por la ley 789 de 2002 y su presupuesto proviene en un 80% de la monetización de la cuota de aprendizaje.
Este documento presenta breves resúmenes biográficos de cinco de los mejores jugadores de baloncesto de la historia de la NBA: Kareem Abdul-Jabbar, Bill Russell, Michael Jordan, Wilt Chamberlain y Lebron James. Detalla sus logros individuales y con sus respectivos equipos, incluyendo títulos, premios MVP y récords establecidos.
A/B Testing Data-Driven Algorithms in the Cloud - WebinarRoberto Turrin
We present how A/B testing can be used to evaluate the performance of Machine Learning algorithms.
We explore the different evaluation approaches - from offline evaluation to online evaluation - with a particular focus on long-term KPIs and on the recent Cloud-based technologies that can facilitate the development and integration of A/B testing.
This document discusses the differences and similarities between interpretation and translation. Interpretation involves orally translating spoken language in real-time, while translation involves written text and can take more time as it requires understanding culture. Both interpretation and translation serve to transfer meaning between languages through text.
El documento describe varias barreras que dificultan el acceso a la justicia para personas pobres, como barreras económicas, geográficas, culturales y de género. Luego presenta datos sobre varios obstáculos en países centroamericanos como falta de juzgados, desconocimiento de derechos y falta de defensores públicos. Finalmente, discute algunas propuestas del Poder Judicial hondureño para garantizar el servicio legal gratuito a grupos vulnerables.
Este documento resume la música salsa, incluyendo sus orígenes en Latinoamérica, características como la melodía y armonía, formas de baile como la cubana y puertorriqueña, influencias en países como Colombia y Estados Unidos, y figuras importantes como Cheo Feliciano y Celia Cruz. También menciona festivales de salsa en Colombia, Nueva York y otros lugares, así como canciones clásicas del género.
Este documento trata sobre ecuaciones de primer y segundo grado. Explica que una ecuación dice que dos lados son iguales y que resolver una ecuación significa encontrar los valores de la variable que hacen que la igualdad sea cierta. Luego describe que una ecuación de primer grado tiene una variable y que una ecuación de segundo grado puede reducirse a la forma ax^2 + bx + c, clasificándolas como completas o incompletas. Finalmente, indica que solucionar una ecuación de segundo grado es averiguar qué valor(es) convierten la ecuación
This short document does not contain any text to summarize. It appears to be blank or missing content. I am unable to generate a meaningful summary with 3 sentences or less as there is no information provided in the document to summarize.
Este documento presenta un resumen de un proyecto de investigación realizado por dos estudiantes sobre el Capitán América. El proyecto siguió el modelo Gavilán para la búsqueda de información, identificando el problema de investigación inicial y preguntas secundarias. Los estudiantes buscaron y seleccionaron fuentes confiables, analizando la información para responder las preguntas planteadas. Concluyeron que la Segunda Guerra Mundial influyó en la creación del personaje debido a la inspiración que brindó al cread
Pablo Carrasco es un artista digital que utiliza el software libre Inkscape para crear ilustraciones vectoriales. Ha creado cientos de obras de arte originales y tutoriales para ayudar a otros artistas a mejorar sus habilidades con Inkscape. Sus ilustraciones vectoriales a menudo representan paisajes naturales de manera estilizada.
The document provides an orientation for a university bookstore, outlining the bookstore's services which include clothing, convenience stores, electronics, shipping and receiving, textbooks, trade books, and vouchers. An organizational chart is presented showing Sonda J. Reinartz as the Director, and managers for operations, course materials, customer service, clothing/soft goods, and electronics. The test password provided is "Bears".
Modern software systems are becoming increasingly complex. To meet the quality, availability, and security demands of the modern web, scalable infrastructure tools are necessary. And these systems are changing rapidly to keep up with the needs of end-users. Join our DevOps expert Ben Lambert to learn the basics about DevOps and what's changing for modern developers and architects.
Erste Facebook-Ad-Benchmark-Studie in Deutschland für die B2B-Branche #AFBMCAllFacebook.de
Vortrag von Anna-Maria Zahn und Stefan Hauck auf der AllFacebook Marketing Conference 2014 in Berlin.
Mehr Informationen:
http://conference.allfacebook.de/
El documento describe diferentes tipos de tangencias entre curvas geométricas que se vieron en clase, incluyendo rectas tangentes a circunferencias desde puntos exteriores, circunferencias tangentes a otras circunferencias conociendo sus radios y puntos de tangencia, circunferencias tangentes a una recta que pasen por un punto dado, circunferencias tangentes a dos rectas paralelas que pasen por un punto interior, y circunferencias tangentes a una recta y otra circunferencia dada.
The document discusses the benefits of continuous testing including reduced time to market, increased architecture complexity handling, smaller and more efficient teams, automation throughout the lifecycle, reduced costs, early failure detection, and quicker feedback. It also identifies challenges around people, processes, tools, and technology integration. The current approach is shown as a continuous testing pipeline with various stages like unit testing, deployment environments, and monitoring. The near future approach envisions optimizing value streams, continuous delivery pipelines, DevSecOps, functional programming, cloud/microservices, and an open framework to support innovations.
State of continuous delivery in 2015 - Minsk 15-5-2015Pavel Chunyayev
The presentation gives high-level overview of most important aspects of implementing Continuous Delivery comparing CD with Agile, DevOps and Lean software development.
Matt Callanan takes the 15 chapters of the famous "Continuous Delivery" book by Jez Humble & Dave Farey and distills it down into 1 hour of convincing arguments, walking through the pieces involved to make it happen including cultural challenges, automated testing, automated deployment & deployment pipelines. Not sure how to get started with DevOps? Finding it hard to convince colleagues & managers that CD is the way forward? Matt has used this presentation to help facilitate enterprise-wide adoption of Continuous Delivery. Slides from a presentation given at DevOps Brisbane March 2014.
In the software industry you'll often hear the words Testing, Quality Assurance [QA] and Quality Control [QC] used interchangeably and very frequently. While it is usually enough to get your point across with a developer, it is certainly helpful to know more about how these apply to the world of software testing. So, what exactly the difference between QC and QA and how can you get from one destination to another? This presentation attempts to shed some light on this and will be taking you through various QA best practices and how we can collectively build and grow the next breed of intelligent QA Engineers
WSO2Con USA 2017: Building a Successful Delivery Team for Customer SuccessWSO2
Ensuring customer success is the the highest priority when we engage with customers. We need to strive to get the customers into production within the shortest time possible to make sure they have sustainable use of WSO2 products. The key to success is to understand the right products for the solution, define an iterative architecture, come up with an agile engagement model and define clarity in terms of scope and acceptance.
The WSO2 Delivery team is well experienced in ensuring customer success with their experiences in the support and services space. Join this session to learn how to best position WSO2 products and learn some best practices in the engagement models.
The document discusses QA best practices in an Agile development environment. It describes key aspects of Agile like iterative delivery, self-organizing teams, and rapid feedback. It addresses challenges of fitting QA into short iterations and questions around testing approaches. The document advocates for testing to be collaborative, automated, and continuous throughout development. It provides recommendations for QA roles in activities like planning, stand-ups, retrospectives and acceptance testing. Overall it promotes testing practices in Agile that focus on early feedback, automation, and involvement of QA throughout the development process.
You don’t need DTAP + Backbase implementation - Amsterdam 17-12-2015Pavel Chunyayev
DTAP is already an outdated concept in 2016. Instead an idea of immutable infrastructure should be used. Backbase in partnership with Levi9 have employed the concept of immutable infrastructure to revolutionize the way Custemer Experience Platform (CXP) is developed and released.
Optimism Webinar 2 - Moving from AB testing to true experimentationOptimizely
Start moving your experimentation program to the next level
Many organizations are already testing and experimenting on a small scale. So now the big question is: what’s stopping you from moving to the next level?
In this webinar, we’ll guide you through the framework that helps you to assess where you are on your journey – plus the four essential building blocks for success.
Building your team and making the time. Defining your strategy. Integrating the technology that unlocks benefits way beyond Google Analytics. And developing the culture of experimentation that drives innovation - and powers growth.
Discover real-world, actionable insights that allow you to successfully grow your program, deliver more value to your business and maximise ROI.
Lisa Rohlfs will be your expert guide:
- Discover a framework to evaluate your journey so far.
- Gain actionable insight to move your program to the next level.
- Create the culture of experimentation that drives innovation – and powers growth.
The document provides an overview of fundamentals of agile, including:
- Describing the waterfall process and limitations with knowledge work
- Introducing the Agile Manifesto which values individuals, working software, customer collaboration, and responding to change over processes and tools
- Outlining common agile approaches like XP, Scrum, and Kanban including roles, ceremonies, and artifacts
- Defining roles like Scrum Master, Product Owner, and cross-functional delivery teams
- Explaining the overall agile process flow including visioning, backlog organization, sprint planning, daily stand-ups, sprint reviews and retrospectives
Apqp bumming you out briefing may 30 2013John Cachat
Sales can’t update the customer on launch status. Engineering spends more time updating Gantt charts than they do actually engineering stuff. Quality can’t find the documentation. Purchasing has no idea when the supplier status is. Sound familiar?
What this means is:
• Products are late
• Quality is unacceptable
• Resources are wasted
• Problems are repeated
What we have found is that Project Management is done with the wrong tools and/or people
• Resources are over-scheduled
• Issues are not resolved
• True costs are unknown / inaccurate
What we have found with Project Management Software
• Tools are cumbersome, force detailed information that is unknown
• People resort back to XLS
• Management cannot support the team and resort to firefighting issues
Learn about an approach to APQP and a SaaS technology that allows you to implement APQP the right way and engage your people and suppliers to improve communication, and launch higher quality products faster and on-time and under budget.
The document discusses software testing documentation, including its use in agile development. It lists common types of testing documents like test plans, cases, and reports. While documentation takes time, it provides benefits like project understanding, quality feedback, and knowledge transfer. Best practices include focusing documentation on real needs, keeping it simple, generating documents programmatically where possible, and only updating when necessary rather than trying to maintain comprehensive documentation. Testing has priority over documentation in agile, but some minimal documentation is still useful for planning, specifications, and recording results.
The document discusses fundamentals of adopting a DevOps culture and practices. It emphasizes establishing a culture of collaboration, communication and shared responsibility between development and operations teams. It also stresses the importance of automating processes, embracing tools to save time but not as the primary focus, and continuously improving culture, processes and technologies over time. Mistakes to avoid include poor infrastructure setup, configuration issues, and security vulnerabilities. The document advocates starting small, measuring progress, and celebrating successes to evolve existing practices towards continuous integration, delivery and deployment.
This document discusses how the agile approach is better suited than traditional project management for "knowledge worker projects" where requirements are rapidly changing and intangible. It outlines key agile principles like valuing individuals and interactions over processes, working software over documentation, and responding to change over following a plan. The document also describes agile practices for planning value, delivering value, confirming value, and tracking/reporting value such as timeboxing, task boards, limiting work in progress, and using burn down charts.
This document provides an introduction to DevOps presented by Sri Parthasarathy from cPrime. It discusses how DevOps aims to break down silos between development and operations teams to allow for more frequent deployments through automating processes. DevOps requires both teams to work closely together across the entire development lifecycle from coding to deployment. The presentation outlines some of the technical aspects involved in DevOps including continuous integration, infrastructure as code, automated testing, and continuous delivery.
Practitest webinar - When a test manager makes a differenceDerk-Jan de Grood
Due to the adoption of Agile, the role of test manager seems redundant. Teams and individual professionals are self-managing and coordinating their own work.
Nevertheless, in some organizations and projects, there is a need for a quality ambassador that understand the agile quality strategy and can help, monitor and ensure that working solutions are delivered.
In this webinar we will explore situations in which you as a test manager can make a difference. For example:
How do we e.g. deal with compliance, integration and final acceptance in a contractor’s context?
How does a test manager coordinate the work over teams and ensures the quality of the testing itself?
Thanks Joel Montvelisky, PractiTest Chief Solution Architect, for hosting my webinar.
Digital transformation through devops dod indianapolisPeter Varhol
This document discusses how DevOps principles can enable digital transformation. Digital transformation focuses on using technology to improve customer experience and business value, while DevOps aims to streamline processes and eliminate bottlenecks. Their synergies are found in systems thinking, amplifying feedback loops, and creating a culture of continuous learning. Digital transformation can be enabled through continuous delivery by applying these synergistic focuses across the continuous delivery pipeline with continuous testing. Continuous testing ensures customer focus throughout the pipeline and manages risk, thus enabling digital transformation.
Experiment and validate business ideas - Talk outline at DevOps Showcase Amst...Pavel Chunyayev
Crucial part of any business is constantly trying to stay relevant for the customers and provide better services that competitors. It’s important to not only generate ideas on how to achieve that, but also to test and validate those ideas. DevOps mindset is indispensable to achieve good business results with software development. But how exactly?
Similar to Want Continuous Delivery? Give testing a priority! 16-6-2016, Friss, Utrecht (20)
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
Odoo ERP software
Odoo ERP software, a leading open-source software for Enterprise Resource Planning (ERP) and business management, has recently launched its latest version, Odoo 17 Community Edition. This update introduces a range of new features and enhancements designed to streamline business operations and support growth.
The Odoo Community serves as a cost-free edition within the Odoo suite of ERP systems. Tailored to accommodate the standard needs of business operations, it provides a robust platform suitable for organisations of different sizes and business sectors. Within the Odoo Community Edition, users can access a variety of essential features and services essential for managing day-to-day tasks efficiently.
This blog presents a detailed overview of the features available within the Odoo 17 Community edition, and the differences between Odoo 17 community and enterprise editions, aiming to equip you with the necessary information to make an informed decision about its suitability for your business.
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
3. @PavelChunyayev
About me
• 12 years of IT experience
• Lived and worked in Ukraine and Estonia
• Moved a year and half ago to the Netherlands
• Love cycling
• Love Dutch language
• Love software development processes
• Love working with people
5. @PavelChunyayev
Continuous Delivery
Incept
• Business idea
• Is needed
immediately
• Should be validated
Plan
• Refine
• Estimate
• Prioritize
Develop
• Put into sprint
• Develop in a branch
• Conduct a code
review
• Merge into master
Build
• Trigger pipeline
• Build
• Unit testing
• Integration testing
• Static code analysis
Test
• Contract testing
• E2E testing
• Security testing
• Resilience testing
Release
• Zero-downtime
• Canary testing
• Rolling deployment
• Blue / green
deployment
Operate
• Monitoring
• Validation of the
idea
• Money generation
• Disposal
9. @PavelChunyayev
Continuous Delivery
Incept
• Business idea
• Is needed
immediately
• Should be validated
Plan
• Refine
• Estimate
• Prioritize
Develop
• Put into sprint
• Develop in a branch
• Conduct a code
review
• Merge into master
Build
• Trigger pipeline
• Build
• Unit testing
• Integration testing
• Static code analysis
Test
• Contract testing
• E2E testing
• Security testing
• Resilience testing
Release
• Zero-downtime
• Canary testing
• Rolling deployment
• Blue / green
deployment
Operate
• Monitoring
• Validation of the
idea
• Money generation
• Disposal
36. @PavelChunyayev
Build quality in
• Testing is not just presence or absence of defects
• Testing is not a separate process
• Test should not just raise the cost of maintenance
• Stop thinking about functional testing only
• Quality goal need to be established early in the development process
• Automated testing – part of Definition of Done
• Test early, move tests to the left
• TDD
39. @PavelChunyayev
To practice
• Deploy software at the end of every iteration (done = released to
production).
• And then start doing it quicker.
• Optimize flow - don’t make ineffective more efficient.
40. @PavelChunyayev
Optimize the flow
• Honour existing processes, records,
and controls.
• They arose for a reason.
• Streamline and simplify all
processes, records, and controls.
• Challenge the level of ceremony.
42. @PavelChunyayev
Lean principles
• Optimize the whole
• Eliminate waste
• Deliver fast by managing flow
• Build quality into the system
• Create knowledge
• Defer commitment
• Respect people
44. @PavelChunyayev
“Developing people and the system
so that together they are capable of
achieving successful results is the
point.”
Mary and Tom Poppendieck
45. @PavelChunyayev
Continuous Delivery
Incept
• Business idea
• Is needed
immediately
• Should be validated
Plan
• Refine
• Estimate
• Prioritize
Develop
• Put into sprint
• Develop in a branch
• Conduct a code
review
• Merge into master
Build
• Trigger pipeline
• Build
• Unit testing
• Integration testing
• Static code analysis
Test
• Contract testing
• E2E testing
• Security testing
• Resilience testing
Release
• Zero-downtime
• Canary testing
• Rolling deployment
• Blue / green
deployment
Operate
• Monitoring
• Validation of the
idea
• Money generation
• Disposal
Keep the product releasable
Build quality in
Improve continuously
Build the right culture
pavel@levi9.com
Editor's Notes
Ideas come from all the sources.
Questions are welcome.
Disagreement is welcome, but after the talk.
Yes, but; what if.
There's always a big gap between a piece of general advice and how it applies in a particular circumstance (which is why consultants are teased for saying "it depends").
There's no way I can know all the particular issues and constraints in your project, so you have to take my half-baked comments and finish them off yourself by deciding how they apply to your circumstances.
.
.
Not every feature is needed.
Shorter and shorter release cycles =>
Release more software in less time.
TPS
Can’t churn out.
No manual testing.
.
.
.
Reproducible and repeatable process (including testing).
Potentially shippable product -> Keeping the product releasable
.
Testing criteria.
Run over and over again.
.
No DTAP.
Immutable (testing framework?)
TTL
Docker
Framework to allow restart - select arbitrary test
Building the thing right
Building the right thing
Unit + Integration – level of microservices.
.
100% coverage?
Test your unit tests.
Know exactly what is broken.
Feature toggling.
Connect units together
How parts of application work together
Feature toggling.
Mock or not to mock
Black box testing.
How service works as a whole.
Different integrations – pub/sub, request/reply.
Feature toggling.
Mock or not to mock
Proof we are still on track
Not only selenium
Focus on:
business flows
personas, user journeys
BDD + DSL?
Data independency
Feature toggling, page objects
Mock or not to mock
Communication – via contracts
* Semantic or not semantic
* API versioning - public or also internal?
* Transition between versions – testing different versions
* Running several versions together
* Semantic or not semantic
* API versioning - public or also internal?
* Transition between versioning – testing different versions
* Running several versions together
* Semantic or not semantic
* API versioning - public or also internal?
* Transition between versioning – testing different versions
* Running several versions together
* Semantic or not semantic
* API versioning - public or also internal?
* Transition between versioning – testing different versions
* Running several versions together
* Semantic or not semantic
* API versioning - public or also internal?
* Transition between versioning – testing different versions
* Running several versions together
Testing in production
Canary
Dark launch
Real users, not synthetic transactions
Security testing
Availability testing
Resilience testing
.
.
.
.
.
.
Unit + Integration – level of microservices.
Unit + Integration – inside
Contract + E2E - outside
The same testing is needed for monolith, but crucial for microservices.
Shared responsibility.
Repetition makes mastery.
Feedback from users.
Feedback to devs, to bussiness
Think of end-user throughout the whole application lifecycle.
A story isn't done until it is being used by real users in production and has been validated to be a useful part of a product.
.
In conflict on purpose.
This is reality.
Evolution, not revolution.
.
Kaizen, Japanese for "improvement."
The most important thing you can build is culture. Don’t imitate, that won’t bring the culture you want.
Stamp on problems, not on people! Solve problems, not people.