Exploratory testing part 1
Download as pptx, pdf0 likes36 views
The document discusses exploratory testing and inattentional blindness, emphasizing that while humans can overlook obvious details due to focus, computers are inherently 'inattentional blind' by design. It highlights the need for a dynamic set of tests that adapt to new possibilities and risks, akin to investigative processes in crime scene analysis where judgment is crucial. The importance of context in testing is also mentioned, illustrating that testing operates within constraints influenced by various stakeholders' interests and objectives.
1 of 9
Download to read offline
Ad
Recommended
Fabian Scarano - Preparing Your Team for the Future
Fabian Scarano - Preparing Your Team for the FutureTEST Huddle The document discusses the future of testing teams and emphasizes the importance of both technical and soft skills, including communication, creativity, and emotional intelligence, as essential for competitive performance. It highlights the challenges posed by increasing customer demands, the need for rapid product cycles, and the complexities of testing service-oriented architectures (SOA). Ultimately, it underscores the necessity of team identity, trust, and efficacy in achieving effective inter-team collaboration in a diverse work environment.
Rikard Edgren - Testing is an Island - A Software Testing Dystopia
Rikard Edgren - Testing is an Island - A Software Testing DystopiaTEST Huddle This document summarizes trends in software testing that could diminish its effectiveness and enjoyment. It notes an increasing focus on verification over validation, precise measurement over subjective judgement, and short-term metrics over long-term quality. This narrowing scope risks making testers isolated and limiting their creativity, motivation and ability to consider the full context of a project. The document advocates a holistic and subjective approach that considers people and intangible factors, not just short-term quantifiable results. Subjectivity and considering the whole system, not just parts, are presented as useful for testing.
Graham Thomas - The Testers Toolbox - EuroSTAR 2010
Graham Thomas - The Testers Toolbox - EuroSTAR 2010TEST Huddle The workshop presented by Graham Thomas focuses on enhancing perception and comprehension through seven key, often overlooked tools applicable to software testing. Participants will learn about concepts like Popper's theory of testability, the Stroop effect, and the use of E-Prime to improve communication and understanding. The workshop aims to equip testers with practical techniques to adapt to the industry's shift toward more agile and exploratory approaches.
Estimations in Project Management
Estimations in Project ManagementIntaver Insititute George Banks made several mental errors when estimating the cost of his daughter's wedding in "The Father of the Bride". He wanted to spend as little as possible, so he ignored factors that would increase the cost like many guests and an expensive cake. He also used an irrelevant reference point (the cost of a house) rather than considering wedding-specific expenses. Additionally, he was overconfident since it was a one-day event at his house. To avoid problems, estimators should gather data from others, make a thorough initial estimate accounting for all known costs, and plan for uncertainties. Accurate project cost estimation is challenging due to biases, incomplete data, and other psychological factors.
Herman- Pieter Nijhof - Where Do Old Testers Go?
Herman- Pieter Nijhof - Where Do Old Testers Go?TEST Huddle The document discusses the career paths and future prospects for testers, emphasizing their increasing demand and underutilization despite common misconceptions about their role. It highlights the need for self-reflection and proactive initiative both from testers and employers to navigate career development. Additionally, it touches on how experienced testers bring unique perspectives and skills, contributing significantly to their field.
Estimates in Project Management
Estimates in Project ManagementIntaver Insititute The document discusses estimation errors in project management using the example of George Banks' unrealistic wedding cost estimate, highlighting psychological biases such as anchoring and overconfidence. It reviews various estimation pitfalls across different project types and emphasizes the importance of using accurate data and effective estimation processes. Additionally, the document suggests remedies for improving estimations, such as reality checks and independent assessments, while illustrating the sensitive nature of decision-making under uncertainty with a military example regarding the Iraq conflict.
Sigma Open Tech Week: Bitter Truth About Software Security
Sigma Open Tech Week: Bitter Truth About Software SecurityVlad Styran This document discusses common problems with how application security is implemented. It argues that software developers often lack security knowledge and focus on functionality over security. Security teams also lack development experience and focus on compliance over practical security. As a result, security is treated as an afterthought through ineffective practices like sole reliance on penetration testing. The document recommends a proper Secure Development Lifecycle approach involving security training, secure coding practices, testing and ongoing improvements.
Decision making - ims davv
Decision making - ims davv Abhishek Kandare The document outlines a seven-step decision-making process that includes identifying a problem, collecting relevant information, developing alternatives, evaluating each alternative, selecting the best solution, implementing the decision, and following up to evaluate outcomes. Each step emphasizes critical thinking and creativity, with an emphasis on gathering accurate information and assessing the effectiveness of solutions. The process aims to address discrepancies between current and desired states of affairs.
10 Guidelines for A/B Testing
10 Guidelines for A/B TestingEmily Robinson The document provides 10 guidelines for running effective A/B tests:
1. Have one key metric per experiment to clarify decision making.
2. Use your key metric to calculate statistical power and determine required sample size.
3. Run experiments for the planned duration without early stopping.
4. Don't search for differences across many segments to avoid false positives.
5. Ensure experiment groups are balanced to avoid bucketing issues.
6. Don't overcomplicate methods when basics suffice.
7. Be cautious launching changes that didn't hurt without evidence of benefit.
8. Involve data scientists in the entire process for better design and analysis.
9. Only analyze people actually exposed to variations
6 Guidelines for A/B Testing
6 Guidelines for A/B TestingEmily Robinson This document provides guidelines for A/B testing, including prioritizing test ideas based on estimated new conversions per day, creating tests by running a power analysis and having incremental tests, analyzing tests by monitoring health metrics, and making decisions carefully based on analysis results. It recommends calculating potential impact, having a data scientist involved, and not launching on neutral results to avoid technical debt.
5 whys nhsiq 2014
5 whys nhsiq 2014NHS Improving Quality The document provides an overview of the '5 Whys' root cause analysis tool, emphasizing its purpose of identifying the root causes of problems rather than solving them directly. It outlines a systematic approach to asking successive 'why' questions to get to the core of an issue, using clear definitions and examples to guide the process. The document also includes recommendations for accompanying tools and methods, as well as criteria to validate the analysis process.
A Guide to the Five Whys Technique
A Guide to the Five Whys TechniqueOlivier Serrat This document discusses the 'Five Whys' technique for root cause analysis, emphasizing the importance of identifying the true cause of problems through systematic questioning. It outlines key principles for effective use, including team collaboration, recording answers, and iterative questioning. Additionally, it acknowledges criticisms of the technique and suggests that proper facilitation can enhance its effectiveness in problem solving.
N=10^9: Automated Experimentation at Scale
N=10^9: Automated Experimentation at ScaleOptimizely The document discusses automated experimentation at Facebook, highlighting the rapid growth and need for better data science infrastructure since its inception in 2012. It outlines the challenges of running multiple experiments, including conflicting results, diverse metrics, and the necessity for centralized management and control tools to facilitate analysis. Key conclusions emphasize the importance of maintaining a strong experimentation culture alongside robust tools and clean data to ensure effective decision-making.
Preventing Information Flow with Jeeves - Singapore Data Privacy Workshop
Preventing Information Flow with Jeeves - Singapore Data Privacy Workshopjxyz The document presents Jean Yang's approach to preventing information leaks called Jeeves. Jeeves factors out security and privacy policies from application code to reduce opportunities for leaks. Programmers specify high-level policies about how sensitive data can flow rather than handling policies within code. The Jeeves runtime then automatically enforces policies to manage how information is released based on the viewer. This allows policy-agnostic programming while still providing formal guarantees about information flow.
'Happiness As Quality Measurement' by Jeroen de Cock
'Happiness As Quality Measurement' by Jeroen de CockTEST Huddle The document discusses the concept of happiness and its measurement, particularly in the context of user experience and software design. It emphasizes the importance of a subjective well-being approach and introduces various theories related to happiness, competence, relatedness, and autonomy. Additionally, it critiques software behavior while suggesting that effective interactions require a combination of personal accountability and understanding of user needs.
Let's test
Let's testkveronicka The document summarizes the agenda for the "Let's Test Context-Driven Software Testing Conference" in Stockholm, Sweden. The conference featured keynote speakers and tutorials on May 7-9, 2012 discussing context-driven testing approaches. Topics included stories-based testing, prioritizing bugs based on business impact, testing in unpredictable domains, moving beyond a pass/fail mindset, focusing on information over coverage metrics, and coaching other testers.
A Happy Marriage between Context-Driven and Agile
A Happy Marriage between Context-Driven and AgileIlari Henrik Aegerter The document discusses how to achieve a happy marriage between context-driven and agile approaches to software development and testing. It advocates for involving testers from the start of projects and having them work closely with developers as part of integrated teams. The document also provides advice on skills needed for testers, such as domain knowledge and a willingness to learn, and emphasizes pairing with other roles like developers to facilitate collaboration and knowledge sharing.
OWF14 - Plenary Session : David Jones, Chief Solutions Architect, Sonatype
OWF14 - Plenary Session : David Jones, Chief Solutions Architect, SonatypeParis Open Source Summit The document discusses the need for effective risk management in open source security, highlighting that many organizations lack formal policies and fail to track vulnerabilities in their components. It emphasizes the importance of having a strategy for open source use, making processes predictable and automated, and engaging skilled personnel to manage risks continuously. Participants reported breaches related to open source, underscoring the necessity of proactive measures in software development.
2014 11-25-sbc322-experiments
2014 11-25-sbc322-experimentsYannick Wurm This document discusses the importance of experimental design for ecological and evolutionary genomics experiments. It notes that poor experimental design can lead to insufficient or misleading data due to issues like pseudoreplication, confounding factors, or inappropriate analysis. The document advises considering factors like calibration of measurement tools, reducing subjective decision making, ensuring subjects are in natural conditions, and avoiding easy mistakes to create a robust experimental design. It also cautions that many types of experiments in ecological and evolutionary genomics, such as reference genome work, gene expression studies, field collections, population surveys, and identifying trait genes, have specific risks of going wrong if the experimental design is inadequate.
Machine Learning Vital Signs
Machine Learning Vital SignsDonald Miner The document discusses the importance of monitoring machine learning models in production using 'vital signs' metrics to ensure their effectiveness over time. It highlights potential challenges such as model drift, accuracy declines, and adversarial threats, proposing solutions like tracking accuracy, model agreement, output distribution, and human feedback. The overall aim is to create a robust monitoring framework that can quickly detect model failures and maintain performance.
Develop your inner tester
Develop your inner tester Anne-Marie Charrett This document provides guidance on developing a tester mindset and strategies for effective testing. It discusses developing an analytical eye for detail and skeptical approach. It emphasizes avoiding confirmation bias by testing to disprove hypotheses rather than just verify them. It also stresses generating new testing ideas by considering different customer models and perspectives. Finally, it discusses prioritizing testing based on risk factors like new features, complexity, critical functions and upstream/downstream dependencies. The overall message is the importance of strategic and logical thinking to structure effective testing.
Rita Bush - How to Use Games to Mitigate Cognitive Bias in Analysis
Rita Bush - How to Use Games to Mitigate Cognitive Bias in AnalysisSeriousGamesAssoc The IARPA's Sirius program aims to use serious games to train intelligence analysts in recognizing and mitigating cognitive biases, promoting experiential learning and repetition. Research indicates that game-based training can effectively improve bias mitigation, with studies showing that participants who played games outperformed those who only watched videos. The findings challenge common myths about training effectiveness related to gamer experience and graphic fidelity.
Information Technology - Discover the Root Cause and Develop a solution throu...
Information Technology - Discover the Root Cause and Develop a solution throu...John Hudson The document discusses incident investigation methodologies emphasizing the importance of changing the questions asked during investigations rather than altering personnel. It outlines three critical skills for effective investigations: service recovery analysis, technical cause analysis, and root cause analysis, along with examples from various clients. Additionally, it highlights the significance of specificity in identifying problems to improve incident resolution processes.
Testing in the Wild
Testing in the WildDawn Code This document discusses strategies for handling non-ideal testing situations when adopting agile practices. It addresses problems like lack of test automation, test data issues, legacy reporting needs, geographic distribution of teams, and separation of testers and programmers. The proposed solutions generally involve starting small, using technology to facilitate remote collaboration, targeting important information in reports, and developing relationships between team members.
Deductive reasoning and logic
Deductive reasoning and logicBlancoScience Crime scene analysis involves making observations that lead to questions, then using logic and deductive reasoning to reach conclusions. Deductive reasoning assembles evidence to logically deduce an explanation, like concluding a body was moved based on limited blood at the scene. Sound reasoning considers all factors to avoid false conclusions, while suspicious yet objective analysis helps solve crimes.
Root Cause Analysis
Root Cause AnalysisSunderland City Council This document outlines a 5-step process for performing a root cause analysis: 1) Define the problem by describing symptoms and what is observed. 2) Collect data on how long the problem has existed, its impact, and different perspectives using a CATWOE analysis. 3) Identify possible causal factors using tools like appreciation, 5 whys, drill down, and cause-and-effect diagrams. 4) Identify the root cause of why the causal factor exists. 5) Recommend and implement solutions to prevent future occurrences, assign responsibilities, and manage risks, using continuous improvement strategies like kaizen. It provides an example task to diagnose a network printing problem at CycleWorld using this root cause analysis model.
Five whys summary
Five whys summarySteve Hayes The document discusses the 5 Whys analysis technique, which helps identify the root causes of problems by asking 'why' five times. It emphasizes the importance of seeing issues as learning opportunities rather than crises, involving all relevant parties in the analysis, and implementing proportional corrective actions. Key insights include the need for specific problem identification, fostering a blame-free environment, and ensuring effective communication of findings across the organization.
SkillSwap Weekend - Usability Testing
SkillSwap Weekend - Usability Testingschaef2493 This document discusses usability testing. It defines usability testing as a method of directly observing users to evaluate the ease of use of a system. Usability is defined by factors like learnability, efficiency, and satisfaction. Usability testing should be done early and often using representative tasks and users. During testing, users are asked to think aloud to reveal their thought processes while using the interface. The results provide insights into how users interpret the UI that can be used to improve usability.
Test Strategy-The real silver bullet in testing by Matthew Eakin
Test Strategy-The real silver bullet in testing by Matthew EakinQA or the Highway This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing a
Exploratory Testing Explained
Exploratory Testing ExplainedTechWell The document discusses exploratory testing, emphasizing it as a structured and purposeful approach rather than mere 'playing around.' It highlights the importance of providing respect for exploratory testers by teaching techniques for effective bug isolation, documentation, and reporting. Key concepts include understanding testing missions, session-based exploration, and the need for testers to adaptively navigate their testing environment for optimal results.
More Related Content
What's hot (20)
10 Guidelines for A/B Testing
10 Guidelines for A/B TestingEmily Robinson The document provides 10 guidelines for running effective A/B tests:
1. Have one key metric per experiment to clarify decision making.
2. Use your key metric to calculate statistical power and determine required sample size.
3. Run experiments for the planned duration without early stopping.
4. Don't search for differences across many segments to avoid false positives.
5. Ensure experiment groups are balanced to avoid bucketing issues.
6. Don't overcomplicate methods when basics suffice.
7. Be cautious launching changes that didn't hurt without evidence of benefit.
8. Involve data scientists in the entire process for better design and analysis.
9. Only analyze people actually exposed to variations
6 Guidelines for A/B Testing
6 Guidelines for A/B TestingEmily Robinson This document provides guidelines for A/B testing, including prioritizing test ideas based on estimated new conversions per day, creating tests by running a power analysis and having incremental tests, analyzing tests by monitoring health metrics, and making decisions carefully based on analysis results. It recommends calculating potential impact, having a data scientist involved, and not launching on neutral results to avoid technical debt.
5 whys nhsiq 2014
5 whys nhsiq 2014NHS Improving Quality The document provides an overview of the '5 Whys' root cause analysis tool, emphasizing its purpose of identifying the root causes of problems rather than solving them directly. It outlines a systematic approach to asking successive 'why' questions to get to the core of an issue, using clear definitions and examples to guide the process. The document also includes recommendations for accompanying tools and methods, as well as criteria to validate the analysis process.
A Guide to the Five Whys Technique
A Guide to the Five Whys TechniqueOlivier Serrat This document discusses the 'Five Whys' technique for root cause analysis, emphasizing the importance of identifying the true cause of problems through systematic questioning. It outlines key principles for effective use, including team collaboration, recording answers, and iterative questioning. Additionally, it acknowledges criticisms of the technique and suggests that proper facilitation can enhance its effectiveness in problem solving.
N=10^9: Automated Experimentation at Scale
N=10^9: Automated Experimentation at ScaleOptimizely The document discusses automated experimentation at Facebook, highlighting the rapid growth and need for better data science infrastructure since its inception in 2012. It outlines the challenges of running multiple experiments, including conflicting results, diverse metrics, and the necessity for centralized management and control tools to facilitate analysis. Key conclusions emphasize the importance of maintaining a strong experimentation culture alongside robust tools and clean data to ensure effective decision-making.
Preventing Information Flow with Jeeves - Singapore Data Privacy Workshop
Preventing Information Flow with Jeeves - Singapore Data Privacy Workshopjxyz The document presents Jean Yang's approach to preventing information leaks called Jeeves. Jeeves factors out security and privacy policies from application code to reduce opportunities for leaks. Programmers specify high-level policies about how sensitive data can flow rather than handling policies within code. The Jeeves runtime then automatically enforces policies to manage how information is released based on the viewer. This allows policy-agnostic programming while still providing formal guarantees about information flow.
'Happiness As Quality Measurement' by Jeroen de Cock
'Happiness As Quality Measurement' by Jeroen de CockTEST Huddle The document discusses the concept of happiness and its measurement, particularly in the context of user experience and software design. It emphasizes the importance of a subjective well-being approach and introduces various theories related to happiness, competence, relatedness, and autonomy. Additionally, it critiques software behavior while suggesting that effective interactions require a combination of personal accountability and understanding of user needs.
Let's test
Let's testkveronicka The document summarizes the agenda for the "Let's Test Context-Driven Software Testing Conference" in Stockholm, Sweden. The conference featured keynote speakers and tutorials on May 7-9, 2012 discussing context-driven testing approaches. Topics included stories-based testing, prioritizing bugs based on business impact, testing in unpredictable domains, moving beyond a pass/fail mindset, focusing on information over coverage metrics, and coaching other testers.
A Happy Marriage between Context-Driven and Agile
A Happy Marriage between Context-Driven and AgileIlari Henrik Aegerter The document discusses how to achieve a happy marriage between context-driven and agile approaches to software development and testing. It advocates for involving testers from the start of projects and having them work closely with developers as part of integrated teams. The document also provides advice on skills needed for testers, such as domain knowledge and a willingness to learn, and emphasizes pairing with other roles like developers to facilitate collaboration and knowledge sharing.
OWF14 - Plenary Session : David Jones, Chief Solutions Architect, Sonatype
OWF14 - Plenary Session : David Jones, Chief Solutions Architect, SonatypeParis Open Source Summit The document discusses the need for effective risk management in open source security, highlighting that many organizations lack formal policies and fail to track vulnerabilities in their components. It emphasizes the importance of having a strategy for open source use, making processes predictable and automated, and engaging skilled personnel to manage risks continuously. Participants reported breaches related to open source, underscoring the necessity of proactive measures in software development.
2014 11-25-sbc322-experiments
2014 11-25-sbc322-experimentsYannick Wurm This document discusses the importance of experimental design for ecological and evolutionary genomics experiments. It notes that poor experimental design can lead to insufficient or misleading data due to issues like pseudoreplication, confounding factors, or inappropriate analysis. The document advises considering factors like calibration of measurement tools, reducing subjective decision making, ensuring subjects are in natural conditions, and avoiding easy mistakes to create a robust experimental design. It also cautions that many types of experiments in ecological and evolutionary genomics, such as reference genome work, gene expression studies, field collections, population surveys, and identifying trait genes, have specific risks of going wrong if the experimental design is inadequate.
Machine Learning Vital Signs
Machine Learning Vital SignsDonald Miner The document discusses the importance of monitoring machine learning models in production using 'vital signs' metrics to ensure their effectiveness over time. It highlights potential challenges such as model drift, accuracy declines, and adversarial threats, proposing solutions like tracking accuracy, model agreement, output distribution, and human feedback. The overall aim is to create a robust monitoring framework that can quickly detect model failures and maintain performance.
Develop your inner tester
Develop your inner tester Anne-Marie Charrett This document provides guidance on developing a tester mindset and strategies for effective testing. It discusses developing an analytical eye for detail and skeptical approach. It emphasizes avoiding confirmation bias by testing to disprove hypotheses rather than just verify them. It also stresses generating new testing ideas by considering different customer models and perspectives. Finally, it discusses prioritizing testing based on risk factors like new features, complexity, critical functions and upstream/downstream dependencies. The overall message is the importance of strategic and logical thinking to structure effective testing.
Rita Bush - How to Use Games to Mitigate Cognitive Bias in Analysis
Rita Bush - How to Use Games to Mitigate Cognitive Bias in AnalysisSeriousGamesAssoc The IARPA's Sirius program aims to use serious games to train intelligence analysts in recognizing and mitigating cognitive biases, promoting experiential learning and repetition. Research indicates that game-based training can effectively improve bias mitigation, with studies showing that participants who played games outperformed those who only watched videos. The findings challenge common myths about training effectiveness related to gamer experience and graphic fidelity.
Information Technology - Discover the Root Cause and Develop a solution throu...
Information Technology - Discover the Root Cause and Develop a solution throu...John Hudson The document discusses incident investigation methodologies emphasizing the importance of changing the questions asked during investigations rather than altering personnel. It outlines three critical skills for effective investigations: service recovery analysis, technical cause analysis, and root cause analysis, along with examples from various clients. Additionally, it highlights the significance of specificity in identifying problems to improve incident resolution processes.
Testing in the Wild
Testing in the WildDawn Code This document discusses strategies for handling non-ideal testing situations when adopting agile practices. It addresses problems like lack of test automation, test data issues, legacy reporting needs, geographic distribution of teams, and separation of testers and programmers. The proposed solutions generally involve starting small, using technology to facilitate remote collaboration, targeting important information in reports, and developing relationships between team members.
Deductive reasoning and logic
Deductive reasoning and logicBlancoScience Crime scene analysis involves making observations that lead to questions, then using logic and deductive reasoning to reach conclusions. Deductive reasoning assembles evidence to logically deduce an explanation, like concluding a body was moved based on limited blood at the scene. Sound reasoning considers all factors to avoid false conclusions, while suspicious yet objective analysis helps solve crimes.
Root Cause Analysis
Root Cause AnalysisSunderland City Council This document outlines a 5-step process for performing a root cause analysis: 1) Define the problem by describing symptoms and what is observed. 2) Collect data on how long the problem has existed, its impact, and different perspectives using a CATWOE analysis. 3) Identify possible causal factors using tools like appreciation, 5 whys, drill down, and cause-and-effect diagrams. 4) Identify the root cause of why the causal factor exists. 5) Recommend and implement solutions to prevent future occurrences, assign responsibilities, and manage risks, using continuous improvement strategies like kaizen. It provides an example task to diagnose a network printing problem at CycleWorld using this root cause analysis model.
Five whys summary
Five whys summarySteve Hayes The document discusses the 5 Whys analysis technique, which helps identify the root causes of problems by asking 'why' five times. It emphasizes the importance of seeing issues as learning opportunities rather than crises, involving all relevant parties in the analysis, and implementing proportional corrective actions. Key insights include the need for specific problem identification, fostering a blame-free environment, and ensuring effective communication of findings across the organization.
SkillSwap Weekend - Usability Testing
SkillSwap Weekend - Usability Testingschaef2493 This document discusses usability testing. It defines usability testing as a method of directly observing users to evaluate the ease of use of a system. Usability is defined by factors like learnability, efficiency, and satisfaction. Usability testing should be done early and often using representative tasks and users. During testing, users are asked to think aloud to reveal their thought processes while using the interface. The results provide insights into how users interpret the UI that can be used to improve usability.
Similar to Exploratory testing part 1 (20)
Test Strategy-The real silver bullet in testing by Matthew Eakin
Test Strategy-The real silver bullet in testing by Matthew EakinQA or the Highway This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing a
Exploratory Testing Explained
Exploratory Testing ExplainedTechWell The document discusses exploratory testing, emphasizing it as a structured and purposeful approach rather than mere 'playing around.' It highlights the importance of providing respect for exploratory testers by teaching techniques for effective bug isolation, documentation, and reporting. Key concepts include understanding testing missions, session-based exploration, and the need for testers to adaptively navigate their testing environment for optimal results.
Michał Stryjak, Poznaj Context-Driven Testing
Michał Stryjak, Poznaj Context-Driven TestingFuture Processing This document discusses context-driven testing, emphasizing its origins, principles, and significance in software testing. It highlights that context-driven testing focuses on tailoring testing practices to the specific context of a project rather than adhering to standardized 'best practices.' The document also contrasts context-driven testing with agile methodologies, noting that while they share similarities, context-driven testing is not inherently linked to agile development.
Caveon Webinar Series - Lessons Learned from Using Statistics to Invalidate ...
Caveon Webinar Series - Lessons Learned from Using Statistics to Invalidate ...Caveon Test Security The document summarizes a webinar discussing using statistics to invalidate test scores due to potential cheating. It includes questions from a moderator and answers from a panel on topics like the process for invalidating scores, types of statistics most useful for identifying cheating, challenges faced in implementing invalidation programs, and legal considerations around invalidations. The webinar emphasized having policies in place before conducting analyses and treating all similar cases consistently.
Michael Bolton - Two Futures of Software Testing
Michael Bolton - Two Futures of Software TestingTEST Huddle The document presents two contrasting futures for software testing, highlighting a 'dark future' characterized by rigid processes, control, and reliance on automation, versus a 'bright future' that emphasizes tester skill, adaptability, and collaboration. It advocates for a context-driven approach where testing serves as a valuable information source for stakeholders and promotes critical thinking applied to testing processes. Ultimately, it integrates a call for testers to embrace flexibility and maintain a focus on quality through continuous questioning and learning.
Supporting innovation in insurance with randomized experimentation
Supporting innovation in insurance with randomized experimentationDomino Data Lab The document discusses the importance of randomized experimentation in the insurance sector, highlighting its effectiveness for assessing the impact of innovations on customer experience. It outlines essential considerations for experimental design, such as statistical power, cognitive biases, and the need for rapid iteration during the testing process. The conclusion emphasizes that despite operational challenges, wider adoption of this methodology can create significant value within insurance firms.
Lean Startup 301
Lean Startup 301Lean Startup Co. The Lean Startup workshop, led by Aubrey Smith, focuses on helping entrepreneurs systematically address uncertainty through rapid iteration, validated learning, and practical application of concepts like MVPs (Minimum Viable Products). Participants will engage in hands-on exercises and case studies, exploring key ideas from the Lean Startup philosophy, such as governance, customer learning, and innovation accounting, to create successful growth-driven companies. The session aims to provide actionable insights for innovators at various experience levels, emphasizing collaboration and continuous improvement.
Santa Barbara Agile: Exploratory Testing Explained and Experienced
Santa Barbara Agile: Exploratory Testing Explained and ExperiencedMaaret Pyhäjärvi Exploratory Testing Explained and Experienced
- Exploratory testing is an approach to software testing that involves dynamically testingsoftware without a fixed plan, using the results of previous tests to determine subsequent tests.
- It is a disciplined approach that finds unknown unknowns and helps testers examine software from different perspectives to uncover more bugs. Tests are performances rather than fixed artifacts.
- Exploratory testing requires testers to be able to strategically choose and defend their test approaches, explain what they have tested, and determine when they are done testing rather than just finding bugs randomly. It is a more systematic approach than unplanned testing.
Cognifide content usabilitytesting-csa2017-v0.1
Cognifide content usabilitytesting-csa2017-v0.1Kate Kenyon Kate Kenyon gave a presentation on content usability testing. She discussed testing content to identify gaps between strategy and practice, using results to inform decisions, and keeping stakeholders aligned. Testing provides quantifiable data on how content performs and business value. The goal is a regular testing process to gather usable data. Testing is part of a cycle of planning, making, testing, reviewing, and publishing content. Old processes plus some testing are insufficient; processes need to change first.
She provided examples of how she conducts testing, including mapping the landscape, prioritizing what to test, writing test cases, running tests, and reporting results. A case study described testing a bank's intranet to evaluate how well it supported global
A Rapid Introduction to Rapid Software Testing
A Rapid Introduction to Rapid Software TestingTechWell This document presents a comprehensive introduction to rapid software testing, authored by Michael Bolton and highlights a testing methodology aimed at efficiently detecting significant software issues under uncertain conditions and time constraints. It details the principles of rapid testing, emphasizing collaboration in diverse teams and the importance of heuristics and oracles for recognizing problems. Notable concepts include the need for effective communication with stakeholders and using lightweight testing processes to maximize value while minimizing costs.
A Rapid Introduction to Rapid Software Testing
A Rapid Introduction to Rapid Software TestingTechWell This document provides a summary of a presentation on Rapid Software Testing. The presentation was given by Michael Bolton of DevelopSense and covered the methodology and mindset of rapid software testing. It emphasizes testing software expertly under uncertainty and time pressure. The presentation defines rapid testing as testing more quickly and less expensively while still achieving excellent results. It compares rapid testing to other approaches like exhaustive, ponderous, and slapdash testing. The presentation also discusses principles of rapid testing, how to recognize problems quickly using heuristics, and testing rapidly to fulfill the mission of testing.
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of TestingHo Chi Minh City Software Testing Club The document discusses the perceived value of software testing and the communication gap between testers and project managers at Megacorp, highlighting that testers are often seen as a nuisance rather than a valuable resource. It emphasizes the importance of quantifying the value of testing through meaningful metrics that align with the goals of various stakeholders in the software development process. The author advocates for a focus on delivering valuable information that aids decision-making to justify testing efforts and improve product quality.
Exploratory Testing Explained and Experienced
Exploratory Testing Explained and ExperiencedMaaret Pyhäjärvi 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.
Exploratory testing
Exploratory testingHuib Schoots 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.
Uncertain Knowledge and Reasoning in Artificial Intelligence
Uncertain Knowledge and Reasoning in Artificial IntelligenceExperfy The document outlines a course on artificial intelligence focusing on reasoning under uncertainty, presented by Dr. Andreas Haja, a professor with over 10 years of experience in AI. It covers relevant topics such as probability theory, Bayesian networks, and inference, emphasizing hands-on examples and practical applications especially in autonomous driving. The course aims to equip participants with essential AI tools and methods for decision-making in uncertain environments across various industries.
Fundamentals_of_Software_testing.pptx
Fundamentals_of_Software_testing.pptxMusaBashir9 The document provides an overview of software testing fundamentals including definitions of testing, why testing is necessary, quality versus testing, general testing vocabulary, testing objectives, and general testing principles. It defines software testing as verifying and validating that software meets requirements, works as expected, and discusses how testing is needed because humans make mistakes and software errors can have expensive and dangerous consequences. The document also provides definitions of quality, contrasts popular versus technical views of quality, and outlines key aspects of quality like functionality, reliability, and value.
Software Testing 2/5
Software Testing 2/5Damian T. Gordon Damian Gordon was a Dutch computer scientist born in 1930 in Rotterdam who received the 1972 Turing Award. He developed several programming language principles including that testing shows presence of bugs but not absence, exhaustive testing is impossible, early testing is important, and defects often cluster in small areas of code. He stressed the importance of risk analysis, test objectives, and regularly updating test cases to find new issues rather than relying on the same cases. Testing approaches must also be tailored to contexts like safety-critical systems versus ecommerce.
Dare to Explore: Discover ET!
Dare to Explore: Discover ET!Raj Indugula The document discusses exploratory testing (ET) as a flexible and adaptive testing approach that allows testers to learn about the software while designing and executing tests without rigid scripts. It highlights ET's fit within agile contexts, its ability to surface risks quickly, and its role in complementing conventional testing methods. Challenges and solutions for transitioning to an exploratory testing mindset are also examined, emphasizing the importance of creativity and collaboration among testers.
A Rapid Introduction to Rapid Software Testing
A Rapid Introduction to Rapid Software TestingTechWell El tutorial 'Una introducción rápida a las pruebas de software rápidas', presentado por Paul Holland, aborda la eficiencia en las pruebas de software, enfatizando la importancia de una mentalidad adaptativa y habilidades prácticas. Se destacan premisas como la relación entre proyectos de software y personas, y la necesidad de pruebas rápidas que identifiquen problemas importantes bajo condiciones de incertidumbre y presión de tiempo. Además, se discuten heurísticas y oráculos como herramientas para reconocer problemas durante el proceso de prueba.
Penetration testing services
Penetration testing servicesAlisha Henderson This document discusses important factors to consider when investing in penetration testing services, including hiring an experienced testing team, clearly defining the scope of the test, understanding the benefits of blackbox vs whitebox testing, setting goals and objectives for the test, ensuring recommendations are provided in the report, and properly scheduling test events.
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of Testing
[HCMC STC Jan 2015] Proving Our Worth Quantifying The Value Of TestingHo Chi Minh City Software Testing Club
Ad
More from Dawn Code (16)
Executable Specifications with FitNesse and Selenium
Executable Specifications with FitNesse and SeleniumDawn Code Dawn Cannan is a QA manager who has been in software testing for 10 years. She will discuss executable specifications using FitNesse and Selenium. She will demonstrate how to create automated tests using these tools and the test automation pyramid. She will also reference her blog and links to learn more about FitNesse, Selenium, and her Selenesse open source project.
Executable Specifications with FitNesse and Selenium
Executable Specifications with FitNesse and SeleniumDawn Code This document discusses using executable specifications with FitNesse and Selenium to minimize miscommunications between business and development teams. It introduces Dawn Cannan and describes the Test Automation Pyramid. Key points covered include defining examples as tests to get everyone on the same page early, preventing bugs, and challenges of test automation in the browser like locating elements and synchronization. The FitNesse framework is presented as a way to define Selenium tests in a wiki accessible to all team members.
A Sampling of Tools
A Sampling of ToolsDawn Code This document provides an overview of common tools used for test automation, including frameworks, runners, drivers, reporting tools and build systems. It discusses factors to consider like the technology stack, skills of those writing and running tests, and how test results will be viewed. Popular automation stacks like HP QTP, FitNesse, Eclipse/JUnit/Selenium/Hudson and Cucumber are described. UI drivers like Selenium, Watir and desktop testing tools are also covered. Common challenges around test design, organization and synchronization are discussed along with approaches to address them.
Fitting Organizational Structure
Fitting Organizational StructureDawn Code This document discusses how to fit organizational structure into an agile team when the team is not fully cohesive. It addresses common issues like separate testing teams, lack of collaboration, and remote or offshore team members. The document provides suggestions for improving communication and collaboration even when organizational barriers exist, such as walking over to other teammates' desks, communicating through documentation, and discussing testing needs early in development. The overall message is that teams can still benefit from agile practices even if the organizational structure is not perfectly aligned.
Pair development
Pair developmentDawn Code This document discusses how pairing programmers and testers during development benefits both roles. Pairing helps minimize customer feedback time, prevents defects, defines what "done" means for a task, prevents confusion, and expands the benefits of test-driven development throughout the development cycle. The document was presented by Dawn Cannan and Shannon Prue at the Agile Development Practices West 2011 conference on pairing roles and customer-driven development.
Remote Dev/Test Pairing
Remote Dev/Test PairingDawn Code This document summarizes a presentation about remote pairing of developers and testers using distributed tools. It discusses how pairing helps build shared understanding and teaches skills in both directions. An example setup uses Mikogo, Skype, webcam and headset to enable remote pairing at low cost. The presentation demonstrates a wiki framework for Cucumber acceptance tests, built with Ruby on Rails and Cucumber. Remote pairing works well after an initial adjustment period.
Crowdsource Your Career
Crowdsource Your CareerDawn Code The document provides tips for crowdsourcing one's career and standing out, including using social media to share opinions and struggles, developing a network by interacting with others in one's field, and avoiding pitfalls like not sharing ideas or keeping personal social media public.
How Low Can Your Tests Go
How Low Can Your Tests GoDawn Code TISQA 2018 conference, discussing strategies for determining which level of test automation that tests should go.
Writing Maintainable Test Automation
Writing Maintainable Test AutomationDawn Code The document discusses best practices for writing maintainable test automation code, emphasizing that automation code should be human-readable and follow clean coding principles. It suggests avoiding common pitfalls like code repetition and encourages meaningful naming conventions to enhance clarity. The balance between maintaining clean code and managing the cost of refactoring is highlighted as essential for effective test automation.
Exploratory testing part 2
Exploratory testing part 2Dawn Code The document provides an overview of exploratory testing in an agile context, defining it as a simultaneous process of learning and testing. It emphasizes the importance of understanding system nouns and verbs, creating context diagrams, and utilizing heuristics to guide exploration. Additionally, it introduces the concept of charters for focused testing sessions and outlines the structure of session reports.
Exploratory testing part 3
Exploratory testing part 3Dawn Code This document discusses various techniques for exploratory testing, including thinking outside the box when testing. It provides examples of riddles and clues to stimulate new perspectives, and suggests pretending to take on different user roles to test from various viewpoints. The document also outlines heuristics like HICCUPS and considerations for testing various elements of a product like structure, function, and interfaces. It concludes with an exploratory testing dice roll technique to help guide exploratory sessions.
Agile and Exploratory Testing Jeopardy
Agile and Exploratory Testing JeopardyDawn Code The document outlines various categories related to product elements, quality elements, agile concepts, and types of data in the context of software testing and development. It includes a series of questions and answers associated with these topics, highlighting crucial terms such as reliability, usability, and business value. Additionally, it references key figures in the software industry and their contributions to testing and agile methodologies.
Pair Development from the Trenches
Pair Development from the TrenchesDawn Code The document discusses various aspects of pair development and programming, emphasizing the roles of developers and testers in writing code and conducting testing. It highlights the overlap in skills between developers and testers, focusing on unit tests, integration tests, and exploratory testing. The document also includes links to further learning resources and test heuristics.
Page objects: the good, the bad, the ugly
Page objects: the good, the bad, the uglyDawn Code The document discusses page objects in software testing, emphasizing the need for clean, maintainable code that is human-readable and conveys intent. It highlights best practices like meaningful naming and the DRY principle while addressing the complications of complex page objects. The content concludes with recommended resources for further reading on automated testing and page object design.
Testing Legacy Apps Mindmap
Testing Legacy Apps MindmapDawn Code Mindmap I created while defining my presentation for Agile Worlds 2010
Testing Legacy Apps
Testing Legacy AppsDawn Code The document discusses testing challenges for teams transitioning to agile and provides recommendations for addressing them. It recommends starting with automating frequent, time-consuming tasks to "stop the bleeding". It also suggests beginning pair testing and programming to facilitate collaboration between testers and developers. The document advocates filling in test automation over time using the test automation pyramid and testing quadrants frameworks as guides.
Ad
Recently uploaded (20)
declaration of Variables and constants.pptx
declaration of Variables and constants.pptxmeemee7378 Rules of declaration of variables and constants
A Guide to Telemedicine Software Development.pdf
A Guide to Telemedicine Software Development.pdfOlivero Bozzelli Learn how telemedicine software is built from the ground up—starting with idea validation, followed by tech selection, feature integration, and deployment.
Know more about this: https://www.yesitlabs.com/a-guide-to-telemedicine-software-development/
Streamlining CI/CD with FME Flow: A Practical Guide
Streamlining CI/CD with FME Flow: A Practical GuideSafe Software Join us as we explore how to deploy a fault-tolerant FME Flow installation using FME Flow’s IaC templates alongside Terraform, AWS, and GitHub in a CI/CD workflow. This session will also cover how to leverage FME’s CI/CD capabilities for FME Flow upgrades and FME object migration between different environments, ensuring seamless automation and scalability.
Test Case Design Techniques – Practical Examples & Best Practices in Software...
Test Case Design Techniques – Practical Examples & Best Practices in Software...Muhammad Fahad Bashir This presentation was part of the SQA & PM Bootcamp, where I served as a trainer. It focuses on effective test case design techniques, blending theoretical knowledge with practical application, especially useful for manual testers and QA beginners.
Video Lecture Recording : https://www.facebook.com/share/v/1Z44DiXN5v/
What’s Covered:
🧾 Definition and Purpose of Test Case Design
🚀 Importance of Structured Test Design
🧠 Test Case Design Techniques Overview:
✅ Black Box Techniques
✅ White Box Techniques
✅ Experience-Based Techniques
📝 Manual Test Case Design in Detail
🔐 Real-World Example: Login Page Test Case
🧩 Black Box Methods Explained with Examples:
Equivalence Partitioning (EP)
Boundary Value Analysis (BVA)
Difference Between EP & BVA
📊 Decision Table Testing
💡 Experience-Based Testing: Error Guessing, Exploratory Testing
📂 White Box Techniques (Introductory Overview)
➕ Much More to Help You Build Strong Manual Testing Skills
This resource is especially helpful for students, aspiring QA professionals, and junior testers looking to master test design fundamentals with clarity and practical insight.
Sysinfo OST to PST Converter Infographic
Sysinfo OST to PST Converter InfographicSysInfo Tools The SysInfo OST to PST Converter is the most secure software to perform the OST to PST conversion. It converts OST files into various formats, including MBOX, EML, EMLX, HTML, and CSV, with 100% accuracy. Along with that, it imports OST files into different email clients like Office 365 and G Suite.
visit: https://www.sysinfotools.com/ost-to-pst-converter.php
Why Edge Computing Matters in Mobile Application Tech.pdf
Why Edge Computing Matters in Mobile Application Tech.pdfIMG Global Infotech This PDF explores the critical role of edge computing in modern mobile application technology. Learn how edge enhances app speed, reduces latency, improves data privacy, and supports real-time performance. Ideal for developers, tech strategists, and mobile innovators looking to stay ahead in the evolving mobile ecosystem.
IObit Driver Booster Pro 12 Crack Latest Version Download
IObit Driver Booster Pro 12 Crack Latest Version Downloadpcprocore 👉𝗡𝗼𝘁𝗲:𝗖𝗼𝗽𝘆 𝗹𝗶𝗻𝗸 & 𝗽𝗮𝘀𝘁𝗲 𝗶𝗻𝘁𝗼 𝗚𝗼𝗼𝗴𝗹𝗲 𝗻𝗲𝘄 𝘁𝗮𝗯🔴▶ https://pcprocore.com/ ◀✅
IObit Driver Booster Pro is the solution. It automatically downloads and updates drivers with just one click, avoiding hardware failures, system instability, and security vulnerabilities.
Threat Modeling a Batch Job Framework - Teri Radichel - AWS re:Inforce 2025
Threat Modeling a Batch Job Framework - Teri Radichel - AWS re:Inforce 20252nd Sight Lab This presentation is similar to another presentation I gave earlier in the year at the AWS Community Security Day, except that I had less time to present and incorporated some AI slides into the presentation. In this presentation I explain what batch jobs are, how to use them, and that AI Agents are essentially batch jobs. All the same security controls that apply to batch jobs also apply to AI agents. In addition, we have more concerns with AI agents because AI is based on a statistical model. That means that depending on where and how AI is used we lose some of the reliability that we would get from a traditional batch job. That needs to be taken into consideration when selecting how and when to use AI Agents as batch jobs and whether we should use AI to trigger an Agent. As I mention on one side - I don't want you to predict what my bank statement should look like. I want it to be right! By looking at various data breaches we can determine how those attacks worked and whether the system we are building is susceptible to a similar attack or not.
ERP Systems in the UAE: Driving Business Transformation with Smart Solutions
ERP Systems in the UAE: Driving Business Transformation with Smart Solutionsdheeodoo ERP solutions are driving innovative change for businesses across the UAE through improved efficiency, reduced operational costs, and provide real-time visibility of operational data. By offering native Arabic language support, VAT compliance, and some level of cloud readiness, ERP solutions also supports and are consistent with the initiative for Smart Dubai 2030. Odoo is an example of a flexible & scalable solution. If you're looking for expert support with implementation contact Banibro. www.banibro.com
Y - Recursion The Hard Way GopherCon EU 2025
Y - Recursion The Hard Way GopherCon EU 2025Eleanor McHugh In most modern programming languages, including Go, it's possible for a function to call itself recursively. It's such a mainstream technique that we've come to take it for granted.
But what if functions couldn't call themselves?
There's a branch of mathematics called Combinatorics which answers just these kinds of questions, and this presentation takes these ideas and phrases them in Go to teach a deeper view of computation through the medium of code.
Download Adobe Illustrator Crack free for Windows 2025?
Download Adobe Illustrator Crack free for Windows 2025?grete1122g COPY & PASTE LINK 👉👉👉 https://click4pc.com/after-verification-click-go-to-download-page/
Adobe Illustrator CC Crack will make your illustration level upgrade by moving toward real modification purpose using adobe pro tools there ..
Modern Platform Engineering with Choreo - The AI-Native Internal Developer Pl...
Modern Platform Engineering with Choreo - The AI-Native Internal Developer Pl...WSO2 Building and operating internal platforms has become increasingly complex — sprawling toolchains, rising costs, and fragmented developer experiences are slowing teams down. It’s time for a new approach.
This slide deck explores modern platform engineering with Choreo, WSO2’s AI-native Internal Developer Platform as a Service. Discover how you can streamline platform operations, empower your developers, and drive faster innovation — all while reducing complexity and cost.
Learn more: https://wso2.com/choreo/platform-engineering/
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptx
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptxMaharshi Mallela Movie recommendation system is a software application or algorithm designed to suggest movies to users based on their preferences, viewing history, or other relevant factors. The primary goal of such a system is to enhance user experience by providing personalized and relevant movie suggestions.
Best Practice for LLM Serving in the Cloud
Best Practice for LLM Serving in the CloudAlluxio, Inc. Alluxio Webinar
June 17, 2025
For more Alluxio Events: https://www.alluxio.io/events/
Speaker:
Nilesh Agarwal (Co-founder & CTO @ Inferless)
Nilesh Agarwal, co-founder & CTO at Inferless, shares insights on accelerating LLM inference in the cloud using Alluxio, tackling key bottlenecks like slow model weight loading from S3 and lengthy container startup time. Inferless uses Alluxio as a three-tier cache system that dramatically cuts model load time by 10x.
Best MLM Compensation Plans for Network Marketing Success in 2025
Best MLM Compensation Plans for Network Marketing Success in 2025LETSCMS Pvt. Ltd.
Discover the top MLM compensation plans including Unilevel, Binary, Matrix, Board, and Australian Plans. Learn how to choose the best plan for your business growth with expert insights from MLM Trees. Explore hybrid models, payout strategies, and earning potential.
Learn more: https://www.mlmtrees.com/mlm-plans/
OpenChain Webinar - AboutCode - Practical Compliance in One Stack – Licensing...
OpenChain Webinar - AboutCode - Practical Compliance in One Stack – Licensing...Shane Coughlan OpenChain Webinar - AboutCode - Practical Compliance in One Stack – Licensing, Vulnerabilities, and More
Simplify Task, Team, and Project Management with Orangescrum Work
Simplify Task, Team, and Project Management with Orangescrum WorkOrangescrum Streamline project workflows, team collaboration, and time tracking with orangescrum work, your all-in-one tool for smarter and faster project execution.
AI for PV: Development and Governance for a Regulated Industry
AI for PV: Development and Governance for a Regulated IndustryBiologit AI for pharmacovigilance: Development and Governance for a Regulated Industry.
A survey of regulatory guidance for the use of artificial intelligence in pharmacovigilance and best practices for its safe implementation with the Biologit literature platform as case study.
Test Case Design Techniques – Practical Examples & Best Practices in Software...
Test Case Design Techniques – Practical Examples & Best Practices in Software...Muhammad Fahad Bashir
Exploratory testing part 1
- 2. Inattentional Blindness Check out these videos https://www.youtube.com/watch?v=vJG698U2Mvo https://www.youtube.com/watch?v=IGQmdoK_ZfY
- 3. Inattentional Blindness We pay attention to some things and therefore we do NOT pay attention to others Even events that “should be” obvious will be missed if we are attending to other things. Computers focus only on what they are programmed to look at: They are inattentionally blind by design! Content from Cen Kaner, Exploratory Testing @ QUEST 2008
- 4. What we need … Is a constantly evolving set of tests That exercise the software in new ways (new combinations of features and data) So that we get our choice of Broader coverage of the infinite space of possibilities Adapting as we recognize new classes of possibilities And sharper focus On risks or issues that we decide are of critical interest today Content from Cen Kaner, Exploratory Testing @ QUEST 2008
- 5. Testing is like CSI MANY tools, procedures, sources of evidence. • Tools and procedures don't define an investigation or its goals. • There is too much evidence to test, tools are often expensive, so investigators must exercise judgment. • The investigator must pick what to study, and how in order to reveal how, in order to reveal the most needed information. Content from Cen Kaner, Exploratory Testing @ QUEST 2008
- 6. Imagine … Imagine crime scene investigators (real investigators of real crime scenes) following a script. How effective do you think they would be? Content from Cen Kaner, Exploratory Testing @ QUEST 2008
- 7. Context Testing is always done within a context We test in the face of harsh constraints • Complete testing is impossible • Project schedules and budget are finite Testing might be done before, during or after a release Improvement of product or process might or might not be an objective of testing We test on behalf of stakeholders • Project manager, marketing manager, programmer, competitor, attorney – Which stakeholder(s) this time? • What information are they interested in? • What risks do they want to mitigate? Content from Cen Kaner, Exploratory Testing @ QUEST 2008
- 8. Context What are examples of context that impact our testing?