Start with Quality - an Agile Tester's Case StudyNick Zdunić
A presentation given at MTUG 2016. The recording is available on the Code Genesys website as well http://www.codegenesys.com/start-with-quality/
Some inspiration from Henrik Knibergs presentation. Just so happens we didn't know of this until we had implemented it. It was so similar. We give credit to his material in the slide deck as well.
QCP - How to reduce your quality control Budget while keeping your risks low?Quality Control Partners
This document provides tips for reducing quality control costs while importing from China. It suggests requiring inspectors to check only critical specifications, giving more flexibility to best suppliers by reducing inspection severity or skipping random lots, closely managing worst suppliers by checking production early, and developing suppliers by providing training and process advice. Working with more rigorously selected suppliers is also recommended.
Over the past couple of years we've migrated from a traditional, waterfall development process to more of an iterative one. At the same time we've moved from structured to object oriented programming languages. These are big transitions and we are proud to say that we've released our first .NET product built on an object oriented framework.
We have recently adopted the Lean Start-up Process first introduced by Eric Ries. This is a presentation I gave at our customer advisory board meeting that was adapted from Eric's presentation found here:
http://www.slideshare.net/startuplessonslearned/eric-ries-lean-startup-presentation-for-web-20-expo-april-1-2009-a-disciplined-approach-to-imagining-designing-and-building-new-products
Find us at http://exumatech.com or @ExumaTech
1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important.
2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews.
3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.
The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.
This document discusses why checklists are better than test cases for documentation in quality assurance. It argues that test cases become overcrowded and focus too much on documentation rather than core functions. Checklists are more time-saving and easy to update. An example compares a test case to a checklist for login/registration flows. The author's company Hipo uses a test pad and robot framework integrated with checklists to share with clients and team members.
This document discusses the debate around software testing - whether or not it is worthwhile for companies, especially startups, to implement testing practices. It acknowledges both benefits of testing like improved quality and reduced bugs, as well as challenges like increased time and costs. The document provides examples of how to effectively sell the value of testing to customers and overcome objections. It emphasizes that testing leads to more maintainable code and helps avoid technical debt.
Start with Quality - an Agile Tester's Case StudyNick Zdunić
A presentation given at MTUG 2016. The recording is available on the Code Genesys website as well http://www.codegenesys.com/start-with-quality/
Some inspiration from Henrik Knibergs presentation. Just so happens we didn't know of this until we had implemented it. It was so similar. We give credit to his material in the slide deck as well.
QCP - How to reduce your quality control Budget while keeping your risks low?Quality Control Partners
This document provides tips for reducing quality control costs while importing from China. It suggests requiring inspectors to check only critical specifications, giving more flexibility to best suppliers by reducing inspection severity or skipping random lots, closely managing worst suppliers by checking production early, and developing suppliers by providing training and process advice. Working with more rigorously selected suppliers is also recommended.
Over the past couple of years we've migrated from a traditional, waterfall development process to more of an iterative one. At the same time we've moved from structured to object oriented programming languages. These are big transitions and we are proud to say that we've released our first .NET product built on an object oriented framework.
We have recently adopted the Lean Start-up Process first introduced by Eric Ries. This is a presentation I gave at our customer advisory board meeting that was adapted from Eric's presentation found here:
http://www.slideshare.net/startuplessonslearned/eric-ries-lean-startup-presentation-for-web-20-expo-april-1-2009-a-disciplined-approach-to-imagining-designing-and-building-new-products
Find us at http://exumatech.com or @ExumaTech
1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important.
2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews.
3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.
The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.
This document discusses why checklists are better than test cases for documentation in quality assurance. It argues that test cases become overcrowded and focus too much on documentation rather than core functions. Checklists are more time-saving and easy to update. An example compares a test case to a checklist for login/registration flows. The author's company Hipo uses a test pad and robot framework integrated with checklists to share with clients and team members.
This document discusses the debate around software testing - whether or not it is worthwhile for companies, especially startups, to implement testing practices. It acknowledges both benefits of testing like improved quality and reduced bugs, as well as challenges like increased time and costs. The document provides examples of how to effectively sell the value of testing to customers and overcome objections. It emphasizes that testing leads to more maintainable code and helps avoid technical debt.
by Alan Taylor (Innodev)
Test Driven Development is an engineering concept with practices that has great benefit to business. For example, if your business wants to have idealised and revered products, you will have:
- an ability to deliver high quality products which keep up with the latest customer wishes;
- products which are constantly updated with the latest cool features; and
- ability to very quickly resolve any issues that do occur – and they do for even the best organisation
We will share with you why Test Driven Development is a pivotal tool in the fight to be one of those inspiring organisations. We will cover the practices at a high level and go into the outcomes of those practices. We will include not only how the business should benefit directly from them, but also how they provide indirect benefits for the team and the organisation. Every positive has some negatives, whether they are perceived or actual, long term or short term). We will touch on how they are like any form of exercise – they will be hard work at times, but afterwards the results will include fitter, stronger and faster teams able to delivery consistently better results.
As a manager or leader, you will be able to walk away with insight that will enable you to determine how TDD is worth following up in your domain.
As someone within the delivery team, you will leave with deeper understanding of how you, your team and your company can effectively benefit from Test Driven Development.
The document argues that the term "quality assurance" (QA) no longer accurately describes the role of testers in an Agile development process. QA implies monitoring and assuring quality from the outside, whereas testers are part of the development team. "Quality assistance" is also problematic as it implies assisting others rather than creating value. The document proposes using "quality intelligence" instead, which better captures how testers acquire and transform product data into useful information for stakeholders. Adopting this new term would help testing roles fully transition to an Agile paradigm.
This document discusses agile testing and its principles. It defines agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. The key principles of agile testing are that individuals and interactions are valued over processes, working software is valued over documentation, and responding to change is valued over following a plan. It also discusses specific agile development methodologies like extreme programming and the role of testing in agile projects.
In this webinar, Hans goes through a number of solutions a team can do to diminish this problem, and what actions to take when it happens. Hans discussed the following solutions on how one can apply better test design to drive better automation, a number of technical strategies, what developers and product owners can do to help, and how to handle the testing and automation work that is still left after a sprint has finished. A key item in handling the test automation work that is left over is that QA’s need to own the testing from the beginning, and should not get stuck in the work of previous sprints, since that will inhibit good cooperation with other team members, making matters worse.
Key Takeaways:
- Get more tests created and automated.
- Make automation manageable and maintainable.
- Keep the QA people in sync with their fellow team members.
View webinar recording - https://testhuddle.com/resource/how-to-get-automated-testing-done/
This document summarizes the key points from a seminar on quality and productivity. It discusses the customer mission of delivering excellent quality products on time and on budget. It outlines Next's expectations for suppliers to meet customer expectations. It also discusses challenges like price pressures and how improvements can be made through techniques like lean manufacturing, reducing waste, and improving internal processes and training.
This document discusses quality and its importance for productivity. It defines quality as meeting customer requirements and doing things right the first time. It states that quality is everyone's responsibility, not just the quality department. Poor quality practices include lack of clear instructions, departments working in silos, and a "not my problem" attitude. The document recommends preventing defects through design for manufacturability and addressing root causes. It outlines various quality management approaches and tools like quality circles, zero defects, total quality management, six sigma, fishbone diagrams, and the DMAIC process. Finally, it lists benefits of quality like strengthened competitiveness and higher profitability.
Maelscrum / Business Story Manager OverviewPaul Gerrard
The document provides an overview of the Business Story Method, Story Platform, and Maelscrum tool. It describes how the method is used for requirements analysis, planning, execution and reporting. The Story Platform brings together the Business Story Manager and Maelscrum tools to support the method. Maelscrum allows users to create requirements, stories, scenarios, processes and link them to enable traceability and testing.
Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...Codemotion
Performance tests are not only an important instrument for understanding a system and its runtime environment. It is also essential in order to check stability and scalability – non-functional requirements that might be decisive for success. But won't my cloud hosting service scale for me as long as I can afford it? Yes, but… It only operates and scales resources. It won't automatically make your system fast, stable and scalable. This talk shows how such and comparable questions can be clarified with performance tests and how DevOps teams benefit from regular test practise.
This talk sets out the thinking behind the Gerrard Consulting Business Story Method. The slides present background, an overview of the method and introduces the Testela Business tool that supports Gerrard Consulting services.
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019Codemotion
What is the job of a CTO and how does it change as a startup grows in size and scale? As a CTO, where should you spend your focus? As an engineer aspiring to be a CTO, what skills should you pursue? In this inspiring and personal talk, I describe my journey from early Red Hat engineer to CTO at Bloomon. I will share my view on what it means to be a CTO, and ultimately answer the question: Should the CTO be coding?
MHA2018 - Quality Advocacy: The next progression for Agile Testers - Don PetersAgileDenver
"As we strive as an industry to deliver value more quickly, we need to adapt our testing practices to keep up.
As Quality Advocates, we can’t sit back and wait for work to show up in our queue. We can provide the most value if we bring our testing skills and mindset to all of the activities our team performs. I’ll discuss the attributes of a Quality Advocate and how we can influence culture, planning, and test automation strategy to help our teams deliver value and delight customers."
Analysis Prioritisation Communication-Day SevenReuben Ray
This document provides information on quality processes and process improvement strategies. It discusses concepts like the planning process with inputs like vision and gap analysis, prioritization using Kano analysis, and monitoring. Other sections cover quality definitions and strategies for competitive advantage like cost leadership, differentiation, and customer orientation. Process improvement frameworks like Lean, Six Sigma, TQM and BPR are mentioned. The document also includes information on benchmarking, value creation, implementation, and team mandates for process improvement projects.
Pushing the Bottleneck: Predicting and Addressing the Next, Next ThingIBM UrbanCode Products
Finding bottlenecks in our software delivery processes is often pretty easy. But once we squash one bottleneck, another team becomes the limiting factor. This presentation looks how bottlenecks work, and how to predict the next bottleneck you'll need to work on.
Typical software testers focus on learning ‘Hard’ skills associated with the responsibilities of their role. However, these skills allow them to become a "Dependable" or "Knowledgeable" tester, rather than a "Great" tester. What are the skills necessary to take you to the next level within your ladder of testing career, to become someone known as "Great" tester? This presentation will identify some of the key skills that can take you to the next level and provides an easy-to-follow roadmap on mastering those skills.
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.
The document discusses how test axioms can be used to advance testing practices. It introduces 16 proposed test axioms grouped into stakeholder, design, and delivery axioms. The axioms represent critical thinking processes for testing any system. The document discusses how the axioms can help testers design test strategies, assess improvement opportunities, and define needed skills. It also proposes a "first equation of testing" that separates axioms, context, values, and thinking to allow for different valid approaches. Additionally, the concept of "quantum testing" is introduced to discuss assigning significance to tests rather than defining their value, which can only be determined by stakeholders.
The document discusses 10 signs that an organization's software testing may not be enough. These include having excessive production bugs, bugs found during user acceptance testing, growing bug counts over test cycles, not investing in testing compared to competitors, lacking clear criteria for what constitutes "enough" testing, testers advising against releasing software, weak prevention efforts like code reviews, lack of developer unit testing, frequently reduced testing periods causing deadline problems, and high tester turnover. The document advocates treating testing as risk management, increasing test reuse and automation, and addresses common challenges and questions around software testing.
Ruud Teunissen - Test Process Improvement on a Shoestring TEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Test Process Improvement on a Shoestring by Ruud Teunissen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
- The speaker proposes 16 "test axioms" that are intended to provide a framework for testing approaches and represent principles that are context-insensitive and self-evidently true.
- The axioms are grouped into three categories: stakeholders, design, and delivery. The speaker argues the axioms can help testers think critically about testing and identify flaws in arguments.
- It is argued that process improvement models are not effective for improving testing because there is no consensus on best practices and processes must be tailored to context. True improvement requires understanding why current approaches are used given the context.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
Test & measurement; importance of test and measurement in electronics; measur...SHIV DUTT
This document discusses the importance of test and measurement in product development. It explains that testing saves companies from heavy losses by identifying issues early. Testing provides confidence in the design, allows for corrections, and reduces risks. The document also discusses reliability and validity, noting that reliable tests produce consistent results and valid tests accurately measure the intended characteristic. It provides tips for ensuring reliable and valid measurement, such as carefully analyzing performance, taking multiple measurements, and keeping specifications tight during pre-production. Testing is necessary to identify defects, ensure design correctness, and establish reliability. Industries must focus on testing their products rather than just outward finishing.
by Alan Taylor (Innodev)
Test Driven Development is an engineering concept with practices that has great benefit to business. For example, if your business wants to have idealised and revered products, you will have:
- an ability to deliver high quality products which keep up with the latest customer wishes;
- products which are constantly updated with the latest cool features; and
- ability to very quickly resolve any issues that do occur – and they do for even the best organisation
We will share with you why Test Driven Development is a pivotal tool in the fight to be one of those inspiring organisations. We will cover the practices at a high level and go into the outcomes of those practices. We will include not only how the business should benefit directly from them, but also how they provide indirect benefits for the team and the organisation. Every positive has some negatives, whether they are perceived or actual, long term or short term). We will touch on how they are like any form of exercise – they will be hard work at times, but afterwards the results will include fitter, stronger and faster teams able to delivery consistently better results.
As a manager or leader, you will be able to walk away with insight that will enable you to determine how TDD is worth following up in your domain.
As someone within the delivery team, you will leave with deeper understanding of how you, your team and your company can effectively benefit from Test Driven Development.
The document argues that the term "quality assurance" (QA) no longer accurately describes the role of testers in an Agile development process. QA implies monitoring and assuring quality from the outside, whereas testers are part of the development team. "Quality assistance" is also problematic as it implies assisting others rather than creating value. The document proposes using "quality intelligence" instead, which better captures how testers acquire and transform product data into useful information for stakeholders. Adopting this new term would help testing roles fully transition to an Agile paradigm.
This document discusses agile testing and its principles. It defines agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. The key principles of agile testing are that individuals and interactions are valued over processes, working software is valued over documentation, and responding to change is valued over following a plan. It also discusses specific agile development methodologies like extreme programming and the role of testing in agile projects.
In this webinar, Hans goes through a number of solutions a team can do to diminish this problem, and what actions to take when it happens. Hans discussed the following solutions on how one can apply better test design to drive better automation, a number of technical strategies, what developers and product owners can do to help, and how to handle the testing and automation work that is still left after a sprint has finished. A key item in handling the test automation work that is left over is that QA’s need to own the testing from the beginning, and should not get stuck in the work of previous sprints, since that will inhibit good cooperation with other team members, making matters worse.
Key Takeaways:
- Get more tests created and automated.
- Make automation manageable and maintainable.
- Keep the QA people in sync with their fellow team members.
View webinar recording - https://testhuddle.com/resource/how-to-get-automated-testing-done/
This document summarizes the key points from a seminar on quality and productivity. It discusses the customer mission of delivering excellent quality products on time and on budget. It outlines Next's expectations for suppliers to meet customer expectations. It also discusses challenges like price pressures and how improvements can be made through techniques like lean manufacturing, reducing waste, and improving internal processes and training.
This document discusses quality and its importance for productivity. It defines quality as meeting customer requirements and doing things right the first time. It states that quality is everyone's responsibility, not just the quality department. Poor quality practices include lack of clear instructions, departments working in silos, and a "not my problem" attitude. The document recommends preventing defects through design for manufacturability and addressing root causes. It outlines various quality management approaches and tools like quality circles, zero defects, total quality management, six sigma, fishbone diagrams, and the DMAIC process. Finally, it lists benefits of quality like strengthened competitiveness and higher profitability.
Maelscrum / Business Story Manager OverviewPaul Gerrard
The document provides an overview of the Business Story Method, Story Platform, and Maelscrum tool. It describes how the method is used for requirements analysis, planning, execution and reporting. The Story Platform brings together the Business Story Manager and Maelscrum tools to support the method. Maelscrum allows users to create requirements, stories, scenarios, processes and link them to enable traceability and testing.
Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...Codemotion
Performance tests are not only an important instrument for understanding a system and its runtime environment. It is also essential in order to check stability and scalability – non-functional requirements that might be decisive for success. But won't my cloud hosting service scale for me as long as I can afford it? Yes, but… It only operates and scales resources. It won't automatically make your system fast, stable and scalable. This talk shows how such and comparable questions can be clarified with performance tests and how DevOps teams benefit from regular test practise.
This talk sets out the thinking behind the Gerrard Consulting Business Story Method. The slides present background, an overview of the method and introduces the Testela Business tool that supports Gerrard Consulting services.
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019Codemotion
What is the job of a CTO and how does it change as a startup grows in size and scale? As a CTO, where should you spend your focus? As an engineer aspiring to be a CTO, what skills should you pursue? In this inspiring and personal talk, I describe my journey from early Red Hat engineer to CTO at Bloomon. I will share my view on what it means to be a CTO, and ultimately answer the question: Should the CTO be coding?
MHA2018 - Quality Advocacy: The next progression for Agile Testers - Don PetersAgileDenver
"As we strive as an industry to deliver value more quickly, we need to adapt our testing practices to keep up.
As Quality Advocates, we can’t sit back and wait for work to show up in our queue. We can provide the most value if we bring our testing skills and mindset to all of the activities our team performs. I’ll discuss the attributes of a Quality Advocate and how we can influence culture, planning, and test automation strategy to help our teams deliver value and delight customers."
Analysis Prioritisation Communication-Day SevenReuben Ray
This document provides information on quality processes and process improvement strategies. It discusses concepts like the planning process with inputs like vision and gap analysis, prioritization using Kano analysis, and monitoring. Other sections cover quality definitions and strategies for competitive advantage like cost leadership, differentiation, and customer orientation. Process improvement frameworks like Lean, Six Sigma, TQM and BPR are mentioned. The document also includes information on benchmarking, value creation, implementation, and team mandates for process improvement projects.
Pushing the Bottleneck: Predicting and Addressing the Next, Next ThingIBM UrbanCode Products
Finding bottlenecks in our software delivery processes is often pretty easy. But once we squash one bottleneck, another team becomes the limiting factor. This presentation looks how bottlenecks work, and how to predict the next bottleneck you'll need to work on.
Typical software testers focus on learning ‘Hard’ skills associated with the responsibilities of their role. However, these skills allow them to become a "Dependable" or "Knowledgeable" tester, rather than a "Great" tester. What are the skills necessary to take you to the next level within your ladder of testing career, to become someone known as "Great" tester? This presentation will identify some of the key skills that can take you to the next level and provides an easy-to-follow roadmap on mastering those skills.
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.
The document discusses how test axioms can be used to advance testing practices. It introduces 16 proposed test axioms grouped into stakeholder, design, and delivery axioms. The axioms represent critical thinking processes for testing any system. The document discusses how the axioms can help testers design test strategies, assess improvement opportunities, and define needed skills. It also proposes a "first equation of testing" that separates axioms, context, values, and thinking to allow for different valid approaches. Additionally, the concept of "quantum testing" is introduced to discuss assigning significance to tests rather than defining their value, which can only be determined by stakeholders.
The document discusses 10 signs that an organization's software testing may not be enough. These include having excessive production bugs, bugs found during user acceptance testing, growing bug counts over test cycles, not investing in testing compared to competitors, lacking clear criteria for what constitutes "enough" testing, testers advising against releasing software, weak prevention efforts like code reviews, lack of developer unit testing, frequently reduced testing periods causing deadline problems, and high tester turnover. The document advocates treating testing as risk management, increasing test reuse and automation, and addresses common challenges and questions around software testing.
Ruud Teunissen - Test Process Improvement on a Shoestring TEST Huddle
EuroSTAR Software Testing Conference 2009 presentation on Test Process Improvement on a Shoestring by Ruud Teunissen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
- The speaker proposes 16 "test axioms" that are intended to provide a framework for testing approaches and represent principles that are context-insensitive and self-evidently true.
- The axioms are grouped into three categories: stakeholders, design, and delivery. The speaker argues the axioms can help testers think critically about testing and identify flaws in arguments.
- It is argued that process improvement models are not effective for improving testing because there is no consensus on best practices and processes must be tailored to context. True improvement requires understanding why current approaches are used given the context.
Growing a Company Test Community: Roles and Paths for TestersTEST Huddle
Over the past three years, our company’s test team has grown from three lonesome testers to a community of nine – with more planned. Since we don’t see testers as “click monkeys”, but as valuable and integrated project members who bring a specific skill set to the table, it’s important for us to choose testers well and to train them in various areas so that they can contribute, grow and see their own career path within testing.
To structure to our internal tester training program, we have been developing role descriptions, education paths and career options for our testers, which I’d like to share with you in this webinar.
View webinar - https://huddle.eurostarsoftwaretesting.com/resource/webinar/growing-company-test-community-roles-paths-testers/
Test & measurement; importance of test and measurement in electronics; measur...SHIV DUTT
This document discusses the importance of test and measurement in product development. It explains that testing saves companies from heavy losses by identifying issues early. Testing provides confidence in the design, allows for corrections, and reduces risks. The document also discusses reliability and validity, noting that reliable tests produce consistent results and valid tests accurately measure the intended characteristic. It provides tips for ensuring reliable and valid measurement, such as carefully analyzing performance, taking multiple measurements, and keeping specifications tight during pre-production. Testing is necessary to identify defects, ensure design correctness, and establish reliability. Industries must focus on testing their products rather than just outward finishing.
This document discusses the concepts of quality, quality systems, and their importance for businesses. It explains that quality can be measured both tangibly, through factors like reliability and durability, and intangibly, through a brand's reputation. Total Quality Management and Kaizen approaches aim to build quality into production processes and continuously improve quality through small changes. Quality standards like ISO 9001, BS5750, and CE marking indicate that a business has systems to ensure a consistent level of quality, though they do not guarantee high quality itself. Managing quality systems involves costs but can provide benefits like increased sales, reputation, and price through a good quality reputation.
This document provides an introduction to quality concepts, including ISO 9001 standards, processes, quality control, quality assurance, and total quality management. It discusses how focusing on quality can help businesses stay operational by exceeding customer expectations and maintaining continuous improvement. Key aspects that help ensure quality like process control and Deming's management obligations are also summarized. The document emphasizes that quality must be a priority from the planning stage and should engage all employees to best serve customers.
Quality Control is the key for any business growth. The Entrepreneur should focus on Quality control in order to increase the user experience of the product/services.
The document provides an overview of quality concepts including definitions of quality, quality control, dimensions of quality, and the evolution of quality approaches. It discusses concepts like total quality management, Deming's 14 points, Kaizen technique, quality by design, and product development cycles. The key aspects covered are definitions of quality, importance of meeting customer expectations, involvement of all aspects of a firm in quality, and designing quality into products through evaluating prototypes and design changes.
The document describes the services provided by AQSS (Pty) Ltd, an independent quality sorting and inspection company. Their mission is to provide affordable, high-quality sorting and inspection services to automotive customers. Key services include sorting, inspection, containment certification, launch support, and quality assistance. Using AQSS ensures defective products are prevented from reaching customers while maintaining production goals.
In the software industry you'll often hear the words Testing, Quality Assurance [QA] and Quality Control [QC] used interchangeably and very frequently. While it is usually enough to get your point across with a developer, it is certainly helpful to know more about how these apply to the world of software testing. So, what exactly the difference between QC and QA and how can you get from one destination to another? This presentation attempts to shed some light on this and will be taking you through various QA best practices and how we can collectively build and grow the next breed of intelligent QA Engineers
Learn how to establish a greater sense of confidence in your release cycle, along with the practices and processes to create a high-performing engineering culture within your team.
This document provides an overview of quality management and control. It discusses specifying quality, quality control processes like inspection and testing, reliability, and total quality management. Key points covered include defining quality and managing it through various stages of production. Quality is ensured through methods like inspection of raw materials, work in progress, and finished goods. Total quality management aims for continuous improvement through planning, controlling, and improving quality. Quality circles involve workers identifying and solving quality problems.
This document provides an overview of quality concepts including definitions of quality, zero defects, customers, quality terms and concepts, inspection, sampling, and the differences between SPC and acceptance sampling. It defines quality as meeting customer expectations and conforming to specifications. Zero defects aims for no product or service defects. Customers are critical to quality and satisfaction. Total quality management, continuous improvement, six sigma, and PDCA model are quality approaches. Inspection and sampling are used to check for defects. SPC monitors processes while acceptance sampling accepts or rejects lots.
This document discusses quality and testing. It begins by asking if 99% defect-free is sufficient, then gives examples of issues with a 1% defect rate. It defines quality as meeting or exceeding customer expectations. Quality assurance involves preventing defects through testing, reviews, and other methods. Testing works with quality assurance to find defects for the customer. Without quality, there are costs from rework, lost customers, and more. Quality must be built in from the start through goals, planning, and continuous improvement. Individuals have a role to play through involvement, improvement, and customer satisfaction using a Plan-Do-Check-Act approach.
This document provides an overview of Total Quality Management (TQM) concepts including definitions of quality, inspection, quality control, quality assurance, and quality management. It discusses quality gurus like Deming, Juran, Crosby, and Taguchi and some of their key philosophies and tools. Specifically, it covers Deming's PDCA cycle and 14 points, Juran's quality trilogy, Crosby's 14 points and concept of "quality is free", and Taguchi's concept of customer tolerance limits and quality loss function which quantifies costs of poor quality over the lifetime of a product.
QA and test departments often are composed of employees with business backgrounds who have little training when it comes to software testing. Though they are engaged, these team members can get overwhelmed by the thousands of test cases they have to execute over and over, and they don’t see a future career path in testing. What can be done to address these challenges? Join Sophie Benjamin as she presents her personal step-by-step recipe to transform QA and test teams and position them for success within IT. She talks about the essential roles in QA and test teams, their skills and contributions within the software delivery cycle, and tips and tricks to keep employees motivated and willing to invest in their careers. Attendees will leave with practical advice on what leaders and managers can do to ensure that their QA and test teams deliver results and add value to their organizations, today and in the future.
Role of qa&qc in manufacturing presentationImran Jamil
This document discusses quality control, quality assurance, and quality improvement concepts. It provides examples of quality control and quality assurance activities in manufacturing, such as inspections, audits, and process documentation. Quality control focuses on inspection and testing to find defects, while quality assurance aims to prevent defects by improving processes. Quality improvement is about continuously studying processes to identify and implement solutions to problems. The goal is to create systems that prevent errors from occurring.
Quality Management and Statistical Process ControlMahmudul Hasan
This document discusses quality management concepts including the meaning of quality, quality assurance vs quality control, process control, and statistical process control. It defines quality as meeting customer expectations and fitness for use. Quality assurance focuses on implementing processes while quality control checks output. Process control monitors a process to ensure it behaves as expected. Statistical process control uses tools like control charts to reduce variability and identify sources of variation. The document reviews various quality measurement and process analysis tools.
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdfBaha Majid
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
React.js, a JavaScript library developed by Facebook, has gained immense popularity for building user interfaces, especially for single-page applications. Over the years, React has evolved and expanded its capabilities, becoming a preferred choice for mobile app development. This article will explore why React.js is an excellent choice for the Best Mobile App development company in Noida.
Visit Us For Information: https://www.linkedin.com/pulse/what-makes-reactjs-stand-out-mobile-app-development-rajesh-rai-pihvf/
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...Luigi Fugaro
Vector databases are transforming how we handle data, allowing us to search through text, images, and audio by converting them into vectors. Today, we'll dive into the basics of this exciting technology and discuss its potential to revolutionize our next-generation AI applications. We'll examine typical uses for these databases and the essential tools
developers need. Plus, we'll zoom in on the advanced capabilities of vector search and semantic caching in Java, showcasing these through a live demo with Redis libraries. Get ready to see how these powerful tools can change the game!
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
The Rising Future of CPaaS in the Middle East 2024Yara Milbes
Explore "The Rising Future of CPaaS in the Middle East in 2024" with this comprehensive PPT presentation. Discover how Communication Platforms as a Service (CPaaS) is transforming communication across various sectors in the Middle East.
DECODING JAVA THREAD DUMPS: MASTER THE ART OF ANALYSISTier1 app
Are you ready to unlock the secrets hidden within Java thread dumps? Join us for a hands-on session where we'll delve into effective troubleshooting patterns to swiftly identify the root causes of production problems. Discover the right tools, techniques, and best practices while exploring *real-world case studies of major outages* in Fortune 500 enterprises. Engage in interactive lab exercises where you'll have the opportunity to troubleshoot thread dumps and uncover performance issues firsthand. Join us and become a master of Java thread dump analysis!
Malibou Pitch Deck For Its €3M Seed Roundsjcobrien
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
Orca: Nocode Graphical Editor for Container OrchestrationPedro J. Molina
Tool demo on CEDI/SISTEDES/JISBD2024 at A Coruña, Spain. 2024.06.18
"Orca: Nocode Graphical Editor for Container Orchestration"
by Pedro J. Molina PhD. from Metadev
Liberarsi dai framework con i Web Component.pptxMassimo Artizzu
In Italian
Presentazione sulle feature e l'utilizzo dei Web Component nell sviluppo di pagine e applicazioni web. Racconto delle ragioni storiche dell'avvento dei Web Component. Evidenziazione dei vantaggi e delle sfide poste, indicazione delle best practices, con particolare accento sulla possibilità di usare web component per facilitare la migrazione delle proprie applicazioni verso nuovi stack tecnologici.
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...kalichargn70th171
In today's fiercely competitive mobile app market, the role of the QA team is pivotal for continuous improvement and sustained success. Effective testing strategies are essential to navigate the challenges confidently and precisely. Ensuring the perfection of mobile apps before they reach end-users requires thoughtful decisions in the testing plan.
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...
Is test automation really the solution to your quality problem
1. Reuben Korngold May 2018
Is test automation really the solution to
your quality problem?
2. Commercial in Confidence
1. Are you automating to save time/money or improve
quality?
2. Have you over-promised automation benefits?
3. Are you trying to check or test?
4. Can you replicate a human? Are there humans left to
think about quality?
5. With convenience of automation:
a) Are your tests telling you the truth?
b) Are the same checks passing every time providing confidence of
quality?
c) How will you address quality fade?
Big Test Automation Questions.
5. Commercial in Confidence
Standing on the shoulders of our quality veterans
W Edwards Deming
1900-1993
“… is accomplished by
better management of
design, engineering,
testing and by
improvement of
processes”.
”The customer’s
definition of quality is
the only one that
matters”
Phil Crosby
1926-2001
“Has to be the
fabric of the
organisation, not
part of the fabric”.
“Has to be caused,
not controlled”
Peter Drucker
1909-2005
“… is not what the
supplier puts in. It is
what the customer
gets out and is willing
to pay for. Customers
pay only for what is
of use to them and
gives them value.
Nothing else
constitutes quality” Joseph Duran
1904-2008
“Fitness for use.
Fitness is defined
by the customer”
Robert Pirsig
1928-2017
“… is like modern art.
We may not be able
to define great
modern art; but we
frequently recognise
it when we see it.”
6. Commercial in Confidence
How ISO and PMBOK define quality.
“The degree to which a set of
inherent characteristics fulfills
requirements.”
7. Commercial in Confidence
PMBOK, 5th Edition
PMBOK: Project Quality Management
Quality management has 2 goals:
1. Ensuring a quality end-product.
2. Ensuring that all of the processes
involved during the project
lifecycle are carried out efficiently.
By managing quality, project
managers can ensure a successful
project and increased customer
satisfaction.
9. Commercial in Confidence
Are you working in QA?
• Quality Assurance is the process for managing
quality.
• Processes are put in place to ensure the correct
steps are done in the correct way.
• If the correct processes are in place there is
greater confidence that the actual results will
turn out as expected
• Quality Control is checking or detecting the
output for quality, also known as “testing”
13. Commercial in Confidence
Quality conformance: The Customer
I want a car that:
1. Has 4 wheels
2. Has working brake lights
3. Has air conditioning
Also, I do not want it to rob the engine of power
15. Commercial in Confidence
Delivering to specification = quality?
4 Wheels
Air
Conditioning
Working brake
lights
Air Con Power
Source
Doesn’t rob engine of
power!
You didn’t specifically
tell me “no dents”
17. Commercial in Confidence
Performance (Does it meet my core need)
Features (Anything additionally appealing)
Reliability (Will not fail over a time period)
Conformance (Precision to meet standards)
Durability (Lifespan)
Serviceability (Speed to repair)
Aesthetics (Personal preferences)
Perceived Quality (Indirect measures)
Dimensions of quality.
Garvin, Harvard Business School
18. Commercial in Confidence
Induction: Absence of evidence vs evidence of absence
1. How do you know that you covered what you needed to?
2. Zero defects detected = bug free?
3. Do you think you can now predict quality issues?
Getting philosophical about quality
SEXTUS EMPERICUS,
c. 200AD:
A universal rule could not
be established from an
incomplete set of
particular instances
DAVID HUME,
c. 1700’s
1. You cannot generalise
based on limited
observations
2. Sequences of events
from the past cannot
predict the future
19. Commercial in Confidence
Checking or testing?
Checking
• Unambiguous binary result against specification
• Compares an output to an expected output
• Can be performed by machines as the result is
self-decidable
• Finds presence of defects
Testing
• Gain an understanding about the fitness for purpose
of the product
• Combines checking with an observation to either an
implicit or explicit expected result
• Performed through exploration, discovery, and
learning
• Humans evaluate results
• Raises questions of use cases, usability and richer
defects not mechanically detected
22. Commercial in Confidence
We can no longer only optimise for efficiency in the 21st century
http://www.afr.com/leadership/atlassian-cofounder-scott-farquhar-challenges-business-focus-on-efficiency-20180409-h0yju7
“…eliminating variables and optimising
output rates worked for factory workers
in the 19th century but made little sense
now.”
We must adapt to, and plan for change.
24. Commercial in Confidence
Get local contractors to manually test
Do the same thing cheaper offshore using
labour arbitrage and tick-boxes
If we can describe what to do in enough
detail that someone halfway around the
world can do it, why not just automate it?
WHY
doesn't testing
fix quality?
Evolution of the testing industry
25. Commercial in Confidence
So why automate?
• Because technology is fun and we love
tinkering with the latest tools
• Increases motivation and optimism
• Operational efficiency for checking
• Consistency
• Stable metrics (e.g. tests per hour)
• Auditability
• Speed to deliver
• Cost
• Liberate test analysts to be analysts not
“checkers” or get rid of testers altogether
• Because we believe that consistent and robotic
checking is the solution to quality
28. Commercial in Confidence
• A test suite using record and playback broke the
next release (recommended approach only for
short term contractors)
• Limited validations meant test automation suite
completed
• The Test Automator went on holidays and
nobody else could use it
• Automated tests were later found to exercise
only 5 of 200 web services, team believed
coverage was high
• Maintenance of a test suite exceeded the manual
execution time each release
• Lots of defects found but it was the script that
was faulty not the software
Horror stories.
29. Commercial in Confidence
• Able to complete a 15 person days testing overnight,
freeing up testing team to be analysts, not executors
• Expanding test coverage beyond what humans could
possibly achieve
• Repetitious data creation
• Identification of variations using screen diffs that
human testers had not detected
• API level tests quickly implemented that had high ROI
being fast, efficient, and stable
• Automation implemented in build process, fast
feedback identified variances soon after check-in
Development is additive.
Automation can be a labour saviour.
30. Commercial in Confidence
• Start with the idea, end with the customer
• Employ quality methods and measures across the lifecycle
• Plan for quality, and follow through with the plan
• Use Humans who understand the context
• Always involve and listen to your customers, as they are the
ultimate measure of quality
• Do perform Quality Control (checking) to confirm delivery
• As close to source of creation as possible
• Automate repetition & breadth
• Align verification to business goals and risks
• Remember that checking (alone) is not quality - really test: explore, discover, and learn
How to really assure quality.
31. Is test automation really the solution
to your quality problem?
Yes
No
Maybe
Dude, are you serious?
32. Commercial in Confidence
Lets ask our some of our friends….
RANDOM TECH
GUY:
It can do more
consistent and
thorough checking,
early and regularly.
CROSBY: If this creates
a culture of quality in
the fabric of the
organization then it
can play a part.
ADVOCATE: Employ
checks early. Don’t spoil
the product’s potential
by waiting until its
packaged before
thinking about quality.
CUSTOMER: Doing your
same checks only faster
won’t make me happy.
Maybe you could get me
involved so you deliver
what I wanted?
JURAN: Dude, fitness
is measured by the
customer. Involve the
customer, already!
DRUCKER:
What’s the customer
going to get out of it?
DEMING: Sounds like better
management of design,
engineering and testing. Do it.
But don’t forget the customer.
PIRSIG: Quality is like modern art, you know it
when you see it. Test automation is a cool
modern art but only one appreciated by techno
boffins not customers.
Hands up who has used test automation before? Can anyone offer a definition of quality?
Phil Crosby – businessman and author of QM practices. Involved in Zero Defects program
Peter Drucker – management consultant and author and business guru
Joseph Duran – engineer and management consultant and author. Evangelist for quality management
Robert Pirsig – philosopher and author – Zen and the art of motorcycle maintenance: an inquiry into values
W Edwards Deming – American engineer, author, management consultant. Brought quality to Japan under behest of General MacArthur and then brought it back to USA to become more competitive starting with Ford in 1981
$2.8 billion is similar to the GDP of East Timor (World Bank 2017)
$1.8 billion is the cost of the new Sunshine Coast University Hospital, which the IT overspend would have paid for a good portion of it
Hands up how many people have been involved in the reactive process is the last 2 years?