Role of QA in Continuous Delivery
•
0 likes•565 views
This document discusses the role of quality assurance (QA) in continuous delivery. It begins with an introduction of the author and then covers topics like fast-paced environments, QA as part of an organization, continuous delivery, and test automation. The main points are that QA needs to be integrated into cross-functional teams to support continuous delivery, with a focus on automating testing to validate software updates and allow for frequent deployments in a production environment. Continuous delivery aims to keep software always in a releasable state through practices like continuous integration.
Report
Share
Report
Share
Recommended
Agile Testing in Enterprise: Way to transform - SQA Days 2014
This document discusses problems that can occur with traditional testing approaches and how to transition to agile testing practices. It provides two examples of organizations that struggled with long regression cycles, missed estimates, low quality and stress. The root causes are identified as document-based collaboration, lack of testing knowledge by developers, and infrastructure management chaos. Recommendations are made to use Kanban, collaborate on requirements, implement smart metrics, test automation, and a DevOps approach. Specific practices that were implemented include risk management, specification by example, test-driven development, continuous integration, configuration automation, and test automation. The results were increased delivery rates up to 5 times, zero bugs in production, no overtime, and more enjoyable work.
One metric cycle time
This document discusses cycle time as the one key metric that software engineering teams should focus on. It defines cycle time as the time taken to deliver a standalone piece of work from coding to deployment. Measuring and focusing on reducing cycle time leads to benefits like improved team coordination, communication, predictability, and ability to incorporate feedback in shorter learning cycles. The document cites data showing that on average, engineering organizations see over 15% reduction in cycle time after the first month of measuring it, with improvements continuing in subsequent months. It emphasizes that simply measuring metrics is not enough and teams need insights into problems in order to take action and automate processes to continuously reduce cycle time.
Why we need test automation, but it’s not the right question
Why we need test automation, but it’s not the right question. A presentation of Xebia Seminar Killing the test bottleneck.
Introduction to Automated Testing
Learn about the benefits of writing unit tests. You will spend less time fixing bugs and you will get a better design for your software. Some of the questions answered are:
Why should I, as a developer, write tests?
How can I improve the software design by writing tests?
How can I save time, by spending time writing tests?
When should I write unit tests and when should I write system tests?
Continuous Deployment
- Continuous deployment involves releasing code changes to production as soon as they pass all tests, allowing for frequent, low-risk releases.
- Smartling transitioned to continuous deployment by gradually gaining team buy-in, celebrating small wins, and instituting practices like automated testing, monitoring, and single-button deployments.
- This resulted in benefits like quicker feedback, fewer bugs, easier rollbacks, and happier users and management who saw frequent new features.
Test Automation Canvas
This document discusses test automation challenges at an investment bank and lessons learned. It outlines problems with lengthy manual regression testing. An attempt was made to use Jameleon for test automation but it caused issues. They identified needs for metrics, definitions of done, and separating test connections. Recommendations include using tools like Selenium and SoapUI with a Jenkins/JIRA setup. While quick wins are possible, separating test connections and fully defining requirements are important for successful test automation.
How engineering practices help business
This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.
Agile vs. waterfall - The fundamentals differences
In this presentation I will review the main differences between waterfall and agile methodology, this presentation is a great place to start if you want to know why more and more companies are using agile as the preferred development methodology.
Recommended
Agile Testing in Enterprise: Way to transform - SQA Days 2014
This document discusses problems that can occur with traditional testing approaches and how to transition to agile testing practices. It provides two examples of organizations that struggled with long regression cycles, missed estimates, low quality and stress. The root causes are identified as document-based collaboration, lack of testing knowledge by developers, and infrastructure management chaos. Recommendations are made to use Kanban, collaborate on requirements, implement smart metrics, test automation, and a DevOps approach. Specific practices that were implemented include risk management, specification by example, test-driven development, continuous integration, configuration automation, and test automation. The results were increased delivery rates up to 5 times, zero bugs in production, no overtime, and more enjoyable work.
One metric cycle time
This document discusses cycle time as the one key metric that software engineering teams should focus on. It defines cycle time as the time taken to deliver a standalone piece of work from coding to deployment. Measuring and focusing on reducing cycle time leads to benefits like improved team coordination, communication, predictability, and ability to incorporate feedback in shorter learning cycles. The document cites data showing that on average, engineering organizations see over 15% reduction in cycle time after the first month of measuring it, with improvements continuing in subsequent months. It emphasizes that simply measuring metrics is not enough and teams need insights into problems in order to take action and automate processes to continuously reduce cycle time.
Why we need test automation, but it’s not the right question
Why we need test automation, but it’s not the right question. A presentation of Xebia Seminar Killing the test bottleneck.
Introduction to Automated Testing
Learn about the benefits of writing unit tests. You will spend less time fixing bugs and you will get a better design for your software. Some of the questions answered are:
Why should I, as a developer, write tests?
How can I improve the software design by writing tests?
How can I save time, by spending time writing tests?
When should I write unit tests and when should I write system tests?
Continuous Deployment
- Continuous deployment involves releasing code changes to production as soon as they pass all tests, allowing for frequent, low-risk releases.
- Smartling transitioned to continuous deployment by gradually gaining team buy-in, celebrating small wins, and instituting practices like automated testing, monitoring, and single-button deployments.
- This resulted in benefits like quicker feedback, fewer bugs, easier rollbacks, and happier users and management who saw frequent new features.
Test Automation Canvas
This document discusses test automation challenges at an investment bank and lessons learned. It outlines problems with lengthy manual regression testing. An attempt was made to use Jameleon for test automation but it caused issues. They identified needs for metrics, definitions of done, and separating test connections. Recommendations include using tools like Selenium and SoapUI with a Jenkins/JIRA setup. While quick wins are possible, separating test connections and fully defining requirements are important for successful test automation.
How engineering practices help business
This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.
Agile vs. waterfall - The fundamentals differences
In this presentation I will review the main differences between waterfall and agile methodology, this presentation is a great place to start if you want to know why more and more companies are using agile as the preferred development methodology.
Agile scrum roles
The document discusses the roles in Scrum, an agile software development methodology. It describes the three main roles: the Scrum Team which develops the software; the Product Owner who prioritizes features and represents customers; and the Scrum Master who leads the team and ensures they follow Scrum practices. The roles work together iteratively with the Scrum Team delivering working software increments each sprint while the Product Owner and Scrum Master provide feedback and guidance.
Spec By Example or How to teach people talk to each other
This document introduces an approach called "Spec By Example" to improve communication between developers, QA analysts, and clients. It involves impact mapping to focus on user stories, QA and analyst pairing to create examples to describe requirements, and diverse and merge sessions for the team to collaboratively build out examples. The examples are then optimized by compressing tables and introducing parameters before being linked to automated tests through a behavior driven development approach. This unified process allows requirements, test cases, and code to have a single source of truth, makes it easy to trace work back to business needs, and improves estimation, demos, and reduces rework and issues.
Security Implications for a DevOps Transformation
If your organization is undergoing a DevOps transformation, you’re probably thinking about where security fits in. All too often, we tack on security testing at the end of the delivery process, which means significant problems go undetected until development is complete. As we adopt DevOps principles and practices, we enable a natural solution to this problem: ensure that security experts are involved throughout the delivery process.
In this webinar, DevOps.com and Puppet defined a reference implementation of DevOps from the ground up, by illustrating how the software delivery process evolves at a hypothetical startup. Once we've laid a technical foundation for DevOps, we discussed the implications for security. We also discussed:
Benefits for and challenges to security during a DevOps transformation
How to craft a DevOps-ready security practice
Refinements of a standard DevOps workflow to address security needs
Continuous Testing in DevOps
This document provides an overview of continuous testing in DevOps presented by Michael Hackett of LogiGear Corporation. It discusses what DevOps is and how testing fits into the continuous delivery pipeline. It emphasizes the need for testing at every step of development and deployment through test automation. It also provides examples of challenges companies face in implementing continuous testing and DevOps practices.
Efficient or Just Busy?
The document discusses the benefits of using work-in-progress (WIP) limits to manage software projects more efficiently. It notes that while 100% utilization seems ideal, it actually leads to lower quality and longer cycle times due to multitasking. Introducing moderate WIP limits of around 2x the average WIP has been shown to significantly improve average cycle times by around 60% while only increasing costs marginally. The slack time created allows for continuous improvement, automation, higher quality code, and helps the team self-balance. Ultimately, utilizing WIP limits results in more efficient work compared to constantly keeping teams at 100% utilization.
SplunkLive! - Want to Turbocharge your Developer Pipeline?
1) Splunk can help optimize developer build times by collecting metrics on the build process and visualizing them in dashboards.
2) The document discusses how Atlassian used Splunk to analyze build metrics after their codebase and number of modules grew substantially, leading to inefficient builds and long build times.
3) By collecting Maven build metrics in Splunk and creating visualizations like timelines and dependency graphs, Atlassian was able to identify inefficiencies, reduce unnecessary dependencies, parallelize tasks, and ultimately decrease overall build time from 10:40 to 6:30.
Invite the tester to the party
This slide deck was used at the Global Scrum Gathering in Prague in 2015. The deck provides inspiration on:
* How to make the tester part of the Development Team
* How to eliminate the need for "Quality Control"
* Foster collaboration within the team.
Consuming DevOps: How Upstream DevOps Initiatives Disrupted our Downstream Co...
The DevOps transformation is a cultural movement spreading rapidly across most companies and industries. As Dev teams race to adopt new strategies to build and release software faster, often extended and peripheral teams scramble to keep up.
Join Bryan Cole, ADM practice manager at Micro Focus, in this webinar to discuss how the rapid delivery cadence adopted by the software delivery teams impacted their downstream consumers and what happened as a result of that.
At Micro Focus, our own DevOps transformation completely disrupted our presales, technical enablement and marketing organizations, forcing each to adapt and implement a DevOps transformation of their own in order to maintain coordination and alignment with R&D teams.
In this session, we will talk about:
What happened to our organization internally
What events forced changes in how we operate
How we continue to evolve our own DevOps transformation practices to keep up with the R&D organization.
Testing In Production (TiP) Advances with Big Data & the Cloud
Testing in Production (TiP) has moved from taboo to accepted practice owing to its ability to measure reality and provide actionable feedback. These risks can be mitigated by using proven methodologies, methodologies borne of experience and tools built specifically to handle TiP’s unique requirements.
Big Data enables TIP by analyzing user behavior then creating realistic tests. During testing, cloud-based resources are used for the huge data volumes and processed within-memory technology specifically designed for this process
Microsoft’s Seth Eliot is a TiP pioneer and SOASTA’s Rob Holcomb has helped evolve the practice with hundreds of SOASTA customers. Catch this webinar, now on-demand, as they dig into:
How to leverage both active and passive monitoring for TiP
Testing and measuring system stress in production
Experimentation and iterative improvement
How SOASTA CloudTest facilitates TiP for organizations of all sizes
Using Error Budgets to Prioritize Work
Site Reliability Engineering (SRE) is a set of principles, practices, and organizational constructs that seek to balance the reliability of a service with the need to continually deliver new features. An error budget is the primary construct used to help balance these seemingly competing goals.
This is an introduction to error budgets and their components: service level indicators (SLIs) and service level objectives (SLOs). We will discuss the art of creating and implementing SLOs.
Attendees will be able to:
• Describe the key concepts, namely, Error Budget, Service Level Indicator (SLIs), and Service Level Objectives (SLOs)
• Recommend actions to take when the error budget is over consumed
• Recommend actions to take when excess error budget remains
In the spirit of DevOps, Error Budgets and SLOs work best when they are agreed to in collaboration with many different constituents across the business. As such, this presentation is appropriate for:
• Product Owners and Product Managers
• Business decision makers
• Developers
• Operators
• And anyone else interested in building and operating services that deliver business and customer value.
The evolution of agile development process
The Evolution of Agile Development Process
The main sections of this presentation
1. Overview
2. The Waterfall Model as a baseline
3. Waterfall Model – Phases of the process
4. The problem in traditional models
5. Agile Software Development as the Alternative
6. The Agile Manifesto – The Beginning
7. The Manifesto for Agile Software Development
8. The benefits of the agile methodology
Beyond WIP Limits (Lean Kanban Tour Edition)
- Implementing work-in-progress (WIP) limits results in improved efficiency and productivity over allowing unlimited WIP, with average cycle times improving by 28-59% and predictability increasing by 65-89%.
- The slack time introduced by WIP limits drives continuous improvement efforts and allows teams to help each other, learn, and make system improvements.
- While WIP limits can result in a small 1% increase in the cost of blocked or idle work, they provide significant value by reducing cycle times and improving predictability.
Continuous delivery
This document discusses the principles and benefits of continuous delivery. It emphasizes delivering valuable software to users as quickly as possible through early and continuous delivery. It recommends automating the software delivery process through practices like continuous integration, deployment pipelines, and feature flags to reduce risk and enable reliable, repeatable releases. Frequent integration and deployment allows for real project progress updates and quick recovery from any issues.
Chad Vossen - We shall produce working software
- The document describes Chad Vossen's experience with traditional waterfall projects and an agile approach called "flash builds".
- A waterfall project to modernize 28 C++ programs took 20,000 hours over 2.5 years with a 11% success rate, while flash builds completed similar work in 136 hours with a 39% success rate.
- The flash build approach focuses on working software over documentation, uses collaboration rooms and task boards, and allows for daily retrospectives and feedback to iteratively improve. The second flash build completed 44 points in 2 days compared to 25 points in the first attempt.
Feedback Loops in Agile Development
Agile development relies on feedback loops to continuously improve the development process. Short iterations and frequent delivery of working software allows customers to provide early and regular feedback to identify issues and ensure the project stays aligned with their needs. Feedback also comes from testing and following principles like rapid feedback and short releases where developers seek feedback quickly after each change and deliver new versions frequently to speed up the feedback cycle. The goal is to detect and address problems as early as possible through an empirical process of making changes, learning from the results, and evolving the process.
Intro to DevOps 4 undergraduates
Help students get familiar with the basic concepts of DevOps processes and technologies and the challenges facing companies who are looking to embrace scalable software deployment.
[This workshop was given to TAU CS students over the years 2015-2016]
Supervisor 8.13 New Release Webinar
This document outlines the new features in Supervisor 8.13 including conditional simulation, QQ plots, optimum digline analysis, GT curve analysis, and probability plots. It also summarizes previously released features in versions 8.11 and 8.12. Planned future releases are mentioned, including multivariate simulation in version 8.14. The webinar agenda includes explanations of the new features, design principles, and how to provide feedback or get involved in the pre-release program. Users are encouraged to download the latest version, watch feature demo videos, and share feedback to help improve the software.
The 5 Laws of Software Estimates
Презентация подготовлена по материалам выступления Анатолия Таразевича на витебском Miniq #27, который был проведен 30 июля 2020:
https://community-z.com/events/miniq-vitebsk-27
Про доклад:
Оценки, как правило, являются необходимым злом в разработке программного обеспечения. К сожалению, люди склонны считать, что написание нового программного обеспечения - это все равно что строить дом или ремонтировать автомобиль, и что подрядчик или участвующий в нем механик должны быть в состоянии обеспечить надежную и точную оценку обьема работы и сроков её выполнения. Но это не всегда так и для того чтобы этого достичь понимания в этом вопросе - важно чтобы все люди участвующие в процессе разработки, будь то разработчик или бизнесс-аналитик, понимали главные особенности и законы эстимаций об этом мы и поговорим.
[QE 2015] Michał Kordas - Agile testing: Optimizing the feedback loops
W ostatnich latach nauczyliśmy się, że krótkie pętle sprzężenia zwrotnego, czyli tzw. short feedback loops, mają ogromne znaczenie i są jednym z najważniejszych elementów metodyki agile. Właśnie dlatego zabiorę nas na „wycieczkę” po różnych pętlach, z którymi miałem styczność pracując przy swoich projektach.
Zaczniemy od naiwnego podejścia „test-after”, następnie przejdziemy do „test-first”, TDD, projektowania ewolucyjnego, minimalnej analizy, 3 Agile Amigos, podejścia biznesowego. Na koniec poznamy rozwiązania oparte na technice „outside-in” BDD.
Agile + Benefits + Transition Nov 2009
The document discusses agile as an active risk management strategy for software development projects. It notes that agile approaches can help reduce costs, delay, and increase benefits and value. The document also provides evidence that agile methods have benefits like increased productivity, quality and stakeholder satisfaction. It discusses how many large companies and government organizations like the DoD have adopted agile. Finally, it outlines a suggested agile transition approach using coaches over several phases.
Live predictions with schemaless data at scale. MLMU Kosice, Exponea
Imagine you have huge amounts of data about your customers. All this data is schemaless and represents everything a customer is doing in your e-shop. From page visits and banner showings to purchases or registrations. Having all this data is a data scientists wet dream but also a nightmare at the same time. The data is schemaless and every project you track can send you different attributes and event types. Now, here comes the hard work. Create some universal data preprocessing engine which can turn all of this data into something that is reasonable and useful for machine learning algorithms for any project you have.
We will show you, how this is done at Exponea and much more. How to connect this data to Spark ML library and then translate the model into a sequence of mathematical functions and aggregation methods for our in memory database to evaluate it on all customers in real time.Ondrej Brichta – currently working at Exponea as AI Engineer. Studying Logic and computability at Vienna University of Technology, alumni of Nexteria Leadership Academy and Matfyz in Bratislava
Google Summer of Code 2017: Experience at Discourse
Sharing lessons learned and inspiration for computer science students about open source and Google Summer of Code programme. Presented during PeWe Ontoparty at Slovak University of Technology. https://www.pewe.sk/autumn-201718-november-10-2017/
More Related Content
What's hot
Agile scrum roles
The document discusses the roles in Scrum, an agile software development methodology. It describes the three main roles: the Scrum Team which develops the software; the Product Owner who prioritizes features and represents customers; and the Scrum Master who leads the team and ensures they follow Scrum practices. The roles work together iteratively with the Scrum Team delivering working software increments each sprint while the Product Owner and Scrum Master provide feedback and guidance.
Spec By Example or How to teach people talk to each other
This document introduces an approach called "Spec By Example" to improve communication between developers, QA analysts, and clients. It involves impact mapping to focus on user stories, QA and analyst pairing to create examples to describe requirements, and diverse and merge sessions for the team to collaboratively build out examples. The examples are then optimized by compressing tables and introducing parameters before being linked to automated tests through a behavior driven development approach. This unified process allows requirements, test cases, and code to have a single source of truth, makes it easy to trace work back to business needs, and improves estimation, demos, and reduces rework and issues.
Security Implications for a DevOps Transformation
If your organization is undergoing a DevOps transformation, you’re probably thinking about where security fits in. All too often, we tack on security testing at the end of the delivery process, which means significant problems go undetected until development is complete. As we adopt DevOps principles and practices, we enable a natural solution to this problem: ensure that security experts are involved throughout the delivery process.
In this webinar, DevOps.com and Puppet defined a reference implementation of DevOps from the ground up, by illustrating how the software delivery process evolves at a hypothetical startup. Once we've laid a technical foundation for DevOps, we discussed the implications for security. We also discussed:
Benefits for and challenges to security during a DevOps transformation
How to craft a DevOps-ready security practice
Refinements of a standard DevOps workflow to address security needs
Continuous Testing in DevOps
This document provides an overview of continuous testing in DevOps presented by Michael Hackett of LogiGear Corporation. It discusses what DevOps is and how testing fits into the continuous delivery pipeline. It emphasizes the need for testing at every step of development and deployment through test automation. It also provides examples of challenges companies face in implementing continuous testing and DevOps practices.
Efficient or Just Busy?
The document discusses the benefits of using work-in-progress (WIP) limits to manage software projects more efficiently. It notes that while 100% utilization seems ideal, it actually leads to lower quality and longer cycle times due to multitasking. Introducing moderate WIP limits of around 2x the average WIP has been shown to significantly improve average cycle times by around 60% while only increasing costs marginally. The slack time created allows for continuous improvement, automation, higher quality code, and helps the team self-balance. Ultimately, utilizing WIP limits results in more efficient work compared to constantly keeping teams at 100% utilization.
SplunkLive! - Want to Turbocharge your Developer Pipeline?
1) Splunk can help optimize developer build times by collecting metrics on the build process and visualizing them in dashboards.
2) The document discusses how Atlassian used Splunk to analyze build metrics after their codebase and number of modules grew substantially, leading to inefficient builds and long build times.
3) By collecting Maven build metrics in Splunk and creating visualizations like timelines and dependency graphs, Atlassian was able to identify inefficiencies, reduce unnecessary dependencies, parallelize tasks, and ultimately decrease overall build time from 10:40 to 6:30.
Invite the tester to the party
This slide deck was used at the Global Scrum Gathering in Prague in 2015. The deck provides inspiration on:
* How to make the tester part of the Development Team
* How to eliminate the need for "Quality Control"
* Foster collaboration within the team.
Consuming DevOps: How Upstream DevOps Initiatives Disrupted our Downstream Co...
The DevOps transformation is a cultural movement spreading rapidly across most companies and industries. As Dev teams race to adopt new strategies to build and release software faster, often extended and peripheral teams scramble to keep up.
Join Bryan Cole, ADM practice manager at Micro Focus, in this webinar to discuss how the rapid delivery cadence adopted by the software delivery teams impacted their downstream consumers and what happened as a result of that.
At Micro Focus, our own DevOps transformation completely disrupted our presales, technical enablement and marketing organizations, forcing each to adapt and implement a DevOps transformation of their own in order to maintain coordination and alignment with R&D teams.
In this session, we will talk about:
What happened to our organization internally
What events forced changes in how we operate
How we continue to evolve our own DevOps transformation practices to keep up with the R&D organization.
Testing In Production (TiP) Advances with Big Data & the Cloud
Testing in Production (TiP) has moved from taboo to accepted practice owing to its ability to measure reality and provide actionable feedback. These risks can be mitigated by using proven methodologies, methodologies borne of experience and tools built specifically to handle TiP’s unique requirements.
Big Data enables TIP by analyzing user behavior then creating realistic tests. During testing, cloud-based resources are used for the huge data volumes and processed within-memory technology specifically designed for this process
Microsoft’s Seth Eliot is a TiP pioneer and SOASTA’s Rob Holcomb has helped evolve the practice with hundreds of SOASTA customers. Catch this webinar, now on-demand, as they dig into:
How to leverage both active and passive monitoring for TiP
Testing and measuring system stress in production
Experimentation and iterative improvement
How SOASTA CloudTest facilitates TiP for organizations of all sizes
Using Error Budgets to Prioritize Work
Site Reliability Engineering (SRE) is a set of principles, practices, and organizational constructs that seek to balance the reliability of a service with the need to continually deliver new features. An error budget is the primary construct used to help balance these seemingly competing goals.
This is an introduction to error budgets and their components: service level indicators (SLIs) and service level objectives (SLOs). We will discuss the art of creating and implementing SLOs.
Attendees will be able to:
• Describe the key concepts, namely, Error Budget, Service Level Indicator (SLIs), and Service Level Objectives (SLOs)
• Recommend actions to take when the error budget is over consumed
• Recommend actions to take when excess error budget remains
In the spirit of DevOps, Error Budgets and SLOs work best when they are agreed to in collaboration with many different constituents across the business. As such, this presentation is appropriate for:
• Product Owners and Product Managers
• Business decision makers
• Developers
• Operators
• And anyone else interested in building and operating services that deliver business and customer value.
The evolution of agile development process
The Evolution of Agile Development Process
The main sections of this presentation
1. Overview
2. The Waterfall Model as a baseline
3. Waterfall Model – Phases of the process
4. The problem in traditional models
5. Agile Software Development as the Alternative
6. The Agile Manifesto – The Beginning
7. The Manifesto for Agile Software Development
8. The benefits of the agile methodology
Beyond WIP Limits (Lean Kanban Tour Edition)
- Implementing work-in-progress (WIP) limits results in improved efficiency and productivity over allowing unlimited WIP, with average cycle times improving by 28-59% and predictability increasing by 65-89%.
- The slack time introduced by WIP limits drives continuous improvement efforts and allows teams to help each other, learn, and make system improvements.
- While WIP limits can result in a small 1% increase in the cost of blocked or idle work, they provide significant value by reducing cycle times and improving predictability.
Continuous delivery
This document discusses the principles and benefits of continuous delivery. It emphasizes delivering valuable software to users as quickly as possible through early and continuous delivery. It recommends automating the software delivery process through practices like continuous integration, deployment pipelines, and feature flags to reduce risk and enable reliable, repeatable releases. Frequent integration and deployment allows for real project progress updates and quick recovery from any issues.
Chad Vossen - We shall produce working software
- The document describes Chad Vossen's experience with traditional waterfall projects and an agile approach called "flash builds".
- A waterfall project to modernize 28 C++ programs took 20,000 hours over 2.5 years with a 11% success rate, while flash builds completed similar work in 136 hours with a 39% success rate.
- The flash build approach focuses on working software over documentation, uses collaboration rooms and task boards, and allows for daily retrospectives and feedback to iteratively improve. The second flash build completed 44 points in 2 days compared to 25 points in the first attempt.
Feedback Loops in Agile Development
Agile development relies on feedback loops to continuously improve the development process. Short iterations and frequent delivery of working software allows customers to provide early and regular feedback to identify issues and ensure the project stays aligned with their needs. Feedback also comes from testing and following principles like rapid feedback and short releases where developers seek feedback quickly after each change and deliver new versions frequently to speed up the feedback cycle. The goal is to detect and address problems as early as possible through an empirical process of making changes, learning from the results, and evolving the process.
Intro to DevOps 4 undergraduates
Help students get familiar with the basic concepts of DevOps processes and technologies and the challenges facing companies who are looking to embrace scalable software deployment.
[This workshop was given to TAU CS students over the years 2015-2016]
Supervisor 8.13 New Release Webinar
This document outlines the new features in Supervisor 8.13 including conditional simulation, QQ plots, optimum digline analysis, GT curve analysis, and probability plots. It also summarizes previously released features in versions 8.11 and 8.12. Planned future releases are mentioned, including multivariate simulation in version 8.14. The webinar agenda includes explanations of the new features, design principles, and how to provide feedback or get involved in the pre-release program. Users are encouraged to download the latest version, watch feature demo videos, and share feedback to help improve the software.
The 5 Laws of Software Estimates
Презентация подготовлена по материалам выступления Анатолия Таразевича на витебском Miniq #27, который был проведен 30 июля 2020:
https://community-z.com/events/miniq-vitebsk-27
Про доклад:
Оценки, как правило, являются необходимым злом в разработке программного обеспечения. К сожалению, люди склонны считать, что написание нового программного обеспечения - это все равно что строить дом или ремонтировать автомобиль, и что подрядчик или участвующий в нем механик должны быть в состоянии обеспечить надежную и точную оценку обьема работы и сроков её выполнения. Но это не всегда так и для того чтобы этого достичь понимания в этом вопросе - важно чтобы все люди участвующие в процессе разработки, будь то разработчик или бизнесс-аналитик, понимали главные особенности и законы эстимаций об этом мы и поговорим.
[QE 2015] Michał Kordas - Agile testing: Optimizing the feedback loops
W ostatnich latach nauczyliśmy się, że krótkie pętle sprzężenia zwrotnego, czyli tzw. short feedback loops, mają ogromne znaczenie i są jednym z najważniejszych elementów metodyki agile. Właśnie dlatego zabiorę nas na „wycieczkę” po różnych pętlach, z którymi miałem styczność pracując przy swoich projektach.
Zaczniemy od naiwnego podejścia „test-after”, następnie przejdziemy do „test-first”, TDD, projektowania ewolucyjnego, minimalnej analizy, 3 Agile Amigos, podejścia biznesowego. Na koniec poznamy rozwiązania oparte na technice „outside-in” BDD.
Agile + Benefits + Transition Nov 2009
The document discusses agile as an active risk management strategy for software development projects. It notes that agile approaches can help reduce costs, delay, and increase benefits and value. The document also provides evidence that agile methods have benefits like increased productivity, quality and stakeholder satisfaction. It discusses how many large companies and government organizations like the DoD have adopted agile. Finally, it outlines a suggested agile transition approach using coaches over several phases.
What's hot (20)
Spec By Example or How to teach people talk to each other
Spec By Example or How to teach people talk to each other
SplunkLive! - Want to Turbocharge your Developer Pipeline?
SplunkLive! - Want to Turbocharge your Developer Pipeline?
Consuming DevOps: How Upstream DevOps Initiatives Disrupted our Downstream Co...
Consuming DevOps: How Upstream DevOps Initiatives Disrupted our Downstream Co...
Testing In Production (TiP) Advances with Big Data & the Cloud
Testing In Production (TiP) Advances with Big Data & the Cloud
[QE 2015] Michał Kordas - Agile testing: Optimizing the feedback loops
[QE 2015] Michał Kordas - Agile testing: Optimizing the feedback loops
Viewers also liked
Live predictions with schemaless data at scale. MLMU Kosice, Exponea
Imagine you have huge amounts of data about your customers. All this data is schemaless and represents everything a customer is doing in your e-shop. From page visits and banner showings to purchases or registrations. Having all this data is a data scientists wet dream but also a nightmare at the same time. The data is schemaless and every project you track can send you different attributes and event types. Now, here comes the hard work. Create some universal data preprocessing engine which can turn all of this data into something that is reasonable and useful for machine learning algorithms for any project you have.
We will show you, how this is done at Exponea and much more. How to connect this data to Spark ML library and then translate the model into a sequence of mathematical functions and aggregation methods for our in memory database to evaluate it on all customers in real time.Ondrej Brichta – currently working at Exponea as AI Engineer. Studying Logic and computability at Vienna University of Technology, alumni of Nexteria Leadership Academy and Matfyz in Bratislava
Google Summer of Code 2017: Experience at Discourse
Sharing lessons learned and inspiration for computer science students about open source and Google Summer of Code programme. Presented during PeWe Ontoparty at Slovak University of Technology. https://www.pewe.sk/autumn-201718-november-10-2017/
Educational Question Routing in Online Student Communities
1. The document presents an educational question routing framework for online student communities that recommends questions to users suitable to answer them based on their expertise, willingness, and workload.
2. An experiment applying this framework to a quantum cryptography MOOC with over 4,600 students showed it increased accurate recommendations, community participation in answering questions, and average user contributions compared to a baseline method.
3. The framework incorporated additional data from the MOOC beyond community question answering activity and its effectiveness was demonstrated in a real online experiment over 7 weeks with the MOOC students.
Orgb Team Charter[1]
The team charter outlines the team's mission, goals, upcoming projects, roles and responsibilities. The team's mission is to provide a professional work environment that encourages creativity, teamwork and enthusiasm. Their goal is to achieve an average grade of 85% by exemplifying strong communication and high quality work. The charter then lists the team's projects for their courses, desired outcomes, stakeholders and evaluation criteria. It also establishes processes for communication, expectations, decision making and conflict resolution.
Project charter sample
This document is a project charter template for a project. It includes sections for the project description, objectives, scope, assumptions, approach, team structure, communication plan, risk mitigation plan, change control plan, and appendices for additional review processes. The project description should be 1-2 concise sentences explaining what the project will accomplish and for whom. The objectives, scope, and assumptions help define the goals, deliverables, and presumptions of the project. The approach outlines the planned methodology and timeline. The team structure identifies roles and responsibilities. The communication plan establishes regular check-ins. The risk plan evaluates potential issues.
Quality Assurance
Using experienced QA resources improves workflow and efficiency, enabling a company to be more competitive in the market. Charter Global has a strong technical understanding of the resources needed to maintain an effective QA organization.
GoodData: The DevOps Story @ FIT CVUT October 16 2013
Presentation was a part of FIT CVUT / MI-AIT (Případové studie aplikace a řízení IT).
We compare the traditional organization model of separate teams for engineering, QA and operations to the DevOps model using autonomous cross-functional teams. The presentation uses GoodData as a case study.
[Srijan Wednesday Webinars] Building a High Performance QA Team
Speaker: Karim Fanadka, HPE Software
Session Slides: http://www.srijan.net/webinar/building-high-performance-qa-team/
Karim is a DevTest manager at HPE Software and his team is responsible for testing their new SaaS product, the StormRunner Load. In this webinar, Karim shares his experience of building a QA team that is agile, efficient, and uses the latest testing frameworks. He will also talk about continuous testing, automation, test based analytics and hotfixes.
Karim start's off the challenges in agile QA and then moves on to solving these challenges. The best part is when he shares the trick to delivering to production every 1.5 months, even for a high pressure enterprise product.
The Q/A session also brings out some very interesting topics, going into greater details and various suggestions that you can implement for your own QA teams.
Qa exploratory test charter template
The document provides a template for an exploratory test charter. The charter includes sections for introduction, context, execution, and reporting. The context section describes the test environment, coverage area, and tasks. The execution section is for documenting testing notes, output files, issues, and bugs found. The reporting section summarizes the time spent on design, execution, issue investigation, and other phases of the exploratory test.
Roles responsabilities-jc
The document outlines various roles involved in a project and provides a brief description for each. It includes roles such as Creative Director, Strategist, Art Director, Information Architect, Producer, Solutions Architect, Designer, Copywriter, and both front-end and back-end developers along with lead and assistant variations. Each role is assigned a nickname like "The Conductor", "The Aligner", and "The Builder" to further describe their responsibilities in driving the creative vision, ensuring alignment between objectives and needs, and leading development respectively.
The Project Charter Ensuring Quality
How the project Charter is the most important document to any Project manager. This presentation will guide you through the necessary sections and items to include in any Project Charter in order to be a powerful "one step / One site" tool for the entire project Team to use as reference to confirm on what project areas to accomplish or operate was agreed upon as a team - so there will not be any confusion or vagueness.
Why Everyone Needs DevOps Now: 15 Year Study Of High Performing Technology Orgs
This presentation describes my interpretation of the Why and How of DevOps, and the key findings from my 15 year study of high-performing IT organizations, and how they simultaneously deliver stellar service levels and rapid implementation of new features into the production environment.
Organizations employing DevOps practices such as Google, Amazon, Facebook, Etsy and Twitter are routinely deploying code into production hundreds, or even thousands, of times per day, while providing world-class availability, reliability and security. In contrast, most organizations struggle to do releases more every nine months.
He will present how these high-performing organizations achieve this fast flow of work through Product Management and Development, through QA and Infosec, and into IT Operations. By doing so, other organizations can now replicate the extraordinary culture and outcomes enabling their organization to win in the marketplace.
The Groop Project Checklist
The document outlines the three phases of the Groop System Foundation: inception, execution, and launch. In the inception phase, challenges included not having a clear focus, brainstorming separately, and not understanding users. Tools like workshops helped define purpose, priorities, and user needs. In execution, building the system faced challenges like different languages/interests and lack of consensus, while tools like planning kits helped with motivation, clarity, and user stories. Launch challenges were lack of testing/feedback plans, with tools like testing kits building confidence and adoption but still needing more learning.
My Personal CORE Strategy: Brand, Customers, Goals
FREE Webinar Thursday, May 22nd 5:30 PM
fb.me/6Enzgvd23
The Skool OS CORE is a strategic planning framework that helps you define your brand, define your customers and prioritize your goals. As an experiment I used it on myself. Can the CORE Strategic framework be used for a person?
The Prime Directive. How To Charter Your Team Best (With LEGO Serious Play)
Team chartering is generally used at the start of a project only, and team charters tend to be quite general and abstract.
In this hands-on session of Agile Cambridge Conference 2015, we will use the 'Lego Serious Play' method to develop a team-specific team charter, which fits individual team goals and can be adapted continuously.
Project Metrics & Measures
The document outlines a roadmap for defining project metrics and measures to track project success. It discusses establishing governance and scope, identifying key metrics, collecting baseline data, setting benchmarks and targets, reporting processes, implementation, and review. Metrics should be clearly defined, agreed upon, and tied to business goals to provide a common understanding of project status and performance.
Developing Metrics and KPI (Key Performance Indicators
Get a FREE performance management kit and access to all of Victor's full videos at:
www.lifecycle-performance-pros.com
This presentation covers the basics of developing successful performance metrics, from developing winning KPIs, learning how to develop the right metrics, the rules of developing KPIs and metrics and common performance metrics for managing a successful organization.
Viewers also liked (17)
Live predictions with schemaless data at scale. MLMU Kosice, Exponea
Live predictions with schemaless data at scale. MLMU Kosice, Exponea
Google Summer of Code 2017: Experience at Discourse
Google Summer of Code 2017: Experience at Discourse
Educational Question Routing in Online Student Communities
Educational Question Routing in Online Student Communities
GoodData: The DevOps Story @ FIT CVUT October 16 2013
GoodData: The DevOps Story @ FIT CVUT October 16 2013
[Srijan Wednesday Webinars] Building a High Performance QA Team
[Srijan Wednesday Webinars] Building a High Performance QA Team
Why Everyone Needs DevOps Now: 15 Year Study Of High Performing Technology Orgs
Why Everyone Needs DevOps Now: 15 Year Study Of High Performing Technology Orgs
My Personal CORE Strategy: Brand, Customers, Goals
My Personal CORE Strategy: Brand, Customers, Goals
The Prime Directive. How To Charter Your Team Best (With LEGO Serious Play)
The Prime Directive. How To Charter Your Team Best (With LEGO Serious Play)
Developing Metrics and KPI (Key Performance Indicators
Developing Metrics and KPI (Key Performance Indicators
Similar to Role of QA in Continuous Delivery
DevOps overview 2019-04-13 Nelkinda April Meetup
This document provides an overview of DevOps, including:
- Defining DevOps as unifying software development and operations through automation and monitoring.
- Tracing the history from waterfall to agile/DevOps approaches.
- Describing the DevOps lifecycle including continuous development, testing, integration, delivery, and monitoring.
- Explaining concepts like continuous integration, continuous delivery, and emphasizing culture changes like collaboration over silos.
DevOps Indonesia #2 - Toolchain & Technology
This document discusses DevOps tools and practices. It covers DevOps toolchains, building deployment pipelines gradually through automation, and the importance of knowledge over tools. Continuous integration, continuous delivery, and deploying changes frequently are emphasized. Visualizing processes, integrating changes daily, keeping builds fast and tests automated, and deploying to production-like environments are presented as core DevOps practices.
DevOps Indonesia - DevOps Toolchain and Technology
We are discussing about DevOps Toolchain and Technology in this DevOps Indonesia meetup. Come and Join us for next meetup session.
How to win at DevOps (and understand it along the way)
Learn the basics of DevOps, continuous integration, continuous delivery and the tools that you’ll need to successfully implement DevOps at your organization.
Release Engineering Downstream of an OpenStack Project
Presentation given at OSCON 2015 Open Cloud Day on 7/21/2015
For open source projects such as OpenStack, being able to effectively build, release, and deploy upstream code into a production environment is as much art as science. Using the experience gained from more than three years in OpenStack operations, we will share best practices and tools to create a sustainable and repeatable release engineering process for your own open source development needs.
http://www.oscon.com/open-source-2015/public/schedule/detail/44790
Release Automation: Better Quality, Faster Deployment, Amazing ROI
A great deal of confusion surrounds the concepts of release automation, continuous integration, continuous delivery, and continuous deployment. Even some industry experts are confused about the differences. How these concepts work progressively to achieve high quality software delivery is generating a lot of discussion and controversy. Bryan Linder defines the methodology, processes, and tools associated with release automation, as well as the differences between its maturity levels. Understand the benefits of more frequent, smaller releases, and the exponential risk generated by large, infrequent releases. Hear highlights of industry case studies that demonstrate the substantial speed, quality, and ROI gains of improving your release automation process. Acquire the insight and motivation needed to take the next step—from wherever you organization is now—toward full release automation. Takeaways include a glossary of terms, a continuous integration tools comparison chart, and a release automation maturity chart.
Павел Чуняев - State of Continuous Delivery in 2015
Павел Чуняев - State of Continuous Delivery in 2015
#itspringby
https://www.youtube.com/watch?v=Q2XD9HnSzhk
State of continuous delivery in 2015 - Minsk 15-5-2015
The presentation gives high-level overview of most important aspects of implementing Continuous Delivery comparing CD with Agile, DevOps and Lean software development.
Continuous Delivery: The New Normal. London Event.
This document summarizes the key findings of a survey on continuous delivery practices. The survey found that 65% of software professionals report their organizations have started implementing continuous delivery, up from 28% in previous years. Continuous delivery is becoming more common for both SaaS and non-SaaS companies due to factors like faster time to market and competitive advantage. However, challenges remain around integrating technologies and gaining the necessary skills.
Scaling continuous delivery @ GeeCon 2014
Tomas Riha discusses the challenges of scaling continuous delivery. Initially, their process worked well with a small team but failed as they grew. Key lessons include: making environments portable across infrastructure to allow scaling; building quality through an architecture and test strategy that optimize lead time; and empowering cross-functional teams through consensus on practices and autonomous environments.
DevOps - Motivadores e Benefícios
DevOps é um conjunto de princípios, métodos e tecnologias para lidar com o desafio de liberar rapidamente a evolução do software de alta qualidade desde o desenvolvimento até a produção, onde tudo se torna programável: aplicação, testes e Infraestrutura.
Devops Mindset Essentials
First DRAFT of a DevOps presentation and posters covering the essentials for a DevOps mindset. Help improve the content by forking and contributing a pull request to https://github.com/wpschaub/DevOps-mindset-essentials/blob/master/README.md.
Dev ops != Dev+Ops
DevOps, sibling of Agile is born of the need to improve IT service delivery agility to the more stable environment.
DevOps movement emphasizes tearing the boundaries between makers (Development) & caretakers (Operations) of IT services/products.
Soasta | CloudBees webinar 11/12/2015
The webinar discusses enabling continuous performance testing with Jenkins CI/CD pipelines. It introduces SOASTA and CloudBees as partners that offer a complete cloud-based service for continuous performance testing and continuous delivery with Jenkins. The webinar agenda includes building performance tests, connecting tests to Jenkins, establishing performance baselines, executing tests in parallel with CD pipelines in Jenkins Workflow, and reviewing performance and functional test results.
DevOps for beginners
From the the teams struggling with DevOps to experienced professionals trying to make a shift to DevOps, this presentation helps in how understanding how DevOps makes Deliveries faster and accurate
Continuous testing & devops with @petemar5hall
This document discusses testing software in high frequency delivery environments using continuous testing and DevOps practices. It outlines how continuous testing is not just about test automation, but also includes automated management of environments, application feedback through monitoring, and engaging in XP practices. DevOps helps by automating building, testing, and deployment to provide consistency and tools for teams. Characteristics of high frequency delivery environments include automating infrastructure, testing, and deployment to reduce errors and allow for smaller, more frequent deliveries. This allows for a single view of quality and faster restore times when issues arise.
Práticas, Técnicas e Ferramentas para Continuous Delivery com ALM
Palestra feita na trilha de DevOps no TDC2014 em São Paulo.
Como estruturar uma estratégia de Continuous Delivery suportada por ALM, promovendo visibilidade, colaboração e controle
Test Automation at the Speed of Agile: Making It Work Every Build
Join Danny McKeown, Paychex’s lead test enterprise automation architect, to see how a small tools group supports nearly one-hundred agile teams as they move toward achieving continuous delivery. Take part in the conversation to understand how Paychex is progressing in the third year of its agile transformation. Danny describes how this IT-wide initiative has impacted how the tools group supports so many teams and changed its own practices to provide more timely support. With the goal of increasing velocity, a solid automation strategy has become a powerful enabler. Danny describes how Paychex assesses progress with a maturity lens. Their always-evolving automation framework serves web and mobile team requirements. He shares an HTML5 mini-case study, describing how adopting responsive web changed practices. Embedding quality in multiple daily builds has not come without its challenges, and Danny describes the lessons learned and their next steps. This interactive session will encourage participants to share their experiences as well—so come ready!
Testing in the new age of DevOps
- Introduction to DevOps.
- Glossary.
- Continuous testing.
- The DevOps lifecycle.
- Where does QA fit in DevOps.
- Test-Driven Development (TDD).
- References.
DevOps - Introduction to data science
Lecture: Introduction to Data Science
given 2017 at Technical University of Kaiserslautern, Germany
topic: DevOps and professional development
Similar to Role of QA in Continuous Delivery (20)
DevOps Indonesia - DevOps Toolchain and Technology
DevOps Indonesia - DevOps Toolchain and Technology
How to win at DevOps (and understand it along the way)
How to win at DevOps (and understand it along the way)
Release Engineering Downstream of an OpenStack Project
Release Engineering Downstream of an OpenStack Project
Release Automation: Better Quality, Faster Deployment, Amazing ROI
Release Automation: Better Quality, Faster Deployment, Amazing ROI
Павел Чуняев - State of Continuous Delivery in 2015
Павел Чуняев - State of Continuous Delivery in 2015
State of continuous delivery in 2015 - Minsk 15-5-2015
State of continuous delivery in 2015 - Minsk 15-5-2015
Continuous Delivery: The New Normal. London Event.
Continuous Delivery: The New Normal. London Event.
Práticas, Técnicas e Ferramentas para Continuous Delivery com ALM
Práticas, Técnicas e Ferramentas para Continuous Delivery com ALM
Test Automation at the Speed of Agile: Making It Work Every Build
Test Automation at the Speed of Agile: Making It Work Every Build
More from Lukáš Fryč
Arquillian: Helping web developers and QA get along
Modern development practices include testing our Web applications as a fundamental part of the application development lifecycle. Web UIs though can be particularly difficult to test with basic tools. Arquillian is an award-winning integration testing framework and Selenium WebDriver is an outstanding tool for UI test automation. Together they offer a base for high-quality tests.
This session looks to the Arquillian Universe for help. Equipped with the Arquillian extensions - Drone, Graphene and Warp - we will show you tests that cover both client-side (REST) and server-rendered (JSF) web applications. With a single test it is now possible to assert state (both in the server and on the client) at arbitrary points within the request lifecycle!
We will look at current best practices for how to achieve a rapid turnaround when doing test development by minimizing the effort required to write tests, and thereby increase productivity and thus making these tests future-proof. Additionally we will show tools and techniques that provide a separation of concerns between test authors (developers) and test automators (QA). How to execute a single test in both arbitrary server containers as well as arbitrary client browsers. And how it can enable us to run test suites in constrained environments like cloud-based continuous integration providers.
JSF 2.2 Deep Dive with RichFaces 5
JavaServer Faces (JSF) is the portion of the Java EE specification that deals with the rendering of web UIs. A server-side rendering framework, JSF is component centric and nicely encapsulates both visual and non-visual UI elements and provides a health component marketplace.
The JSF specification as recently undergone a minor release increment with the release of JSF 2.2. While not the revolution seen with the release of the 2.0 specification, JSF 2.2 does include some new and sought-after features. We’ll cover these new features discussing: View Actions, Faces Flows, HTML 5 support, improved CDI integration, the FileUpload component, Resource library contract, stateless views, and the new window ID.
Taking a use-case based approach we’ll see how this laundry list of new features will affect your application development. Finally we’ll look at how the RichFaces component library is leveraging these new capabilities in the upcoming RichFaces 5 release.
Web Components: Rethinking Web App Development
Web Components is an emerging umbrella of standards that fundamentally changes the way we compose our web applications. Web Components abstract away the complexity introduced when using low-level building blocks such as HTML, CSS and JavaScript.
This complexity is usually handled on the level of web frameworks, where we can perceive few phenomenons: web frameworks usually
it’s own way of how to work with low-level APIs,
maintains custom UI widget suites,
lock us in a particular solution.
What about inventing some common denominator that could frameworks and app developers built upon?
Web Components are essentially a set of improvements that are being added to the web platform: HTML Imports, Shadow DOM, <template>, custom elements, decorators. All of these APIs are on their way to becoming standards. But can we leverage them already?
Thanks to polyfill libraries like Polymer we can leverage those new APIs right away!
Thanks to Web Components, the web will get a new common denominator which kills fragmentation and encourages reuse and portability of user interfaces.
Web Technologies in Java EE 7
This document discusses various web technologies in Java EE including JSF 2.2, JAX-RS 2.0, JSON-P, and WebSocket. It provides an overview of client-side vs server-side web approaches, describes the capabilities and goals of each technology, and demonstrates examples of using JAX-RS for RESTful services, the JSON processing APIs, and WebSocket. The document is presented by Lukas Fryc, a software engineer at Red Hat interested in Java EE, HTML5, and Web Components.
Designing Top-Class Test Suites for Web Applications
The evolution which came with the Arquillian, award-winning integration test framework, and Selenium, outstanding tool for UI automation, allows to write high-quality tests. But these technologies can’t save the world by themselves, since they are leaving too many questions open:
* Does Selenium cover everything? It covers page transitions, a simple JavaScript interaction and a portion of DOM. Is it really enough?
* Mocking requests for testing server-side code is pain. Is it necessary?
* Are you able to detect that your component’s visual representation changes?
* Does investigating these changes involve a disproportionate amount of effort?
* Isn’t manual test development too expensive?
What if you could fill all the above gaps?
Going mobile with RichFaces
The rise of portable devices last year shows how important is making applications compatible with mobiles. When it comes to web applications, JSF offers the same strong background for mobile development as it does for desktop applications: an extensible framework with a widely-accepted development model, allowing reuse of JSF programming skills and technologies on the mobile platform. RichFaces 4.1 goes behind concepts brought by JSF and provides developer with framework which makes your applications ready for mobile devices and offers you as rich component suite as for desktop environments. Lukas is going to show you how the RichFaces Showcase was turned into an application for portable devices, how a light-weight javascript framework was designed for making RichFaces applications mobile ready, the principles of an one-page application design and what are the necessary optimizations for making RichFaces applications run on mobile devices properly.
RichFaces CDK: Rapid JSF Component Development
JSF component libraries provide you with a solid basis for building enterprise UIs as they are covering most common use cases. But what can you do in a case that no existing component fits your project requirements?
There are many JavaScript component projects which offer together nearly infinite possibilities. But it might not be evident that leveraging these JavaScript frameworks is as easy as writing plain old HTML code, separating component and page development efforts. But how to wrap these components to fit into JSF eco-system?
That’s exactly where RichFaces CDK comes into play.
Arquillian: Effective tests from the client to the server
Tools like Selenium, an outstanding tool for UI test automation, and Arquillian, an award-winning integration testing framework, offer a base for high-quality tests which are crucial for a web app development. However writing UI tests and covering server-side logic leaves many questions open:
* Does Selenium cover everything? Page transitions, simple JavaScript interaction and a portion of DOM. Is it really enough?
* Mocking requests for testing server-side code is pain. Is it necessary?
* Are you able to detect that your component’s visual representation changes?
* Does investigating these changes involve a disproportionate amount of effort?
* Isn’t manual test development too expensive?
Testing JSF with Arquillian and Selenium
Testing of web applications is significant part of development cycle from perspective of both, application development and quality assurance.
JSF concepts makes testing of applications simple by separation of concerns, but enforces employing of specific tools for testing business logic and user interface.
Lukas covers testing pitas and introduce frameworks which make testing of JSF application a breeze and motivate developers to follow concepts of test-driven development.
RichFaces 4 rolling to Mobile Era
RichFaces 4 rolling to Mobile Era
A session at JSF and RichFaces Workshop/Conference
Mobile devices and smart phones are rapidly becoming the primary web client for significant amount of users. For the web developers it represents new area where they should focus when developing applications. They need to handle device specifics as feature support and display possibilities.
RichFaces is opening doors for engineers which are focused on application development and rely on framework to handle consequences. RichFaces comprises suite of component which is optimized for use on both, mobile and desktop clients.
Lukas discuss where HTML5 and CSS3 fits into the picture and how can JSF and RichFaces
More from Lukáš Fryč (10)
Arquillian: Helping web developers and QA get along
Arquillian: Helping web developers and QA get along
Designing Top-Class Test Suites for Web Applications
Designing Top-Class Test Suites for Web Applications
Arquillian: Effective tests from the client to the server
Arquillian: Effective tests from the client to the server
Recently uploaded
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, 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.
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
Recently uploaded (20)
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
Role of QA in Continuous Delivery
- 1. ROLE OF QA IN CONTINUOUS DELIVERY L U K A S F R Y C | T E S T C R U N C H | 3 . 1 1 . 2 0 1 7
- 2. Lukáš Fryč • Lead Frontend Engineer • 10 years experience in frontend engineering (15+ with programming) • Testing Geek • 8 Software Patents (3 in space of Software Quality) • Core Contributor to Arquillian testing platform à (Duke’s award for most innovative Java project) • Mentoring / Coaching my teammates
- 3. MEET OUR TEAM W R I T E H E R E S O M E T H I N G TABLE OF CONTENTS FAST-PACED ENVIRONMENT QA AS PART OF ORGANIZATION CONTINUOUS DELIVERY TEST AUTOMATION R O L E O F Q A I N C O N T I N U O U S D E V E L O P M E N T
- 4. SaaS = S O F T W A R E A S A S E R V I C E
- 5. Software as a Service TRACK ANALYZE ENGAGE +41% +25% +10% +14%
- 6. Software Complexity TRACK ANALYZE ENGAGE +41% +25% +10% +14%
- 8. ORGANIZATION Q A A S P A R T O F
- 13. Melvin Conway „Organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations.“ CONWAY’S LAW
- 14. DANGERS OF SILOS
- 15. Horizontal Team Split Frontend Backend A.I.OpsQA
- 16. Cross-Functional Teams NEW PREDICTION SYSTEM FRONTEND PERFORMANCE Frontend Backend A.I.OpsQA IMPROVE CAMPAIGN THROUGHPUTIMPROVE…
- 18. The time between the initiation and completion of the production process LEAD TIME CONTINUOUS DELIVERY METRICS The total elapsed time to move a unit work from the beginning to the end of a physical process. CYCLE TIME
- 19. Wiliam Gibson „The future is already here — it's just not very evenly distributed.“ ABOUT THE FUTURE
- 20. INNOVATION
- 21. CONTINUOUS * Deploy as the final stage of continuous integration CONTINUOUS DEPLOYMENT Integrate early and often Everyone checks into master at least once a day CONTINUOUS INTEGRATION Software is always in a deployable state. CONTINUOUS DELIVERY
- 22. CONTINUOUS DELIVERY Analysis + Design Development Testing + Showcase Integration + QA Release + Operations The “last mile” Always in a releasable state
- 23. PLANNING = FEATURE BREAKDOWN 1 1 1 1 2 2 2 2 2 3 < 1DAY DELIVERY
- 24. TEST AUTOMATION
- 26. A BIT OF THEORY…
- 29. AUTOMATE TO FREE HANDS FOR QUALITY
- 30. MEET OUR TEAM W R I T E H E R E S O M E T H I N G ...THAT‘S IT FAST-PACED ENVIRONMENT QA AS PART OF ORGANIZATION CONTINUOUS DELIVERY TEST AUTOMATION R O L E O F Q A I N C O N T I N U O U S D E L I V E R Y
- 31. MEET OUR TEAM W R I T E H E R E S O M E T H I N G @lfryc #Exponea THANK YOU L U K A S F R Y C