This document summarizes a presentation about establishing release quality levels and acceptance tests. It discusses defining quality as meeting user requirements and being free of defects. It presents frameworks for considering quality, including the traditional iron triangle of scope, schedule and cost, and expanding it to a quality box that also includes intrinsic quality and value. The presentation outlines setting release quality levels based on factors like testing and defects, and developing acceptance tests owned by product managers to define completion and allow for automated regression testing.
YuryMakedonov_SavingRunawayProject_DKL_2005_07Yury M
This document describes how a failing software project was turned around using agile principles. The project originally followed a waterfall approach but failed to deliver what users wanted. It was restarted using iterative development, active user involvement in testing and requirements development, co-location of team members, and oversight from a change control board including the project sponsor. These agile practices allowed the project to be delivered in increments that met user needs.
Quality Assurance to Test Engineering – Insights From our Journey by Oksana S...QA or the Highway
This document discusses the transformation of a QA organization to a test engineering organization. It provides historical context on the evolution of testing techniques from the 1970s to present. It then details the specific transformation journey the organization took, including providing awareness training, mentorship, skills assessments, hiring test engineers, and establishing partnerships with offshore test engineering firms. The results were removing barriers between manual and automation testing, enabling more associates to use automation, and shifting testing upstream. Future trends of testing as a developer responsibility and increasing automation are also discussed.
Requirements and Acceptance Tests: Yes, They Go TogetherTechWell
The practice of software development requires a clear understanding of business needs. Misunderstanding requirements causes waste, slipped schedules, and mistrust. Developers implement their perceived interpretation of requirements; testers test against their perceptions. Disagreement can arise about implementation defects, when the cause is really a disagreement about a requirement. Ken Pugh shows how early acceptance test development decreases requirements misunderstandings by both developers and testers. A testable requirement provides a single source that serves as the analysis document, acceptance criteria, regression test suite, and progress tracker for each feature. Explore how the business, testers, and developers can create, evaluate, and use testable requirements. Join Ken to examine how to transform requirements into stories, which are small units of work that have business value, small implementation effort, and easy-to-understand acceptance tests. Learn how testers and requirement elicitors can work together to create acceptance tests prior to implementation.
Continuous Quality: What DevOps Means for QAJeff Sussna
The document discusses how DevOps is changing the role of quality assurance (QA). It argues that with software increasingly delivered as a service, the focus of QA must shift from testing software to ensuring quality across four dimensions: functionality, operability, deliverability, and coherency. The new QA role involves representing the customer perspective, facilitating requirements understanding, and acting as a "boundary-spanning mirror" to help development, operations, and other teams understand each other and customers. Continuous delivery requires QA to test outside-in across the full customer experience and help build quality into the entire service delivery process.
Everybody loves a good love story. And even more so one that mixes in pop stars and the music business! If you have an interest in hearing about how the benefits of DevOps can help unblock the delivery of IT innovation in your business then you’ll want to hear this story.
Continuous testing & devops with @petemar5hallPeter Marshall
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.
Looking to move to Continuous Delivery? Worried about the quality of your the code? Helping your developers understand clean-code practices and getting the right testing strategy in place can take a while. What should you do to control the quality of the incoming code till then? This talk shares our experience of using PRRiskAdvisor to gradually educate and influence developers to write better code and also help the code reviewer to be more effective at their reviews.
Every time a developer raises a pull-request, PRRiskAdvisor analyzes the files that were changed and publishes a report on the pull request itself with the overall risk associated with this pull request and also risk associated with each file. It also runs static code analysis using SonarQube and publishes the configured violations as comments on the pull request. This way the reviewer just has to look at the pull request to get a decent idea of what it means to review this pull request. If there are too many violations, then PRRiskAdvisor can also automatically reject the pull request.
By doing this, we saw our developers starting paying more attention to clean code practices and hence the overall quality of the incoming code improved, while we worked on putting the right engineering practices and testing strategy in place.
More details: https://confengine.com/last-conference-canberra-2018/proposal/7294/improving-the-quality-of-incoming-code
Conference Link: https://2019.agileindia.org
Presentation from first Poznań Testing and Quality group meeting. I with Lukasz presented how we build and share knowledge in QA team in Cognifide
Authors: Zbyszek Moćkun, Łukasz Morawski
YuryMakedonov_SavingRunawayProject_DKL_2005_07Yury M
This document describes how a failing software project was turned around using agile principles. The project originally followed a waterfall approach but failed to deliver what users wanted. It was restarted using iterative development, active user involvement in testing and requirements development, co-location of team members, and oversight from a change control board including the project sponsor. These agile practices allowed the project to be delivered in increments that met user needs.
Quality Assurance to Test Engineering – Insights From our Journey by Oksana S...QA or the Highway
This document discusses the transformation of a QA organization to a test engineering organization. It provides historical context on the evolution of testing techniques from the 1970s to present. It then details the specific transformation journey the organization took, including providing awareness training, mentorship, skills assessments, hiring test engineers, and establishing partnerships with offshore test engineering firms. The results were removing barriers between manual and automation testing, enabling more associates to use automation, and shifting testing upstream. Future trends of testing as a developer responsibility and increasing automation are also discussed.
Requirements and Acceptance Tests: Yes, They Go TogetherTechWell
The practice of software development requires a clear understanding of business needs. Misunderstanding requirements causes waste, slipped schedules, and mistrust. Developers implement their perceived interpretation of requirements; testers test against their perceptions. Disagreement can arise about implementation defects, when the cause is really a disagreement about a requirement. Ken Pugh shows how early acceptance test development decreases requirements misunderstandings by both developers and testers. A testable requirement provides a single source that serves as the analysis document, acceptance criteria, regression test suite, and progress tracker for each feature. Explore how the business, testers, and developers can create, evaluate, and use testable requirements. Join Ken to examine how to transform requirements into stories, which are small units of work that have business value, small implementation effort, and easy-to-understand acceptance tests. Learn how testers and requirement elicitors can work together to create acceptance tests prior to implementation.
Continuous Quality: What DevOps Means for QAJeff Sussna
The document discusses how DevOps is changing the role of quality assurance (QA). It argues that with software increasingly delivered as a service, the focus of QA must shift from testing software to ensuring quality across four dimensions: functionality, operability, deliverability, and coherency. The new QA role involves representing the customer perspective, facilitating requirements understanding, and acting as a "boundary-spanning mirror" to help development, operations, and other teams understand each other and customers. Continuous delivery requires QA to test outside-in across the full customer experience and help build quality into the entire service delivery process.
Everybody loves a good love story. And even more so one that mixes in pop stars and the music business! If you have an interest in hearing about how the benefits of DevOps can help unblock the delivery of IT innovation in your business then you’ll want to hear this story.
Continuous testing & devops with @petemar5hallPeter Marshall
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.
Looking to move to Continuous Delivery? Worried about the quality of your the code? Helping your developers understand clean-code practices and getting the right testing strategy in place can take a while. What should you do to control the quality of the incoming code till then? This talk shares our experience of using PRRiskAdvisor to gradually educate and influence developers to write better code and also help the code reviewer to be more effective at their reviews.
Every time a developer raises a pull-request, PRRiskAdvisor analyzes the files that were changed and publishes a report on the pull request itself with the overall risk associated with this pull request and also risk associated with each file. It also runs static code analysis using SonarQube and publishes the configured violations as comments on the pull request. This way the reviewer just has to look at the pull request to get a decent idea of what it means to review this pull request. If there are too many violations, then PRRiskAdvisor can also automatically reject the pull request.
By doing this, we saw our developers starting paying more attention to clean code practices and hence the overall quality of the incoming code improved, while we worked on putting the right engineering practices and testing strategy in place.
More details: https://confengine.com/last-conference-canberra-2018/proposal/7294/improving-the-quality-of-incoming-code
Conference Link: https://2019.agileindia.org
Presentation from first Poznań Testing and Quality group meeting. I with Lukasz presented how we build and share knowledge in QA team in Cognifide
Authors: Zbyszek Moćkun, Łukasz Morawski
The document discusses shifting the focus of internationalization (i18n) efforts earlier in the software development process. Traditionally, i18n was seen as the responsibility of localization teams and tested later in the cycle. However, with faster release cycles and the need to reach global customers quicker, i18n needs to be integrated as a core part of the initial development process. Static analysis tools can help developers test for i18n issues proactively during development rather than waiting until localization. Catching i18n bugs earlier saves significant time and costs compared to fixing them late in the cycle during localization. The presentation advocates making world-ready software a priority from the start through processes, guidelines and tools that verify i18n compliance
How testers add value to the organization appium confCorina Pip
Testers add value to organizations by participating in requirements definition, technical discussions, and providing input to improve quality and testability. They help ensure requirements are clear and the developed features meet them by testing cases and automated tests. Testers prevent bugs, understand the role of automation in regression testing and fast delivery, and perform security, performance, accessibility, and other types of testing. Overall, testers help organizations achieve quality software and satisfy customers.
This document provides information about a presentation titled "Integrating Automated Testing into DevOps" given by Jeff Payne of Coveros, Inc. It includes biographical information about Jeff Payne, an agenda for the presentation, and content that will be covered, including definitions of DevOps, common DevOps terminology, automated testing for continuous integration and continuous delivery, environments for testing, common tools used, and demos of automated testing.
The digital shakeout in quality assurance and testing by Shiva Agolla and Sat...QA or the Highway
This document discusses the key findings of a survey on quality assurance and testing. It summarizes that digital transformation, agile development, test automation, industrialization, and budgets are the main topics covered. The document highlights that increasing quality is the most important objective of QA and testing, and that challenges are increasing with testing in agile environments. It recommends that organizations increase smart test automation, define QA analytics strategies, invest in smart platforms, and transform QA to support agile and DevOps teams.
Software Testing is a very time consuming activity and consumes enormous amount of effort in any software project. It makes sense to improve productivity of software testing as well as to reduce the defect density in the software, so that overall economy in the project is achieved. In order to do this, we need to understand the defects, their root causes and be able to predict their outcome in advance during estimation.
This presentation by Oaksys is an attempt to share its experience of over 10 years (1998-2008) with the practitioners.
Acceptance Testing for Continuous Delivery by Dave Farley at #AgileIndia2019Agile India
Writing and maintaining a suite of acceptance tests that can give you a high level of confidence in the behaviour and configuration of your system is a complex task. In this session, Dave will describe approaches to acceptance testing that allow teams to:
work quickly and effectively
build excellent functional coverage for complex enterprise-scale systems
manage and maintain those tests in the face of change, and of evolution in both the codebase and the understanding of the business problem.
This workshop will answer the following questions, and more:
How do you fail fast?
How do you make your testing scalable?
How do you isolate test cases from one-another?
How do you maintain a working body of tests when you radically change the interface to your system?
More details:
https://confengine.com/agile-india-2019/proposal/8539/acceptance-testing-for-continuous-delivery
Conference link: https://2019.agileindia.org
A lecture for startup & established companies on the interferences and barriers (some real, some percieved) to executing the operational launch of their products (NPD, NPI, Phase Gates). How to work with contract manufactures, evaluate their cost model, where the biggest opportunities for risk reside in the entire process. This is a series done by an expert in the field, this removes the academic aspects of launching products and focuses on practical, relevant, innovative demonstrations. So of course the slide deck cannot possibly reveal what’s fully entailed in the short workshop. Feel free to contact dan@productrevolution.org for details.
Presentation from second Poznań Testing and Quality group.
This presentation sum up my experience (about 5 years) with automation, as engineer or manager
Exploratory testing and Dev Ops - best friends?Sven Schirmer
Exploratory testing and DevOps practices like test automation can work well together when used appropriately. Exploratory testing involves testing software from the perspective of end users to understand real-world usage, which can then be used to improve automated test coverage. Session-based testing pairs business and development teams to jointly test software. Logging user journeys in production and using that data to plan exploratory test sessions helps test automation better reflect actual usage. Exploratory testing brings end users and different perspectives into the testing process early, discovers new issues, and improves customer relationships with minimal time investment when run regularly.
The document discusses the role of quality assurance (QA) in agile teams. It compares the traditional and agile approaches to QA, outlining the agile QA responsibilities which include helping define user stories and acceptance criteria, estimating stories, ensuring testing is accounted for in planning, and more. Common mistakes like not involving QA throughout or having them run tests in subsequent sprints are also covered.
Building and Scaling High Performing Technology Organizations by Jez Humble a...Agile India
This document discusses building and scaling high-performing technology organizations through agile practices and DevOps. It touches on topics like creating value streams across projects, challenges with going agile at an enterprise level, the importance of principles like test-driven development, and building a culture of learning from failures. It also provides links to research on metrics like lead time for changes and deploy frequency that correlate with high performance.
Exploratory testing in practice, short story how approach influenced on strategyZbyszek Mockun
This document discusses exploratory testing techniques and how one company implemented exploratory testing. It defines exploratory testing as an approach rather than a technique. The company used exploratory techniques like tours and testing heuristics. Initially, their exploratory testing process lacked structure and traceability. To improve it, they implemented a session-based test management approach. This involved planning testing sessions, taking notes within a tool, and having debrief sessions. It helped provide structure while maintaining the flexibility of exploratory testing. They were then able to measure and audit their exploratory testing more effectively.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
Behavior Driven Development—A Guide to Agile Practices by Josh EastmanQA or the Highway
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
This webinar examines how the role of QA is fundamentally different in an Agile project when compared to a traditional project.
We will discuss in this webinar:
- Fundamental shift in the role QA in Agile
- Specific responsibilities of an agile QA tester along the Agile development cycle
- Common mistakes and how to avoid them
- If you are curious about Agile Methods, this webinar will give you a taste of “agile ” from the QA perspective.
Read more from the original copy at https://www.synerzip.com/webinar/qa-role-in-agile-teams/
The concept of “shifting testing left” in the software development lifecycle is not new. Shifting testing from manual to automated and then upstream into engineering is a driving factor in DevOps and agile software development. However, Michael Nauman wonders why test automation, DevOps, and agile software development still frequently fail to deliver on their promises? Aligning and hardening your DevOps and test automation—along with streamlining your agile processes—is critical to your project. Michael shares how AutoCAD’s shifting testing left enabled improvements within their engineering team. Learn how the team increased engineering reliability and velocity, and forced process changes upstream into design and research all the way through to product support. Leave knowing why the concept of separation of concerns with regards to quality is as fundamental as the separation of code quality from product quality. Learn how the AutoCAD web team used process dogma and ruthless prioritization to combat metric idolatry and the host of other evils that hold teams back from fully realizing their potential and going beyond agile.
Accelerate Testing in Agile through a Shared Business Domain LanguageTechWell
In agile projects, when the cycle from ideas to production shortens from months to hours, each software development activity—including testing—is impacted. Reaching this level of agility in testing requires massive automation. But test execution is only one side of the coin. How do we design and maintain tests at the required speed and scale? Testing should start very early in the development process and be used as acceptance criteria by the project stakeholders. Early test design, using a business domain language to write tests, is an efficient solution to support rapid iterations and helps align the team on the definition of done. These principles are the basis of acceptance test-driven development practices. Laurent Py shows you how the use of business domain languages enables test refactoring and accelerates automation. Come and learn how you can leverage acceptance tests and key test refactoring techniques.
In this webinar,Markus Gärtner looks at hardware development using Scrum. He takes a closer look on hardware companies that succeed with Scrum, identifying patterns that work in hardware development including R&D and manufacturing.
Exploratory Testing Kari Kakkonen BTD 2017Kari Kakkonen
My talk on Exploratory Testing basics and its future at Belgium Testing Days / BNTQB Test Summit 2017 https://btdconf.org/ bit of slides revamp included
Is Test Planning a lost art in Agile? by Michelle WilliamsQA or the Highway
This document provides an overview of a presentation on agile test planning. It discusses the challenges of agile requirements and how test strategies serve a purpose beyond a single sprint. It also examines how the agile manifesto relates to planning and the value of test plans in agile. The presentation outlines four testing phases in agile - requirements and design, story/feature verification, system verification, and acceptance. It provides examples of what should be included in a test plan for each phase such as scenarios, automation approach, dependencies, and acceptance criteria.
Backward thinking design qa system for quality goalsgaoliang641
This document discusses strategies for designing a quality assurance system to meet quality goals. It outlines various types of testing, such as user testing, integration testing, and performance testing. It also poses many questions about testing organization, processes, tools, and metrics that need to be considered when setting up a QA system. The document emphasizes establishing repetitive regression testing to stabilize code branches before release and using automation to help reduce the workload of testing.
Technical debt can accumulate when teams prioritize quickly delivering features over maintaining quality. This leads to slower development and more bugs over time. Automation helps reveal technical debt through continuous integration tests, code inspections, and trend analysis. As teams automate their build, deployment, and testing processes, they often discover previously unknown issues. Both direct testing and the learning from automation efforts help teams understand and address technical debt. Managing technical debt through automation provides benefits at both the team and enterprise levels.
The document discusses shifting the focus of internationalization (i18n) efforts earlier in the software development process. Traditionally, i18n was seen as the responsibility of localization teams and tested later in the cycle. However, with faster release cycles and the need to reach global customers quicker, i18n needs to be integrated as a core part of the initial development process. Static analysis tools can help developers test for i18n issues proactively during development rather than waiting until localization. Catching i18n bugs earlier saves significant time and costs compared to fixing them late in the cycle during localization. The presentation advocates making world-ready software a priority from the start through processes, guidelines and tools that verify i18n compliance
How testers add value to the organization appium confCorina Pip
Testers add value to organizations by participating in requirements definition, technical discussions, and providing input to improve quality and testability. They help ensure requirements are clear and the developed features meet them by testing cases and automated tests. Testers prevent bugs, understand the role of automation in regression testing and fast delivery, and perform security, performance, accessibility, and other types of testing. Overall, testers help organizations achieve quality software and satisfy customers.
This document provides information about a presentation titled "Integrating Automated Testing into DevOps" given by Jeff Payne of Coveros, Inc. It includes biographical information about Jeff Payne, an agenda for the presentation, and content that will be covered, including definitions of DevOps, common DevOps terminology, automated testing for continuous integration and continuous delivery, environments for testing, common tools used, and demos of automated testing.
The digital shakeout in quality assurance and testing by Shiva Agolla and Sat...QA or the Highway
This document discusses the key findings of a survey on quality assurance and testing. It summarizes that digital transformation, agile development, test automation, industrialization, and budgets are the main topics covered. The document highlights that increasing quality is the most important objective of QA and testing, and that challenges are increasing with testing in agile environments. It recommends that organizations increase smart test automation, define QA analytics strategies, invest in smart platforms, and transform QA to support agile and DevOps teams.
Software Testing is a very time consuming activity and consumes enormous amount of effort in any software project. It makes sense to improve productivity of software testing as well as to reduce the defect density in the software, so that overall economy in the project is achieved. In order to do this, we need to understand the defects, their root causes and be able to predict their outcome in advance during estimation.
This presentation by Oaksys is an attempt to share its experience of over 10 years (1998-2008) with the practitioners.
Acceptance Testing for Continuous Delivery by Dave Farley at #AgileIndia2019Agile India
Writing and maintaining a suite of acceptance tests that can give you a high level of confidence in the behaviour and configuration of your system is a complex task. In this session, Dave will describe approaches to acceptance testing that allow teams to:
work quickly and effectively
build excellent functional coverage for complex enterprise-scale systems
manage and maintain those tests in the face of change, and of evolution in both the codebase and the understanding of the business problem.
This workshop will answer the following questions, and more:
How do you fail fast?
How do you make your testing scalable?
How do you isolate test cases from one-another?
How do you maintain a working body of tests when you radically change the interface to your system?
More details:
https://confengine.com/agile-india-2019/proposal/8539/acceptance-testing-for-continuous-delivery
Conference link: https://2019.agileindia.org
A lecture for startup & established companies on the interferences and barriers (some real, some percieved) to executing the operational launch of their products (NPD, NPI, Phase Gates). How to work with contract manufactures, evaluate their cost model, where the biggest opportunities for risk reside in the entire process. This is a series done by an expert in the field, this removes the academic aspects of launching products and focuses on practical, relevant, innovative demonstrations. So of course the slide deck cannot possibly reveal what’s fully entailed in the short workshop. Feel free to contact dan@productrevolution.org for details.
Presentation from second Poznań Testing and Quality group.
This presentation sum up my experience (about 5 years) with automation, as engineer or manager
Exploratory testing and Dev Ops - best friends?Sven Schirmer
Exploratory testing and DevOps practices like test automation can work well together when used appropriately. Exploratory testing involves testing software from the perspective of end users to understand real-world usage, which can then be used to improve automated test coverage. Session-based testing pairs business and development teams to jointly test software. Logging user journeys in production and using that data to plan exploratory test sessions helps test automation better reflect actual usage. Exploratory testing brings end users and different perspectives into the testing process early, discovers new issues, and improves customer relationships with minimal time investment when run regularly.
The document discusses the role of quality assurance (QA) in agile teams. It compares the traditional and agile approaches to QA, outlining the agile QA responsibilities which include helping define user stories and acceptance criteria, estimating stories, ensuring testing is accounted for in planning, and more. Common mistakes like not involving QA throughout or having them run tests in subsequent sprints are also covered.
Building and Scaling High Performing Technology Organizations by Jez Humble a...Agile India
This document discusses building and scaling high-performing technology organizations through agile practices and DevOps. It touches on topics like creating value streams across projects, challenges with going agile at an enterprise level, the importance of principles like test-driven development, and building a culture of learning from failures. It also provides links to research on metrics like lead time for changes and deploy frequency that correlate with high performance.
Exploratory testing in practice, short story how approach influenced on strategyZbyszek Mockun
This document discusses exploratory testing techniques and how one company implemented exploratory testing. It defines exploratory testing as an approach rather than a technique. The company used exploratory techniques like tours and testing heuristics. Initially, their exploratory testing process lacked structure and traceability. To improve it, they implemented a session-based test management approach. This involved planning testing sessions, taking notes within a tool, and having debrief sessions. It helped provide structure while maintaining the flexibility of exploratory testing. They were then able to measure and audit their exploratory testing more effectively.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
Behavior Driven Development—A Guide to Agile Practices by Josh EastmanQA or the Highway
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
This webinar examines how the role of QA is fundamentally different in an Agile project when compared to a traditional project.
We will discuss in this webinar:
- Fundamental shift in the role QA in Agile
- Specific responsibilities of an agile QA tester along the Agile development cycle
- Common mistakes and how to avoid them
- If you are curious about Agile Methods, this webinar will give you a taste of “agile ” from the QA perspective.
Read more from the original copy at https://www.synerzip.com/webinar/qa-role-in-agile-teams/
The concept of “shifting testing left” in the software development lifecycle is not new. Shifting testing from manual to automated and then upstream into engineering is a driving factor in DevOps and agile software development. However, Michael Nauman wonders why test automation, DevOps, and agile software development still frequently fail to deliver on their promises? Aligning and hardening your DevOps and test automation—along with streamlining your agile processes—is critical to your project. Michael shares how AutoCAD’s shifting testing left enabled improvements within their engineering team. Learn how the team increased engineering reliability and velocity, and forced process changes upstream into design and research all the way through to product support. Leave knowing why the concept of separation of concerns with regards to quality is as fundamental as the separation of code quality from product quality. Learn how the AutoCAD web team used process dogma and ruthless prioritization to combat metric idolatry and the host of other evils that hold teams back from fully realizing their potential and going beyond agile.
Accelerate Testing in Agile through a Shared Business Domain LanguageTechWell
In agile projects, when the cycle from ideas to production shortens from months to hours, each software development activity—including testing—is impacted. Reaching this level of agility in testing requires massive automation. But test execution is only one side of the coin. How do we design and maintain tests at the required speed and scale? Testing should start very early in the development process and be used as acceptance criteria by the project stakeholders. Early test design, using a business domain language to write tests, is an efficient solution to support rapid iterations and helps align the team on the definition of done. These principles are the basis of acceptance test-driven development practices. Laurent Py shows you how the use of business domain languages enables test refactoring and accelerates automation. Come and learn how you can leverage acceptance tests and key test refactoring techniques.
In this webinar,Markus Gärtner looks at hardware development using Scrum. He takes a closer look on hardware companies that succeed with Scrum, identifying patterns that work in hardware development including R&D and manufacturing.
Exploratory Testing Kari Kakkonen BTD 2017Kari Kakkonen
My talk on Exploratory Testing basics and its future at Belgium Testing Days / BNTQB Test Summit 2017 https://btdconf.org/ bit of slides revamp included
Is Test Planning a lost art in Agile? by Michelle WilliamsQA or the Highway
This document provides an overview of a presentation on agile test planning. It discusses the challenges of agile requirements and how test strategies serve a purpose beyond a single sprint. It also examines how the agile manifesto relates to planning and the value of test plans in agile. The presentation outlines four testing phases in agile - requirements and design, story/feature verification, system verification, and acceptance. It provides examples of what should be included in a test plan for each phase such as scenarios, automation approach, dependencies, and acceptance criteria.
Backward thinking design qa system for quality goalsgaoliang641
This document discusses strategies for designing a quality assurance system to meet quality goals. It outlines various types of testing, such as user testing, integration testing, and performance testing. It also poses many questions about testing organization, processes, tools, and metrics that need to be considered when setting up a QA system. The document emphasizes establishing repetitive regression testing to stabilize code branches before release and using automation to help reduce the workload of testing.
Technical debt can accumulate when teams prioritize quickly delivering features over maintaining quality. This leads to slower development and more bugs over time. Automation helps reveal technical debt through continuous integration tests, code inspections, and trend analysis. As teams automate their build, deployment, and testing processes, they often discover previously unknown issues. Both direct testing and the learning from automation efforts help teams understand and address technical debt. Managing technical debt through automation provides benefits at both the team and enterprise levels.
Raquel Pau discusses strategies for managing technical debt. She defines technical debt as code that is easy to implement in the short run but not the best overall solution. While some technical debt is inevitable when pursuing a minimum viable product strategy, it is important to measure all debt, control increases with quality gates and code reviews, and prioritize reducing existing debt through a "merciless" cleanup approach. Different types of technical debt include architectural, testing, code standards, infrastructure, and knowledge debt. Metrics, consequences, and solutions are proposed for managing each type of debt.
The document discusses various aspects of software testing including:
- Verification is the process of confirming software meets its specifications through static testing techniques like reviews and inspections.
- Validation is the process of confirming software meets user requirements through dynamic testing techniques like unit, integration, and system testing.
- Testing occurs throughout the software development life cycle to reduce risks. White-box testing uses internal knowledge while black-box testing is done without internal knowledge.
- Validation activities include unit testing of individual components, integration testing, and various levels of high-level testing like function, system, and acceptance testing.
5WCSQ - Quality Improvement by the Real-Time Detection of the ProblemsTakanori Suzuki
1. The document discusses quality improvement in software development projects through real-time detection of problems. It describes current high failure rates in projects and how quantitative management can help.
2. It introduces the "Development ForeCast" approach which uses automated measurements, monitoring, and analysis of source code metrics to detect quality problems in real-time. This allows risks to be identified early.
3. Case studies show how static code analysis tools can evaluate quality at different stages of development, like identifying modules likely to have defects during testing. Real-time monitoring of metrics can improve quality while reducing costs.
Ben Walters - Creating Customer Value With Agile Testing - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Creating Customer Value With Agile Testing by Ben Walters. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
One of the biggest problems with code reviews is that they often derail developer productivity. Learn about the essentials of code reviews, where they are today, and where they can be using AI/ML technologies. With machine learning technology, code quality can be improved, and developers can focus on invention, rather than remediation.
The document is a presentation deck about technical debt that covers:
- What technical debt is and how it occurs through bad design decisions or quick development approaches that sacrifice quality
- How to identify technical debt through indicators like comments mentioning certain developers' code or difficulties with setup, deployment, or testing
- Sources of technical debt like time pressure, maintenance neglect, or using outdated libraries
- Why technical debt should be addressed to avoid issues like an uncontrollable codebase and development risks
- How to manage technical debt through practices like refactoring, continuous integration, and prioritizing technical debt in estimations
This document discusses quality assurance in an agile development environment. Some key points:
- In agile, quality is a team responsibility built into each sprint through practices like test-driven development and continuous integration. QA focuses on working software rather than documentation.
- Traditional QA tested after development, but agile QA works throughout development. Automated testing and continuous integration allow for faster feedback.
- The "definition of done" ensures quality standards are met before work is considered complete. This includes things like testing, documentation, and business verification of requirements.
- Metrics like burn-down charts are used to track progress and quality over iterations. Visualizing progress helps the team respond quickly to changes.
Continuous delivery requires more that DevOps. It also requires one to think differently about product design, development & testing, and the overall structure of the organization. This presentation will help you understand what it takes and why one would want to deliver value to your customers multiple times each day. #CIC
Jeff "Cheezy" Morgan Ardita Karaj
The document discusses continuous globalization and localization workflows. It describes Lingoport's suite of tools which provide continuous measurement, automation and visibility for internationalization and localization. The tools accommodate continuous change, measure localization issues, and integrate localization into every sprint and release. Lingoport representatives were available to answer questions.
This document provides an overview of key topics related to quality in software projects from a project manager's perspective. It discusses definitions of quality, different approaches to software development like agile and iterative development, design quality, code quality, security quality, and things project managers can do to focus on quality. Anti-patterns that should be avoided are also covered, such as tolerating long feedback cycles or isolating teams from end-users. The document aims to give project managers insights on how to produce good quality software.
Slides for Houston iPhone Developers' Meetup (April 2012)lqi
The document discusses the importance of code quality and provides tips for improving code quality. It defines code quality as how well software is designed and implemented. It recommends code reviews, static analysis tools like Clang, AppCode, and OCLint to identify code smells and defects. It also discusses refactoring code to improve simplicity, clarity and reduce technical debt. Maintaining high code quality makes software easier to change and evolve over time.
The document discusses various definitions and views of software quality. It defines quality as an effective software process that creates a useful product providing value to both producers and users. Quality is discussed from perspectives including performance, features, reliability, and conformance. Dimensions of quality proposed by Garvin and McCall's quality factors are summarized. The document also covers topics like the software quality dilemma, cost of quality, quality and risk, and achieving software quality through engineering methods, project management, and quality control/assurance.
Our top 10 Metrics reveal the most fundamental data points Agile methodology requires to work effectively, and will put you on the highly targeted path to successful implementation of your Agile processes.
In this presentation you will learn how Farm Credit Services of America/Frontier Farm Credit transformed their quality practices and tooling to bring visibility and consistency to Enterprise Quality, including: testing as a team approach, creating an automated test architecture, measuring progress with dashboards and standardizing on a set of testing tools.
These slides quickly illustrate how you can successfully adopt Agile to improve your development efforts. In addition to discussing how and why teams are interested in Agile, it covers some of the challenges of adopting it and suggestions for ensuring success.
This document discusses establishing code review processes for a team. It outlines the benefits of code reviews, including finding bugs earlier, increased maintainability, and coaching opportunities. It provides suggestions for an effective code review process, such as using checklists, keeping reviews small in scope, and measuring the results. While code reviews require commitment and can be challenging to implement, the document argues they are important for improving code quality and the team.
The document discusses quality assurance (QA) metrics in agile development. It begins by defining quality for both products and processes, noting that QA influence increases as development moves from requirements to validation. It then covers the types of metrics that can be used as a foundation for measuring product quality, including quantitative, qualitative, absolute, relative, and derivative metrics. Finally, it provides examples of QA metrics that can be used for daily monitoring of quality, as well as metrics that can be included in regular quality reports for sprints and releases.
The document discusses software quality and specification by example (SbE). It begins with defining quality and discussing why bugs occur. It then introduces SbE, describing how it can be used to collaboratively specify requirements through examples to derive automated tests and documentation. SbE benefits include improved communication, fewer bugs, and living documentation. The rest of the document provides examples of how to apply SbE, including through a simulation game, and discusses test scope and writing good automated acceptance tests.
Similar to Establishing Release Quality Levels and Release Acceptance Tests (20)
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
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.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
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.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
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.
19. www.conteneo.co
Example from VeriSign Managed Security Services
Release Level Description
Release Level 5 All functionality fully certified.
Near-zero probability of high severity errors and a low probability that medium severity errors.
Release Level 4 All new and modified functionality fully certified, except where risk is deemed minimal (e.g.
internal facing reports, low probability use cases).
Features not fully certified documented in the test plan and/or project charter. Strategic
regression testing of existing functionality performed.
Low probability that high severity errors will be identified in production. Project carries a
moderate probability that medium severity errors.
Release Level 3 All new and modified functionality at least partially certified.
Features not fully certified documented in the test plan and/or project charter.
Partial regression testing performed.
Moderate probability for high severity errors. Higher probability for medium severity errors.
Release Level 2 Most new and/or modified functionality partially certified.
Features not fully certified communicated to stakeholders.
Partial regression testing performed.
Higher probability that high and medium severity errors will be identified.
Release Level 1 New and/or modified features not certified by QA.
Regression testing may or may not occur.
Level 1 releases may be available only for demo or controlled access purposes.
High risk for high severity errors.
19