This document proposes renovating and innovating testing approaches. It suggests renovating risk-based testing by collating current variants, using a context-driven mix of principles, considering value as well as risk, and integrating risk into a Value Flow Scorecard framework. It suggests innovating testing by considering evolution in nature as a model, how "memes" evolve ideas in a field, and allowing emergence between excess order and chaos. The document advocates an approach called Value-Inspired Testing to manage risks and value throughout the software development lifecycle.
The document provides an overview of root cause analysis. It defines root cause analysis as a method used to address problems by identifying their underlying root causes in order to correct or eliminate the cause and prevent recurrence. It describes traditional applications, objectives of training, definitions of root cause and approaches. Key steps in root cause analysis are identified as understanding the meaning of root cause, identifying the steps to find the root cause of problems, and using tools like fishbone diagrams, 5 whys, and asking questions.
This document lists various types of accessories and articles of clothing. It includes jewelry accessories like rings, necklaces, and watches, as well as bags, wallets, belts, and sunglasses. The list also contains different articles of clothing such as shirts, dresses, trousers, shorts, skirts, socks, shoes, ties, pajamas, and swimsuits. Outerwear such as coats, jackets, vests, sweaters, and uniforms are mentioned along with accessories like scarves, gloves, and mittens.
The document contains several quotes and sayings about life, challenges, love, and overcoming difficulties. It encourages facing failures and challenges with optimism and a smile, accepting certain things cannot be explained like love, and empowering oneself to pull through hard times alone rather than relying on others for help.
Dokumen tersebut membahas tentang produk suplemen buah Acai yang dikemas dalam bentuk kapsul, yang mengandung khasiat berbagai buah dari hutan Amazon untuk kesehatan dan diet sehari-hari. Produk ini dikemas khusus untuk memudahkan penyerapan zat gizi oleh semua kelompok umur.
Government and media response to disaster gwestmorelandgwestmo
The document discusses two articles on the negative effects of frightening or exaggerated news content. A survey found that 6th graders had vivid memories of disturbing news they watched. Another article focuses on the risks of exaggeration in news reporting during the 2001 anthrax attacks. Both stories suggest that alarming or overstated news coverage can cause increased negative reactions and effects on viewers.
The document discusses using Fitbit devices in a high school classroom to motivate students towards healthier lifestyles. It includes an email exchange where a teacher asks questions about checking out a Fitbit to students and whether data supports their effectiveness. The Fitbit representative says the devices can be reset and checked out to multiple students. They also say Fitbits should not be used for contact sports but are fine for other activities like running. No free devices or rentals are offered but there is a 30-day return policy.
Presentation given by Siddharth Saxena of Sacred Heart Convent School in the Stage 3 of Mathura Genius Award 2009 (Senior Level) organized by Paarth Educational Foundation (www.paarth.in)
The document provides an overview of root cause analysis. It defines root cause analysis as a method used to address problems by identifying their underlying root causes in order to correct or eliminate the cause and prevent recurrence. It describes traditional applications, objectives of training, definitions of root cause and approaches. Key steps in root cause analysis are identified as understanding the meaning of root cause, identifying the steps to find the root cause of problems, and using tools like fishbone diagrams, 5 whys, and asking questions.
This document lists various types of accessories and articles of clothing. It includes jewelry accessories like rings, necklaces, and watches, as well as bags, wallets, belts, and sunglasses. The list also contains different articles of clothing such as shirts, dresses, trousers, shorts, skirts, socks, shoes, ties, pajamas, and swimsuits. Outerwear such as coats, jackets, vests, sweaters, and uniforms are mentioned along with accessories like scarves, gloves, and mittens.
The document contains several quotes and sayings about life, challenges, love, and overcoming difficulties. It encourages facing failures and challenges with optimism and a smile, accepting certain things cannot be explained like love, and empowering oneself to pull through hard times alone rather than relying on others for help.
Dokumen tersebut membahas tentang produk suplemen buah Acai yang dikemas dalam bentuk kapsul, yang mengandung khasiat berbagai buah dari hutan Amazon untuk kesehatan dan diet sehari-hari. Produk ini dikemas khusus untuk memudahkan penyerapan zat gizi oleh semua kelompok umur.
Government and media response to disaster gwestmorelandgwestmo
The document discusses two articles on the negative effects of frightening or exaggerated news content. A survey found that 6th graders had vivid memories of disturbing news they watched. Another article focuses on the risks of exaggeration in news reporting during the 2001 anthrax attacks. Both stories suggest that alarming or overstated news coverage can cause increased negative reactions and effects on viewers.
The document discusses using Fitbit devices in a high school classroom to motivate students towards healthier lifestyles. It includes an email exchange where a teacher asks questions about checking out a Fitbit to students and whether data supports their effectiveness. The Fitbit representative says the devices can be reset and checked out to multiple students. They also say Fitbits should not be used for contact sports but are fine for other activities like running. No free devices or rentals are offered but there is a 30-day return policy.
Presentation given by Siddharth Saxena of Sacred Heart Convent School in the Stage 3 of Mathura Genius Award 2009 (Senior Level) organized by Paarth Educational Foundation (www.paarth.in)
Eventtypes allow you to categorize events at search time based on search definitions. For example, defining an eventtype called "problem" that includes terms like "error", would tag any events containing those terms as eventtype="problem". This provides a dynamic way to tag events without modifying the raw data. Reports in Splunk display search results in a formatted view like a table or chart and can be placed on dashboards. Apps are collections of Splunk configurations and code that allow you to customize your Splunk environment for specific use cases.
El documento describe un caso de embarazo precoz en la escuela U. E. Urquia en Venezuela. Se presentan varios casos de niñas entre 12 y 17 años que están embarazadas. El documento también describe las consecuencias físicas, psicológicas y sociales del embarazo precoz y la necesidad de implementar programas educativos sobre salud sexual y reproductiva para prevenir este problema.
Top-notch trainers involve participants early, check for understanding, and modify plans based on feedback. They use a variety of learning methods and explain the purpose behind activities. Delivery requires adjusting, refining, and redesigning. Credibility depends on setting norms, eliminating time wasters, engaging participants, and managing behaviors. Trainers must present information, lead discussions, direct exercises, and make effective transitions.
WebHumanResource (WebHR) is an online Human Resource Management System for small and medium organizations. WebHR makes it easy for the HR Department to start managing their HR effectively and efficiently in less than 20 minutes. WebHR is an indispensable tool not just for HR Manager but for the entire organization.
WebHR assists in managing the organization's most important asset - its Human Resource.
This document appears to be a collection of messages between two friends, Shivani and Kiran, reminiscing about their friendship over the years. They discuss inside jokes and memories from their time in college, their shared interests and dislikes, how their first impressions of each other changed, conflicts they have overcome, and the important role they play in each other's lives. Kiran wishes Shivani a happy birthday and says he will celebrate with her next year.
A man bought a rare baseball card worth $92,000 to cheer up his sick son. Lebron James led the Miami Heat to victory over the Los Angeles Clippers despite some of the Heat players being ill with the flu. Chris Brown returned to court for a probation issue related to his assault of Rihanna in 2009, and Rihanna accompanied him to court.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
A talk I gave on OpenSourceChina conference in Dec 2015. The talk is about how netflix builds its data pipeline platform to handle hundreds of billions of events a day. How everybody should leverage the same streaming architecture to build their apps.
The document provides an overview of training conducted by the 2nd Battalion, 130th Infantry Regiment at the eXportable Combat Training Capability (XCTC) program. It discusses how the battalion conducted platoon-level training, including squad and platoon-level live fires. It highlights photos from their training, which included clearing buildings, establishing mortar positions, and medical training like a mass casualty exercise. The commander comments that XCTC develops adaptive, morally straight junior leaders and that the Black Hawk Regiment's Soldiers are recognized for their confidence, courtesy, and fighting ability.
ASUG (Ontario SAP User Group) - Industry & Academic Partnership ROI v finalMichael Sparling
Mike Sparling, the Dean of a large business school, gave a presentation about initiatives at Seneca College to transform business education. He discussed how the relationship between schools and customers/students has changed, requiring schools to adapt. Seneca is focusing on experiential learning through partnerships with industry and applied research projects. The presentation highlighted the creation of a new Center for Big Data and Business Analysis to teach data management and analysis skills. The goal is to produce "different" graduates prepared for future business challenges and opportunities through disruptive change.
MonaVie merupak produk yang sangat dinanti oleh masyarakat Indonesia! MonaVie merupakan minuman supplemen kesehatan dengan komposisi utama Acai Berry dari Brazil yang dikenal dengan kandungan antioksidan tertinggi diantara berbagai buah super, dipadu dengan setidaknya 18 buah dari berbagai belahan dunia yang juga memiliki manfaat kesehatan yang baik.
Keunggulan produk MonaVie yang menghasilkan produk kesehatan terbaik juga memberikan peluang bisnis bagi wirausahawan dengan menjadi distributor MonaVie. Dengan menjadi distributor MonaVie, Anda dapat menikmati dan berbagi manfaat MonaVie, sekaligus mendapatkan keuntungan finansial melalui sistim bonus yang menarik.
Info lebih lanjut kunjungi: http://impianhati.com
ISN Silver Coins Opportunity Explained,
With HSBC buying up stocks of silver and the Daily Telegraph predicting a 400% rise in the next 3 years it is an excellent time to buy silver. In consequence the general public is actively looking for competitively priced coins which is what this fantastic business provides.
El documento habla sobre la maduración de las reacciones de enderezamiento y equilibrio en bebés a través del uso de superficies móviles y estimulación del cuerpo. Describe diferentes posiciones como decúbito ventral, dorsal y lateral, así como ejercicios en cuatro puntos, bipedestación y caminar sobre líneas, para desarrollar el equilibrio mientras el cuerpo o la superficie se mueven.
What's the Science in Data Science? - Skipper SeaboldPyData
The gold standard for validating any scientific assumption is to run an experiment. Data science isn’t any different. Unfortunately, it’s not always possible to design the perfect experiment. In this talk, we’ll take a realistic look at measurement using tools from the social sciences to conduct quasi-experiments with observational data.
This document discusses foundational concepts for effective incident investigations. It argues that not everyone can investigate incidents well just by following basic procedures and training. Effective investigations require understanding key concepts like using appropriate terminology and models. The presentation contrasts egocentric models that focus on failure and human error with ergonomic models that examine all factors contributing to an interaction. The goal of investigation is to change the future by identifying controls, not blame. Effective investigations account for human, equipment and environmental capabilities to find engineering solutions rather than just fixing failures.
Neil Thompson - Value Inspired Testing: Renovating Risk-Based Testing and Inn...TEST Huddle
This document discusses value-inspired testing and innovating testing approaches. It proposes renovating risk-based testing by collating current risk-based testing variants, using a context-driven mix of risk principles, grading test coverage rather than truncating tests, and balancing risk against benefits to provide net value. It also suggests innovating testing by considering evolution in nature as a value flow, appreciating the concept of memes and evolving "memeplexes" in testing, and finding an emergent path between too much chaos and too much order. The document argues that by taking a holistic and evolving approach, testing will continue to innovate rather than become obsolete.
Is it possible to define a set of axioms that provide a framework for software testing that all the variations of test approach currently being advocated align with or obey? In this respect, an axiom would be an uncontested principle; something self-evidently and so obviously true and not requiring proof. What would such test axioms look like? This paper summarises some preliminary work on defining a set of Test Axioms. Some applications of the axioms that would appear useful are suggested for future development. It is also suggested the work of practitioners and researchers is on very shaky ground unless we refine and agree these Axioms. This is a work in progress.
1. The document discusses empiricism in philosophy and science, from early thinkers like Newton to modern ones like Taleb. It emphasizes the importance of experimental testing of hypotheses.
2. The document then gives examples of common mistakes made in applying statistics and empiricism to financial modeling and stock selection, such as ignoring data that doesn't fit hypotheses.
3. It analyzes some sample stock portfolio and factor modeling data, finding the models' effectiveness varied over time, highlighting the need for ongoing empirical testing of hypotheses.
Exploratory testing is an approach to testing that emphasizes the freedom and responsibility of testers to continually optimize the value of their work. It is the process of three mutually supportive activities done in parallel: learning, test design, and test execution. With skill and practice, exploratory testers typically uncover an order of magnitude more problems than when the same amount of effort is spent on procedurally scripted testing. All testers conduct exploratory testing in one way or another, but few know how to do it systematically to obtain the greatest benefits. Even fewer can articulate the process. James Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. James focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.
Eventtypes allow you to categorize events at search time based on search definitions. For example, defining an eventtype called "problem" that includes terms like "error", would tag any events containing those terms as eventtype="problem". This provides a dynamic way to tag events without modifying the raw data. Reports in Splunk display search results in a formatted view like a table or chart and can be placed on dashboards. Apps are collections of Splunk configurations and code that allow you to customize your Splunk environment for specific use cases.
El documento describe un caso de embarazo precoz en la escuela U. E. Urquia en Venezuela. Se presentan varios casos de niñas entre 12 y 17 años que están embarazadas. El documento también describe las consecuencias físicas, psicológicas y sociales del embarazo precoz y la necesidad de implementar programas educativos sobre salud sexual y reproductiva para prevenir este problema.
Top-notch trainers involve participants early, check for understanding, and modify plans based on feedback. They use a variety of learning methods and explain the purpose behind activities. Delivery requires adjusting, refining, and redesigning. Credibility depends on setting norms, eliminating time wasters, engaging participants, and managing behaviors. Trainers must present information, lead discussions, direct exercises, and make effective transitions.
WebHumanResource (WebHR) is an online Human Resource Management System for small and medium organizations. WebHR makes it easy for the HR Department to start managing their HR effectively and efficiently in less than 20 minutes. WebHR is an indispensable tool not just for HR Manager but for the entire organization.
WebHR assists in managing the organization's most important asset - its Human Resource.
This document appears to be a collection of messages between two friends, Shivani and Kiran, reminiscing about their friendship over the years. They discuss inside jokes and memories from their time in college, their shared interests and dislikes, how their first impressions of each other changed, conflicts they have overcome, and the important role they play in each other's lives. Kiran wishes Shivani a happy birthday and says he will celebrate with her next year.
A man bought a rare baseball card worth $92,000 to cheer up his sick son. Lebron James led the Miami Heat to victory over the Los Angeles Clippers despite some of the Heat players being ill with the flu. Chris Brown returned to court for a probation issue related to his assault of Rihanna in 2009, and Rihanna accompanied him to court.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
A talk I gave on OpenSourceChina conference in Dec 2015. The talk is about how netflix builds its data pipeline platform to handle hundreds of billions of events a day. How everybody should leverage the same streaming architecture to build their apps.
The document provides an overview of training conducted by the 2nd Battalion, 130th Infantry Regiment at the eXportable Combat Training Capability (XCTC) program. It discusses how the battalion conducted platoon-level training, including squad and platoon-level live fires. It highlights photos from their training, which included clearing buildings, establishing mortar positions, and medical training like a mass casualty exercise. The commander comments that XCTC develops adaptive, morally straight junior leaders and that the Black Hawk Regiment's Soldiers are recognized for their confidence, courtesy, and fighting ability.
ASUG (Ontario SAP User Group) - Industry & Academic Partnership ROI v finalMichael Sparling
Mike Sparling, the Dean of a large business school, gave a presentation about initiatives at Seneca College to transform business education. He discussed how the relationship between schools and customers/students has changed, requiring schools to adapt. Seneca is focusing on experiential learning through partnerships with industry and applied research projects. The presentation highlighted the creation of a new Center for Big Data and Business Analysis to teach data management and analysis skills. The goal is to produce "different" graduates prepared for future business challenges and opportunities through disruptive change.
MonaVie merupak produk yang sangat dinanti oleh masyarakat Indonesia! MonaVie merupakan minuman supplemen kesehatan dengan komposisi utama Acai Berry dari Brazil yang dikenal dengan kandungan antioksidan tertinggi diantara berbagai buah super, dipadu dengan setidaknya 18 buah dari berbagai belahan dunia yang juga memiliki manfaat kesehatan yang baik.
Keunggulan produk MonaVie yang menghasilkan produk kesehatan terbaik juga memberikan peluang bisnis bagi wirausahawan dengan menjadi distributor MonaVie. Dengan menjadi distributor MonaVie, Anda dapat menikmati dan berbagi manfaat MonaVie, sekaligus mendapatkan keuntungan finansial melalui sistim bonus yang menarik.
Info lebih lanjut kunjungi: http://impianhati.com
ISN Silver Coins Opportunity Explained,
With HSBC buying up stocks of silver and the Daily Telegraph predicting a 400% rise in the next 3 years it is an excellent time to buy silver. In consequence the general public is actively looking for competitively priced coins which is what this fantastic business provides.
El documento habla sobre la maduración de las reacciones de enderezamiento y equilibrio en bebés a través del uso de superficies móviles y estimulación del cuerpo. Describe diferentes posiciones como decúbito ventral, dorsal y lateral, así como ejercicios en cuatro puntos, bipedestación y caminar sobre líneas, para desarrollar el equilibrio mientras el cuerpo o la superficie se mueven.
What's the Science in Data Science? - Skipper SeaboldPyData
The gold standard for validating any scientific assumption is to run an experiment. Data science isn’t any different. Unfortunately, it’s not always possible to design the perfect experiment. In this talk, we’ll take a realistic look at measurement using tools from the social sciences to conduct quasi-experiments with observational data.
This document discusses foundational concepts for effective incident investigations. It argues that not everyone can investigate incidents well just by following basic procedures and training. Effective investigations require understanding key concepts like using appropriate terminology and models. The presentation contrasts egocentric models that focus on failure and human error with ergonomic models that examine all factors contributing to an interaction. The goal of investigation is to change the future by identifying controls, not blame. Effective investigations account for human, equipment and environmental capabilities to find engineering solutions rather than just fixing failures.
Neil Thompson - Value Inspired Testing: Renovating Risk-Based Testing and Inn...TEST Huddle
This document discusses value-inspired testing and innovating testing approaches. It proposes renovating risk-based testing by collating current risk-based testing variants, using a context-driven mix of risk principles, grading test coverage rather than truncating tests, and balancing risk against benefits to provide net value. It also suggests innovating testing by considering evolution in nature as a value flow, appreciating the concept of memes and evolving "memeplexes" in testing, and finding an emergent path between too much chaos and too much order. The document argues that by taking a holistic and evolving approach, testing will continue to innovate rather than become obsolete.
Is it possible to define a set of axioms that provide a framework for software testing that all the variations of test approach currently being advocated align with or obey? In this respect, an axiom would be an uncontested principle; something self-evidently and so obviously true and not requiring proof. What would such test axioms look like? This paper summarises some preliminary work on defining a set of Test Axioms. Some applications of the axioms that would appear useful are suggested for future development. It is also suggested the work of practitioners and researchers is on very shaky ground unless we refine and agree these Axioms. This is a work in progress.
1. The document discusses empiricism in philosophy and science, from early thinkers like Newton to modern ones like Taleb. It emphasizes the importance of experimental testing of hypotheses.
2. The document then gives examples of common mistakes made in applying statistics and empiricism to financial modeling and stock selection, such as ignoring data that doesn't fit hypotheses.
3. It analyzes some sample stock portfolio and factor modeling data, finding the models' effectiveness varied over time, highlighting the need for ongoing empirical testing of hypotheses.
Exploratory testing is an approach to testing that emphasizes the freedom and responsibility of testers to continually optimize the value of their work. It is the process of three mutually supportive activities done in parallel: learning, test design, and test execution. With skill and practice, exploratory testers typically uncover an order of magnitude more problems than when the same amount of effort is spent on procedurally scripted testing. All testers conduct exploratory testing in one way or another, but few know how to do it systematically to obtain the greatest benefits. Even fewer can articulate the process. James Bach looks at specific heuristics and techniques of exploratory testing that will help you get the most from this highly productive approach. James focuses on the skills and dynamics of exploratory testing, and how it can be combined with scripted approaches.
Test reporting is something few testers take time to practice. Nevertheless, it's a fundamental skill—vital for your professional credibility and your own self management. Many people think management judges testing by bugs found or test cases executed. Actually, testing is judged by the story it tells. If your story sounds good, you win. A test report is the story of your testing. It begins as the story we tell ourselves, each moment we are testing, about what we are doing and why. We use the test story within our own minds, to guide our work. James Bach explores the skill of test reporting and examines some of the many different forms a test report might take. As in other areas of testing, context drives good reporting. Sometimes we make an oral report; occasionally we need to write it down. Join James for an in-depth look at the art of the reporting.
This document provides a practical guide to conducting controlled experiments on the web. It discusses key terminology used in controlled experiments such as overall evaluation criterion, factors, variants, null hypothesis, confidence level, and power.
It presents two motivating examples where small changes to user interfaces led to surprisingly large differences in important metrics. In one case, removing a coupon code from an e-commerce checkout page increased conversion rates by 6.5%. In another, changing a ratings widget from yes/no to 5-stars reduced ratings by an order of magnitude.
The document emphasizes that controlled experiments allow evaluating ideas in a reliable way and provide guidance on their value. It also notes that building systems to support experimentation encourages innovation through low
The document provides an overview of exploratory testing. It defines exploratory testing as simultaneous learning, test design, and test execution. Exploratory testing is a highly situational practice that is informed by factors like the product, tester skills, mission, and what is learned during testing. An effective exploratory tester is able to carefully observe, think critically, generate diverse test ideas, and apply rich resources and heuristics to testing. While the external process is straightforward, the inner thought process of the exploratory tester is what truly distinguishes excellent exploratory testing.
Stuart Reid - When Passion Obscures the Facts:The Case For Evidence-Based Te...TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on When Passion Obscures the Facts:The Case For Evidence-Based Testing by Stuart Reid. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
This document summarizes James Bach and Chris Ojaste's repair of a broken Kraft "Grate-It Fresh" parmesan cheese dispenser on December 25, 2008. The dispenser was not grating cheese despite 1/3 of the block remaining. Their analysis determined the grating mechanism involved a rotatable grating plate attached to a threaded spindle that pushes the cheese into the blades. They found the spindle threads were stripped, slipping the pressure plate. Attempts to manually grate the cheese failed. Further examination revealed grooves in the cheese face preventing the grater blades from engaging, identifying the root cause.
Model risk and the importance of model risk management has gotten significant attention in the last few years. As financial companies increase their reliance on quants and quantitative models for decision making, they are increasingly exposed to model risk and are looking for ways to mitigate it. The financial crisis of 2008 and various high profile financial accidents due to model failures has brought model risk management to the forefront as an important topic to be addressed. Many regulatory efforts (Solvency II, Basel III, Dodd-Frank etc.) have been initiated obligating banks and financial institutions to incorporate formal model risk management programs to address model risk. In this talk, we will discuss the key aspects of model verification and validation and discuss best practices for stress and scenario testing for model verification and validation for MATLAB-based models. These best practices are meant to provide practical tips for companies embarking on a formal model risk management program or enhancing their model risk methodologies to address the new realities.
Exploratory testing is an approach that emphasizes freedom and responsibility of individual testers in a process where continuous learning, test design, and execution occur simultaneously. It is a disciplined, planned, and controlled form of testing that focuses on continuous learning. Research has shown there is no significant difference in results between exploratory testing and preplanned test cases, but exploratory testing requires significantly less effort overall. Effective exploratory testing requires skills like making models, keeping an open mind, and risk-based testing approaches. Both the strengths and potential blind spots of exploratory testing are discussed.
Applying Psychology To The Estimation of QAPaula Heenan
Paula Heenan uses her background in psychology to explain how mental heuristics can affect testers' judgements and estimations. Three key heuristics are discussed: 1) "adjust and anchor", where estimates are made by starting from an initial anchor value from past projects, which may not be reliable. 2) "representativeness", where testers focus on functionality that appears similar to past defects, rather than considering probabilities. 3) "availability", where testers focus on easily remembered past issues rather than using defect metrics, due to imaginability and retrievability biases. To mitigate these heuristics, testers should use metrics, checklists, traceability matrices from multiple teams to ensure sufficient testing coverage and understand complexity
The document discusses exploratory testing and Keri Smith. It provides an overview of exploratory testing, noting that it emphasizes personal freedom and responsibility of testers to continually optimize testing. It also discusses Keri Smith's work in conceptual art and guided journals that encourage observing the world like artists and scientists.
Testing in modern times a story about quality and value - agile testing dev ...Huib Schoots
In agile and especially DevOps approaches the motto is: automated everything! Companies like Facebook claim they do not have testers at all. Microsoft only has SDET (software development engineers in Test), other companies are T-shaping developers to do the testing. New kid on the block is AI and machine learning, that will definitely replace testing I hear people claim. What is really happening globally? Do we no longer need testers? Can we actually automate everything? How can we make valuable software for our clients?
In this presentation I will address questions like:
* Do we need testing? And if so: why is testing important?
* What is the business case of testing?
* Can developers also test? And if so: do we still need testers?
* How can we create quality software?
Validity and Reliability of the Research Instrument; How to Test the Validati...Hamed Taherdoost
Questionnaire is one of the most widely used tools to collect data in especially social science research. The main objective of questionnaire in research is to obtain relevant information in most reliable and valid manner. Thus the accuracy and consistency of survey/questionnaire forms a significant aspect of research methodology which are known as validity and reliability. Often new researchers are confused with selection and conducting of proper validity type to test their research instrument (questionnaire/survey). This presentation explores and describes the validity and reliability of a questionnaire/survey and also discusses various forms of validity and reliability tests.
This handbook is written to show how greater control can be gained over total product reliability by the utilization of Accelerated Stress Testing techniques (AST)
Similar to Value-Inspired Testing - renovating Risk-Based Testing, & innovating with Emergence (2012 paper) (20)
Six schools, three cultures of testing: future-proof by shifting left, down, ...Neil Thompson
The document discusses a presentation given by Neil Thompson at the 15th QA & Test conference in Bilbao, Spain from 19-21 October 2016. The presentation covered the history of software testing and proposed that there are three distinct "cultures" or "schools" of testing that don't communicate enough: engineering/standards-driven testing, analytical/science-driven testing, and context-driven testing. Thompson suggested that understanding the different perspectives could help "future-proof" testing approaches by shifting left, down, right, and/or up.
Test Data, Information, Knowledge, Wisdom: past, present & future of standing...Neil Thompson
The document discusses test data for software testing from both past and present perspectives. It begins by covering definitions and concepts related to test data from ISO 29119 standards. It then discusses the basics of test data and how test data requirements and information are developed through the test planning, design and implementation processes. The document also discusses different sources of test data and how test data relates to different testing levels and techniques like unit testing, integration testing and system testing.
From 'Fractal How' to Emergent Empowerment (2013 article)Neil Thompson
Neil Thompson outlines different leadership styles and personalities, and argues that traditional "command-and-control" leadership is not well-suited to today's rapidly changing environment. He discusses how introverted leaders can be effective, especially with proactive teams, and advocates an approach of "emergent empowerment" where leaders channel ideas from team members rather than dictate tasks. Thompson recommends understanding personalities to improve leader-team dynamics and encouraging innovation through empowerment rather than authoritarian control.
The document discusses renovating risk-based testing and innovating with emergence. It proposes renovating the use of risk in testing by collating current risk-based testing variants, using a context-driven mix of risk principles, grading test coverage from high to low risk rather than truncating tests, and balancing risk against benefits to provide net value. It also proposes innovating in testing by considering evolution in nature as a value flow, appreciating the concept of memes and evolving "memeplexes" in testing, and finding the emergent path between too much chaos and too much order through creativity. The document argues that when holistic and evolving, testing will not
Risk-Based Testing - Designing & managing the test process (2002)Neil Thompson
This document provides an introduction to risk-based testing. It discusses how risk-based testing can help determine how much testing is enough by prioritizing tests that address risks. It also discusses when a product may be considered "good enough" by balancing sufficient benefits, critical problems, and whether improving the product would cause more harm than good. The testing contribution to the release decision is to demonstrate delivered benefits and resolution of critical problems through testing records to provide confidence in the assessment.
Testing Masterclass for Electromind (Steve Allott) Mar 2003, London. Slideset was for discussions, not a linear presentation, then was part-extended (work-in-progress) after session.
'Best Practices' & 'Context-Driven' - Building a bridge (2003)Neil Thompson
The document outlines a presentation on bridging the gap between "best practices" and "context-driven" approaches to test management. It discusses learning objectives around understanding each perspective and applying Goldratt's theory of constraints thinking tools. The presentation will cover examples of using these tools to analyze testing practices and determine what is most appropriate based on different project contexts.
Risk Mitigation Trees - Review test handovers with stakeholders (2004)Neil Thompson
The document discusses techniques for managing handovers between development and testing stages, specifically Testing Review Boards (TRBs) and Risk Mitigation Trees (RMTs). TRBs are meetings of stakeholders at handovers to make collaborative decisions. RMTs are diagramming techniques used to split residual risks. Both techniques were used successfully on recent projects to facilitate decision making at handovers and prior to go-live.
ROI at the bug factory - Goldratt & throughput (2004)Neil Thompson
The document discusses using concepts from manufacturing to analyze software development processes. It introduces ROI and Goldratt's Theory of Constraints, which views inventory as a constraint on throughput and profitability. The document argues that specifications and unfinished software can be viewed as inventory in software development. Seeing software development and testing processes through this "factory" lens may provide insights on effectiveness, efficiency, and improvement.
Feedback-focussed process improvement (2006)Neil Thompson
This document summarizes a presentation on process improvement for information systems learning from manufacturing methods. It discusses how Toyota achieved success through its Toyota Production System focusing on quality, then global dominance, and now innovation. It compares Toyota's approach to the Theory of Constraints by Eliyahu Goldratt. The presentation will explore how these new manufacturing paradigms can translate to agile methods and process improvement in IT/information systems using examples and thinking tools to facilitate continuous learning and improvement.
Thinking tools - From top motors through s'ware proc improv't to context-driv...Neil Thompson
This document summarizes Neil Thompson's presentation on applying principles from manufacturing process improvement to software development processes. Some key points:
1. Toyota's production system and product development system emphasize continuous process flow, problem solving, visual controls, and a learning organization to drive quality and innovation.
2. Principles from Toyota, the Toyota Production System, and Eliyahu Goldratt's Theory of Constraints can be applied beyond manufacturing to areas like software development.
3. Analogies will be drawn between manufacturing concepts like value streams, constraints, and critical chains, and how they relate to software development processes and problem solving. The presentation aims to provide simple thinking tools to identify and address constraints in software development lif
This document summarizes a presentation given at STARWest 2007 titled "Holistic Test Analysis & Design". The presentation discusses a holistic method for test analysis and design that uses a spreadsheet to document logical and physical test coverage in a flexible and multi-dimensional manner. The method accounts for test items, features, bases, risks, and conditions to provide a comprehensive view of what needs to be tested. Examples are provided to illustrate how the spreadsheet representation can be used to plan testing at different levels from acceptance to component.
Value Flow Science - Fitter lifecycles from lean balanced scorecards (2011)Neil Thompson
This document discusses using Value Flow ScoreCards to improve software testing and development processes. Value Flow ScoreCards use six viewpoints (supplier, process, product, customer, financial, improvement) to establish objectives, measures, and initiatives. This helps balance stakeholder needs and do work "well enough." The document also discusses applying lean principles to improve the flow of working software through the development lifecycle and reduce impediments. Overall it promotes using flexible, holistic techniques like Value Flow ScoreCards to define better testing strategies, coverage, and processes.
What is Risk? - lightning talk for software testers (2011)Neil Thompson
Software Testing 21 Jun 2011
The document summarizes a presentation given at the Specialist Interest Group in Software Testing (SIGiST) on June 21, 2011 about software risk. The presentation discusses what risk is, how it can be quantified using likelihood and consequence, and that risk has other dimensions like undetectability and urgency that make it worse. It provides examples of different types of risks like project, process, and product risks. It introduces the idea of a "tunable tetrahedron" to represent the interconnected factors of quality, scope, time, and cost. Finally, it discusses using likelihood, consequence, and testability to prioritize product risks for testing.
The Science of Software Testing - Experiments, Evolution & Emergence (2011)Neil Thompson
The document discusses the history and evolution of software testing from the early days of debugging programs to the current conceptions of testing as both an engineering discipline and a scientific field of study. It traces the development of software testing from initial methods focused on demonstration and destruction to more modern prevention-oriented and quality-focused approaches. The document also examines perspectives on treating software testing as a science through use of the scientific method, experiments, and evolving theories and models of both development and testing.
Testing as Value Flow Mgmt - organise your toolbox (2012)Neil Thompson
This document discusses software testing and proposes considering it as value flow management. It summarizes the history of definitions of software testing and proposes alternatives to claims that testing is dead. These alternatives include considering testing as a science by adopting scientific methods and principles of falsifiability. The document also discusses treating the software lifecycle as a flow of value and considering context-driven principles. It proposes that any lifecycle can be improved by focusing on managing the flow of value and considering the project context.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
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.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
1. Value-Inspired Testing:
Renovating Risk-Based Testing, and
Innovating with Emergence v1.0
Neil Thompson NeilT@TiSCL.com @neilttweet
@neiltskype
Thompson information Systems Consulting Ltd www.TiSCL.com +44 (0)7000 NeilTh
(634584)
23 Oast House Crescent,
Farnham,
Surrey,
GU9 0NP
England, UK
Abstract
Is testing “dead”? Some parts are declining, but
evolution can inspire survival.
To renovate use of risk;
collate current variants, eg “Risk-Based”,
“Risk-Driven”;
use a context-driven mix of principles;
prioritise testing from high to low (not zero);
consider value as benefits minus risks;
remember risk applies throughout testing,
from static testing through execution, bug-
fixing and beyond;
integrate risk into Value Flow ScoreCards to
manage across complementary views of
quality.
To innovate:
consider evolution in nature: periods of
ecosystems in stability, punctuated by
innovative disturbances;
as genes evolve in biology, “memes” evolve
in thinking;
testing’s history suggests some specific
memeplexes;
natural innovation seems to emerge on a
path between “excess order” and “excess
chaos”;
could testing evolve similarly? Try Johnson’s
“Where good ideas come from”.
So: VIVVAT Value-Inspired Verification, Validation
And Testing! Please join me in exploring our future.
1
2. Contents
Abstract ............................................................................................................................................................................... 1
0. Introduction .................................................................................................................................................................... 3
1. Renovating the use of Risk in testing .............................................................................................................................. 4
1.1 Current variants of Risk-Based Testing etc ................................................................................................................ 4
1.2 Context-driven mix of available principles ................................................................................................................ 5
1.3 Risk-Graded Testing .................................................................................................................................................. 5
1.4 Value-Graded Testing ................................................................................................................................................ 6
1.5 Value-Inspired Testing............................................................................................................................................... 6
1.6 Value Flow ScoreCards .............................................................................................................................................. 8
Through the lifecycle ................................................................................................................................................... 8
Integrating risk .......................................................................................................................................................... 10
2. Innovating in testing, using Emergence concepts ......................................................................................................... 12
2.1 Evolution in Nature ................................................................................................................................................. 13
Biology....................................................................................................................................................................... 14
Relationship with other sciences .............................................................................................................................. 16
2.2 Evolution of Software Testing ................................................................................................................................. 16
The view ahead ......................................................................................................................................................... 16
The story so far ......................................................................................................................................................... 17
2.3 Genes to Memes ..................................................................................................................................................... 18
2.4 Memeplexes in the History of Testing .................................................................................................................... 18
2.5 Emergence between “Too Much Chaos” and “Too Much Order” .......................................................................... 21
2.6 Innovation and Ideas for Testing ............................................................................................................................. 21
3. VIVVAT Value-Inspired Verification, Validation And Testing ........................................................................................ 25
References and Acknowledgements ................................................................................................................................. 26
2
3. 0. Introduction
The theme of this EuroSTAR 2012 conference is "Innovate & Renovate: Evolving Testing". In his call for submissions,
programme chair Zeger van Hese included a quotation from William Edwards Deming: "Learning is not compulsory...
neither is survival." This is presumably a veiled threat – if we don’t learn, we may not survive. But is it already too
late? Several speakers have recently alleged that testing is dead, or some very similar message:
Tim Rosenblatt (Cloudspace blog 22 Jun 2011) “Testing Is Dead – A Continuous Integration Story For Business
People”;
James Whittaker (STARWest 05 Oct 2011) “All That Testing Is Getting In The Way Of Quality”; and
Alberto Savoia (Google Test Automation Conference 26 Oct 2011) “Test Is Dead”.
There may be others. But I suggest that at least some of these commentators seem to be talking mainly about “the
testing phase”, with an emphasis on functional testing, “independent” of the developers. They mean in particular
purveyors of standard, manual testing, which is increasingly offshored or automated. No-one seems to think that
performance, security or privacy testing is dead. No-one seems to be suggesting that developers have stopped testing
and so should everyone else. It is more a question of who and how.
So in this paper, when I talk about testing, I mean all of testing. I include:
not just dynamic testing (executing software), but various kind of static testing, eg reviews;
not just functional testing but all the non-functional (or para-functional) types – and this list itself may evolve.
I consider what we can learn from the history of testing and its place in the “ecosystems” of IT products and projects.
Testing has been called many things: an art, a craft, and more recently some people (including myself) have been
trying to make it more of a science – even if that means it is a social science (as Cem Kaner argues).
I think of testing as “value flow management” – we should be facilitating / assisting / monitoring / measuring /
improving / optimising (according to your taste, context and role) the flow of value all the way from ideas in people’s
heads (initial requirements) through to not only implemented but also service-managed, supported and maintained
systems and services, in their human context. To do this, in today’s environment of increasingly-rapid, innovative and
pervasive change, we do need to renovate and innovate. When holistic and evolving, testing will not die (and must not
be allowed to die). I choose to focus on:
renovating the increasingly fragmented and apparently-neglected subject of risk-based testing; and
using analogies from science and evolution to inspire ideas for innovation in testing generally.
3
4. 1. Renovating the use of Risk in testing
1.1 Current variants of Risk-Based Testing etc
The first step in renovation is to collate what variants of “Risk-Based Testing” (or related terms) are around, and how
we arrived at this situation. The diagram below shows a simplified flow over time, from left to right.
The early books by Hetzel, Myers and Beizer all contained some notions of testing as depending on principles of risk,
but this was mostly implicit. Then in the later 1980s and through the 1990s, basing testing on risk became explicit as
statement of theory. But you wait ages for guidance on how to practically do risk-based testing, then in 2002 three
books came along at once!
Paul Gerrard, drawing on the earlier work of James Bach and others, published Risk-Based E-Business Testing,
the theme of which was imagining what could go wrong with a system, then designing tests to address those
risks. I was co-author of that book.
Craig & Jaskiel described in Systematic Software Testing a somewhat different view of risk-based testing,
which prioritised software features and attributes according to risk (its current version is called risk-driven
testing, and has no doubt evolved since then);
Kaner, Bach & Pettichord published Lessons Learned in Software Testing, which included context-driven
versions of both of the above variants, but distinguished them as risk-based test design and risk-based test
management respectively.
Since then, I have seen a variety of approaches, published in books, papers or as proprietary methods. I meet many
people who tell me they know what risk-based testing is, it’s quite easy to do, and it’s “not that stuff over there, that’s
not risk-based testing”. I think these are all useful to some degree, but I believe they are all partial views (either
focussing on the prioritisation side or on the risks-as-test-entities side), some seem to be too prescriptive / too
simplistic / too complex, and I do not believe that risk-based testing is easy. Not good risk-based testing, anyway.
The field seems to be fragmented; and it no longer seems to receive the attention it used to. Fashion has moved on to
other subjects. Are some people just paying lip-service to risk-based testing? How many people are doing it well? How
does it relate to /merge into safety-critical methods? In 2007 I integrated the two main aspects of risk-based testing
into my Holistic Test Analysis & Design method, but that is only part of the story (and does not yet have tool support).
I think it is time for a broad re-appraisal of the whole subject – away from one-size-fits-all, to be more inclusive of
various approaches, more responsive to context.
4
5. 1.2 Context-driven mix of available principles
I would like to see more cross-fertilisation and unification between the “upper and lower halves”, sometimes called
risk-based test management and risk-based test design. On some projects these are done by different people of
course, but not always. And anyhow, the two halves should fit together. One way (and it is only just one choice) is to
mirror-image James Bach’s Heuristic Test Strategy Model (HTSM), as illustrated below.
The lower half is borrowed straight from the HTSM, and the upper half is modified to show similar usage for
prioritisation of work. I do not mean simply “do this first, then that...” – decisions need to be made on what to
prioritise, and how. The message here is that we should be ready to mix and match methods and techniques from the
variety available, depending on context factors.
1.3 Risk-Graded Testing
One thing I feel compromises the respectability of risk-based testing in some situations is the notion that having
prioritised things, we can set a cut-off threshold below which things are not tested. A better way, I believe, is to
“grade” coverage and/or effort, from low (not zero) to high, according to the selected risk factors.
5
6. I think “Risk-Graded Testing” might be a better term here than Risk Based Testing. One reason is that Risk-Based
Testing aligns with the term Test Basis, often used to mean a document or other oracle against which tests are
designed. Another reason is that it distances itself from cruder notions of prioritisation, and from cut-off thresholds.
1.4 Value-Graded Testing
Taking this a step further: we should grade testing coverage / effort not only by risk, but also the varying benefits of
the features being tested. There is a partial correlation, because features which have high benefits will also tend to
have high business impact if they go wrong, but it is worth making the distinction because considering the benefits
may generate specific test ideas and inform the selection of test techniques. Particularly In agile methods, if a feature
is exhibiting serious bugs in testing and is not of critical benefit, it is more likely to be descoped from a release.
We may think of value in terms of expected benefits minus residual risk after an amount of testing.
1.5 Value-Inspired Testing
Risk is relevant at all levels of testing, but the risks differ by-level. The diagram below illustrates several principles:
all the way through the lifecycle, different risks accumulate;
the quality information a test provides depends on comparison of software’s behaviour with the test model,
the development mode (verification testing) and also real-world desired behaviour (validation testing).
6
7. Although this is shown in the format of a V-model, it is not necessarily advocating “the” V-model in its traditional
sense. I argue that all lifecycles have some kind of levels of stakeholders & participants, levels of specifications / other
oracles and levels of integration of the developed system. Iterative lifecycles can be considered as repeatedly
descending then ascending through some or all of these levels in various ways.
Looking at this in more detail: requirements are necessarily a simplification of the way the software will behave in use;
no requirements can be perfect. When functional and non-functional specifications are written, there are risks of
distorting / omitting requirements, or adding functionality that is not really wanted. And so on through design and
coding – all of these are different risks with their own set of risk factors (each with their probability and consequence
components). This chain (or rather, network) of risks corresponds to the various definitions of mistake, defect, fault,
failure etc.
To manage these various risks, we need a variety of techniques. The traditional view is that the earlier we mitigate
risks, the less the knock-on effect (diagram below), although in agile methods some more tactical risk management is
used, eg making some decisions as late as possible, allowing technical debt to build, then refactoring at suitable times.
Looking more closely at validation: it includes all the decisions that cannot be made by simply “checking” behaviour
against a specification:
7
8. Even if good specifications exist, are they 100% up to date? Are they still what is wanted, or is a change
request needed?
No specification is perfectly detailed or specifies every possible thing which the software should do and
should not do (expressable as risks), therefore some behaviour will be implicit / assumed, and judgement will
be needed;
in some contexts, traditional specifications may not exist at all;
testers may therefore need “oracles” other than specifications – for example:
o consistency with product /system purpose, history, image, claims, comparable products/systems etc
o familiar failure patterns.
So in summary, risk-related principles apply throughout testing, from reviews to test specification through execution
to retesting, regression testing, go-live and beyond.
1.6 Value Flow ScoreCards
Now, how can we manage risk throughout the system development lifecycle and throughout testing? I propose in this
paper a framework to do this, but in order to get there, for a few moments let us a step back from risk.
Through the lifecycle
In the introduction I suggested we think of testing as value flow management. One approach to this is to start with the
concept of a balanced scorecard. On the left half of the diagram below is a version of Kaplan & Norton’s original. On
the right side is a modified version, tailored for software quality after a variety of authors.
The basic principle is that for each different view of quality, we may set a structure of objectives, measures, targets
and initiatives. Kaplan & Norton’s original purpose was “translating strategy into action”. In IT project terms, we may
ask:
what are our objectives? (for example, we may want to adhere to a particular process standard, or achieve a
certain degree of product quality, or a degree of customer satisfaction;
by what measures will we gauge success – in colloquial terms, “what does good look like?”;
what targets shall we set for a particular stage, eg the next software release? This could be in terms of bug
frequencies and severities after go-live, but measures and targets need not be quantitative, for example
rubrics could be used for customer satisfaction surveys.
Then what initiatives shall we take to make this happen?
Four of the quality viewpoints may be thought of as applying to the current project; the fifth is about improvement,
for future projects.
8
9. In the following diagram, I develop this structure to fit conveniently within the software lifecycle. First I add two more
viewpoints, supplier and infrastructure. Then I arrange the viewpoints in a kind of “value flow unit”.
To use this practically, the scorecard becomes table of seven columns and four rows. There is a rough logical flow from
left to right. In earlier papers I have outlined several applications in and around testing, but there is not space here to
describe those.
In the following diagram (next page), I illustrate how the value flow items which can be defined for an individual team
or role can be cascaded to control value flow through the whole lifecycle, both down and up the levels and from left
to right (corresponding to static then dynamic testing).
9
10. Integrating risk
Now, we are ready to integrate risk into the scorecard. Risks may be seen as threats to the success of the objectives
for each view of quality, so we can insert a new row between objectives and the way we measure, target and define
the way forward. When we know the risks, we can build in appropriate management measures and tactics.
Next, let’s look at different types of risk. Many authors distinguish:
product risks, ie threats to the quality of software; from
project risks, ie threats to the conduct of project activities.
Some authors also distinguish a third type, process risk, which is a kind of specialism of project risk connected with
methodology.
The following diagram (next page) illustrates these, some examples, and relationships between the risks.
10
11. Finally, we can now be more specific about the risks in the scorecard – because there is a strong correlation between
the quality viewpoints and the risk types.
So to summarise up to now: we have arrived at a structure for setting out, balancing and measuring the full range of
quality viewpoints, and for associating with them the risks which threaten. This is a complete, integrated quality and
risk management framework. To continue the renovation, future work should now build together, using this
framework:
a more holistic context-driven approach to risk, putting together the “two halves” of test design and test
management and refining guidance on how to mix and match methods and techniques from the fragmented
variety on offer;
firming up into practical advice how to balance benefits against risks; and
clarifying how risk management activities can be pragmatically controlled throughout the software lifecycle
and throughout the testing process.
The challenge is to achieve an appropriate balance between a robust approach which is too complex, and an
achievable approach which is too simplistic to be useful; this balance varies of course with context.
11
12. Now to move towards the second half of this paper, which focuses on the rightmost column of the Value Flow
ScoreCard, ie improvement for future projects.
The above diagram illustrates the relationship between the Value Flow ScoreCard and a “toolbox” structure I
developed recently to fit around it, to embrace scientific thinking and a structure for thinking about innovation.
2. Innovating in testing, using Emergence concepts
This toolbox structure is not a primary focus of this paper, but just to position the risk renovation and testing-
innovation parts of this paper within that structure for reference:
This second part of this paper moves to consider innovation in testing, via analogies with how innovation occurs in
nature.
12
13. 2.1 Evolution in Nature
The outer layer of the toolbox consists of this triangle:
There is evidence that innovation in nature includes a phenomenon called emergence, which is associated with the
concepts of systems thinking and complexity theory. One way of looking at emergence is to see how different sciences
build progressively on top of each other, according to scale:
When human society is established, the resulting further innovation no longer depends on scale but becomes
explosive in its information content.
The explosion of human innovation is shown in more detail in the diagram on the next page (which also takes the
opportunity to invert the image to a more satisfying view).
13
14. The reference to Kurzweil epochs may not be appreciated by all readers. This is a rather extreme view of how
explosive human innovation may continue in the surprisingly-near future. Many people are very sceptical of these
predictions, but I would argue that bearing in mind the effects of Moore’s Law and the exponential innovation we
have seen in recent years, even if progress is not as fast as Kurzweil expects, software is headed for some big new
territory, and testing should be ready to boldly go there.
Biology
Leaving aside the particular technicalities of physics and chemistry, the most obvious part of the evolutionary saga is
the biological.
A way of appreciating evolution (admittedly not shared by everyone) is to consider it in two related dimensions:
over time, diversity has increased (though not regularly, as we will see); and
also, broadly, the sophistication of organisms has increased (with humankind being a spectacular recent
example).
This concept is illustrated in the following diagram (next page).
14
15. But it seems that evolution has not been smooth. Instead, there seem to be long periods of relative stability,
interrupted by sudden upheavals such as mass extinctions or explosions of new species:
It is outside the scope of this paper to go into details, but there are examples in other sciences (eg physics, chemistry)
of sudden emergences, eg those transformations known as phase changes.
The diagram on the next page illustrates this idea. The point of mentioning this in a paper about software testing is
that many people (including myself) see this kind of behaviour as a universal phenomenon. We could, and maybe
should, learn from it.
15
16. Relationship with other sciences
The theory of such sudden advances was likened by Per Bak to the avalanches that occur unpredictably when a pile of
sand is continually added to from above – suddenly a stable or metastable state gives way to widespread change.
2.2 Evolution of Software Testing
The view ahead
Again you may ask: what has this to do with software testing? Well, if you accept the idea of software testing as a
social science, you should be aware that social sciences (much of human history) is, like other sciences, subject to
punctuated equilibria. Another way of looking at the (Per Bak) avalanches is in terms of Gladwell’s “tipping points”.
Software testing has admittedly failed to keep up with advances in IT generally, and there are various ways out of this
situation. It could, as some have claimed, “die” – but what would that do for the quality of life of all those people who
depend on software? I would prefer to see us rise to the challenge, and help make the world not only a more complex
place but really a better place.
16
17. As IT has innovated explosively, it is worth the testing discipline taking a look ahead. For example, are we ready to test
artificial intelligence? (admittedly some lower forms of AI have been around and in use for a while, but when did you
last hear about them at a testing conference?).
The story so far
The table below represents my extrapolation of Gelperin & Hetzel’s historical analysis plus my recent interpretation of
the “schools of software testing” situation.
But what can my proposed analogies with science and nature contribute to this picture?
17
18. 2.3 Genes to Memes
One way of understanding the explosive transition from slow biological evolution to rapid human cultural evolution is
to consider replicating units of human knowledge and habits as analogous to the genes of DNA. These cultural units
were named “memes” by Richard Dawkins, and many authors since have argued about the accuracy and usefulness
(or not) of this analogy. The illustration immediately below is of genes as media of biological evolution.
The next diagram illustrates the analogy with memes. Memes are not so well-defined, but like genes they replicate
(though not as precisely) and they mutate (more often and more extravagantly?).
2.4 Memeplexes in the History of Testing
I am not the first author to claim a role for memes in software testing; the idea is already widespread on the internet.
But in the meme literature there is a concept termed a “memeplex” – being a collection of related and readily-
coexisting memes. it seems to me that memeplexes are a useful concept to understand software development
ecosystems and schools of software testing.
Below (next page) are two examples of what might be called software testing memeplexes.
18
19. The first is an old attempt by myself to represent what was then known as “software testing best practice”:
The second is an entirely different representation (though also by myself) – and this attempts to represent the
antithesis of software testing “best practices”, namely a context-driven thought structure:
So, do memeplexes really help in understanding the evolution of software testing overall? I think they do, but even
more illuminating I believe are the ideas of platforms, cranes and tipping points. A memeplex codifies an ecosystem
which has become established on a platform. The driving forces are arguably:
what are the cranes that get us to a new level, and the tipping points that make that lift respectable and
respected?
is this a single stream of evolution or are there multiple streams?
In the following diagram I take the Gelperin-Hetzel-based view of software testing history and attempt to express it in
the language of platforms, cranes and tipping points.
19
20. And another worry... here is a different view of the history (so far) of software testing.
Over the most recent few years, has innovation really almost stopped, or is there another explanation?
The diagram below (nest page) shows a different view of testing innovation: cause-effect-chained rather than mere
reportage. The bullet points on the right of the picture are closely related to the material I am about to present
regarding innovation. But how do those factors and aids really operate?
20
21. 2.5 Emergence between “Too Much Chaos” and “Too Much Order”
Now here is a new perspective on the initial ideas about evolution and emergence I expressed above. There are some
suggestions from the scientific literature that life evolves best on “the edge of chaos”:
2.6 Innovation and Ideas for Testing
A way of looking at testing (bearing in mind things I have said above) is to consider that it is part of an ecosystem with
development, but it lags slightly behind (or far behind, depending on your experience / opinion).
Development continually carves a path towards the “chaotic” end of the spectrum, because of market forces and the
typical personality mixes and cultures of programming groups. Conversely, testing tries to keep in step but is drawn
towards the “ordered” end of the spectrum by its typical tester psyche and the conservatism and risk-aversion of its
management.
I have tried to project the suspected tipping points I described above (psychology to method, method to art, art to
engineering etc) onto a swerving path between too much chaos and too much order.
21
22. There is communication between development and testing/quality disciplines, though development is in the lead.
In the platforms, cranes and tipping points illustration a few pages above, I questioned whether anything was wrong
with that picture. Hmm... I think there may be. My perception is that there have been essentially “two cultures” at
work here so far, not understanding each other well enough (see CP Snow, 1956, 1959 etc). The idea of “schools” of
software testing was introduced and publicised as part of the foundation of the Context-Driven School.
I suggest that, rather like testing lagging behind development, traditional testing has been lagging behind context-
driven. But I think that is at least partly due to the client business communities in finance and other traditional
markets having lagged behind the more modern business sectors. The main point however is that the two factions do
not communicate enough – more often they do not understand each other, agree to differ, or argue violently and
non-productively.
So, have I any suggestions to address this concern? Well, maybe...
Author Steven Johnson tells numerous stories of creativity and other innovation in some areas of commonality he has
identified (see diagram next page).
22
23. Johnson’s innovations are expressed as seven themes, introduced by the reef-city-web” concepts and wrapped up by
a survey of most significant human inventions in recent centuries.
The next diagram shows the specific innovation facilitators that aid innovation from platform to platform.
23
24. The conclusion of the book is that over recent centuries the pattern of innovative environments has changed
markedly (as illustrated below).
So, what are the lessons for software testing for all this? The table below gives some examples.
24
25. 3. VIVVAT Value-Inspired Verification, Validation And Testing
To renovate the Latin for “long may it live” – VIVVAT a Value-Inspired evolution of Verification, Validation and Testing.
We still need all three: if we go to the trouble of writing specifications and developing them from higher-level
documents, we need verification. And In this increasingly agile world, we need validation more and more. Testing
suffers from a “two cultures” difficulty, but I hope that science can turn out to be a unifying factor to enable us all to
work most effectively in our various contexts.
25
26. References and Acknowledgements
The sources below have been the primary inputs to this work. This is not a full bibliography, and may be expanded in
future versions of this paper.
I am particularly grateful to colleagues with whom some of these ideas have been developed, both within and outside
client project work – in particular:
Chris Comey of Testing Solutions Group, whose structure for risk-based testing made a useful and
complementary counterpart to the method which Paul Gerrard and I published in the 2002 book Risk-Based
E-Business Testing.
The Software Testing Retreat – a small informal semi-regular gathering started in the UK by EuroSTAR
regulars. In recent years this has grown to include some international friends. The original stimulus for the
Value Flow ScoreCards idea came from Mike Smith who was interested in testing’s role in IT projects’
“governance”, and the governance of testing itself. Isabel Evans was a major inspiration for my subsequent
scorecard ideas which integrated well with her views of quality. My joint presentation with Mike Smith
“Holistic Test Analysis & Design” at STARWest 2007 laid the foundations for the ScoreCard idea.
Stuart Reid has published material on Risk-Based Testing and on innovation in software testing which
contains some similar messages to those in this paper, and to which I have referred:
o The Five Major Challenges to Risk-Based Testing; and
o Lines of Innovation in Software Testing;
Scott Barber blogged some persuasive material in response to the “testing is dead” blogs, and now has a
scheme of mission-driven measurements which are aligned to value and risk (similar themes to this paper);
and
thanks to the Association for Software Testing, its members and the authors and teachers of the Black Box
Software Testing series of courses, with whom I have had many fruitful conversations. These have given me a
deeper insight into the principles and practices of the Context-Driven school of testing, and how those may
be used (where context demands) to more thoughtfully interpret and selectively apply various testing
methodologies of various degrees of formality and ceremony.
EuroSTAR 2012 T6 Neil Thompson Value-Inspired Testing v1_0.docx
26