UK star ultimate testing survival
•Download as PPTX, PDF•
0 likes•409 views
This document provides tips for surviving as a tester based on stories that portray testing as easy but can turn difficult. It summarizes that: 1. Documentation is often lacking, tools are imperfect, and real-life projects introduce challenges beyond what stories suggest. 2. Risk-driven testing is recommended over artifact-driven testing to understand core functionality and risks through techniques like premortems and risk lists. 3. Using oracles like documentation, common sense, and experience can help spot problems, but oracles have more depth than commonly understood. 4. Automation should support testing by being consistent and efficient with short, deterministic scripts rather than replacing testing or focusing on end-to-end UI tests
Report
Share
Report
Share
Recommended
Assorted TDD tips
This document discusses various tips and perspectives on test-driven development (TDD). It addresses TDD as a tool that depends on context and constraints. It should be considered a skill that requires practice. TDD can serve as documentation when tests are written clearly and follow good practices like SOLID principles. The document emphasizes focusing TDD on goals and being aware that tests can increase coupling, requiring trade-offs. It recommends practicing TDD through katas to improve skills.
Worst practices in software testing by the Testing troll
The document discusses best and worst practices in software testing according to a mythical testing creature called "The Testing Troll".
Some worst practices presented include relying solely on documentation, focusing only on repetitive regression testing of old tests, viewing automation as a replacement for human testers, and strictly following best practices without consideration of context.
The best practices emphasized thinking beyond requirements and oracles, prioritizing regression tests that reveal new information, using automation as a tool to enhance testing abilities rather than replace testers, providing information about potential risks, and being aware of testing context in different situations. The conclusion is that there are no absolute best practices and testers must be skeptical professionals who consider context.
Automation vs. intelligence - "follow me if you want to live"
Have you ever heard the story that your job is automatable, that all the human testers will be replaced by machines or automated tests and you will lose your job? Or even worse, that machines and artificial intelligence will take over our craft and our life and we will be totally useless. Do you buy these? Are you afraid?
“Come with me, if you want to live” – this was the famous line that many members of the Human resistance in the Terminator franchise used, when offering their help in the war against Skynet.
So, come with me (and John Connor), and join the testing resistance to fight on the side of intellect against the evil machine army. I am willing to challenge the I part in AI on contest by focusing on few key topics:
Can we translate testing into machine language? Polymorphic and mimeomorphic actions – what are these?
Do we really know what are the benefits of human testing? What are human testers irreplaceable for?
Do we really have empirical evidence that computers are capable of doing professional testing? Do we have evidence of “intelligence” at all?
Last year at RTC ‘17 I was asked – “Is AI the answer to all test automation problems?”. My answer is “No, it’s not!”. And this talk is my explanation why.
Test automation – the bitter truth
Test automation has some bitter truths that are often overlooked. While automation can help with confirmation testing of deterministic scenarios, many critical testing tasks like exploration and qualitative evaluation are not easily automated. Automation also does not necessarily decrease the costs of testing when development, maintenance, and debugging of automation code is considered. It is more accurate to consider test automation as programmatic testing rather than assuming full automation is possible. Both automated and manual testing are misleading terms, and the focus should be on using tools like automation to extend testing rather than replace human testing.
"Worst" practices of software testing
The document discusses "worst practices" of software testing according to The Testing Troll. It provides 5 "worst practices" and alternatives suggested by The Testing Troll. The first is to learn about real testing oracles rather than relying only on requirements. The second is to focus regression testing on tests that reveal new information rather than repetitive testing. The third is to use automation as a tool to extend abilities rather than replace manual testing. The fourth is to provide information about risks through risk-based testing rather than just assuring quality. And the fifth is to be always alert to your context rather than following best practices blindly. The Testing Troll advocates thinking critically and focusing on exploration and human aspects of testing over fixed processes.
Hindsight lessons about API testing
This document provides lessons learned about automating API testing. It discusses what an API is and reasons for automating API tests, including getting clear responses close to the client experience. The document outlines different types of tests to automate, including status code checks, structure checks, and scenario checks. It also discusses cognitive barriers to testing, test setup and environment, using an automation framework, and splitting test logic from application logic. The goal is not to provide a how-to guide but rather discuss lessons learned about effective API testing.
Asking Questions and Writing Effectively
This presentation is all about how asking questions drives an investigation and how to use the answers obtained to create an effective writeup.
Concurrency Errors in Java
This document discusses concurrency errors in Java and how to avoid them. It begins by defining a concurrency error as the result of incorrect synchronization that can cause issues like race conditions and starvation. It notes that concurrency errors can lead to data corruption, security vulnerabilities, and incorrect behavior. While Java includes synchronization primitives, concurrency is still tricky and errors can occur if the primitives are used incorrectly or without properly designing the concurrency model. The document provides examples of potential concurrency errors and ways to avoid them, such as locking on an appropriate shared object to ensure atomic read/write operations. In the end, it emphasizes the importance of remaining vigilant about concurrency through tools, analysis, and careful design.
Recommended
Assorted TDD tips
This document discusses various tips and perspectives on test-driven development (TDD). It addresses TDD as a tool that depends on context and constraints. It should be considered a skill that requires practice. TDD can serve as documentation when tests are written clearly and follow good practices like SOLID principles. The document emphasizes focusing TDD on goals and being aware that tests can increase coupling, requiring trade-offs. It recommends practicing TDD through katas to improve skills.
Worst practices in software testing by the Testing troll
The document discusses best and worst practices in software testing according to a mythical testing creature called "The Testing Troll".
Some worst practices presented include relying solely on documentation, focusing only on repetitive regression testing of old tests, viewing automation as a replacement for human testers, and strictly following best practices without consideration of context.
The best practices emphasized thinking beyond requirements and oracles, prioritizing regression tests that reveal new information, using automation as a tool to enhance testing abilities rather than replace testers, providing information about potential risks, and being aware of testing context in different situations. The conclusion is that there are no absolute best practices and testers must be skeptical professionals who consider context.
Automation vs. intelligence - "follow me if you want to live"
Have you ever heard the story that your job is automatable, that all the human testers will be replaced by machines or automated tests and you will lose your job? Or even worse, that machines and artificial intelligence will take over our craft and our life and we will be totally useless. Do you buy these? Are you afraid?
“Come with me, if you want to live” – this was the famous line that many members of the Human resistance in the Terminator franchise used, when offering their help in the war against Skynet.
So, come with me (and John Connor), and join the testing resistance to fight on the side of intellect against the evil machine army. I am willing to challenge the I part in AI on contest by focusing on few key topics:
Can we translate testing into machine language? Polymorphic and mimeomorphic actions – what are these?
Do we really know what are the benefits of human testing? What are human testers irreplaceable for?
Do we really have empirical evidence that computers are capable of doing professional testing? Do we have evidence of “intelligence” at all?
Last year at RTC ‘17 I was asked – “Is AI the answer to all test automation problems?”. My answer is “No, it’s not!”. And this talk is my explanation why.
Test automation – the bitter truth
Test automation has some bitter truths that are often overlooked. While automation can help with confirmation testing of deterministic scenarios, many critical testing tasks like exploration and qualitative evaluation are not easily automated. Automation also does not necessarily decrease the costs of testing when development, maintenance, and debugging of automation code is considered. It is more accurate to consider test automation as programmatic testing rather than assuming full automation is possible. Both automated and manual testing are misleading terms, and the focus should be on using tools like automation to extend testing rather than replace human testing.
"Worst" practices of software testing
The document discusses "worst practices" of software testing according to The Testing Troll. It provides 5 "worst practices" and alternatives suggested by The Testing Troll. The first is to learn about real testing oracles rather than relying only on requirements. The second is to focus regression testing on tests that reveal new information rather than repetitive testing. The third is to use automation as a tool to extend abilities rather than replace manual testing. The fourth is to provide information about risks through risk-based testing rather than just assuring quality. And the fifth is to be always alert to your context rather than following best practices blindly. The Testing Troll advocates thinking critically and focusing on exploration and human aspects of testing over fixed processes.
Hindsight lessons about API testing
This document provides lessons learned about automating API testing. It discusses what an API is and reasons for automating API tests, including getting clear responses close to the client experience. The document outlines different types of tests to automate, including status code checks, structure checks, and scenario checks. It also discusses cognitive barriers to testing, test setup and environment, using an automation framework, and splitting test logic from application logic. The goal is not to provide a how-to guide but rather discuss lessons learned about effective API testing.
Asking Questions and Writing Effectively
This presentation is all about how asking questions drives an investigation and how to use the answers obtained to create an effective writeup.
Concurrency Errors in Java
This document discusses concurrency errors in Java and how to avoid them. It begins by defining a concurrency error as the result of incorrect synchronization that can cause issues like race conditions and starvation. It notes that concurrency errors can lead to data corruption, security vulnerabilities, and incorrect behavior. While Java includes synchronization primitives, concurrency is still tricky and errors can occur if the primitives are used incorrectly or without properly designing the concurrency model. The document provides examples of potential concurrency errors and ways to avoid them, such as locking on an appropriate shared object to ensure atomic read/write operations. In the end, it emphasizes the importance of remaining vigilant about concurrency through tools, analysis, and careful design.
Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses DateTime.Now? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests?
This presentation is about clearing away automated testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
Break to build - the mindset of the modern day tester
I spent last couple of years performing, talking, writing and listening about software testing.
But what is software testing? I am told my job is to “break software”. But why break it, it looks good?! I like the programmers, they are my friends. And, as Michael Bolton says, “We don’t break software, it was already broken when we got it”.
I sure don’t break software for living, but I do something way better and much more satisfying - I break clichés about software testing.
So, my job as your guide in your journey in testing will be to break some clichés from the past in order to build the mindset of the modern tester.
DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers
This document summarizes a presentation on overcoming obstacles, pitfalls, and dangers of automated testing. The presentation covers four main obstacles: 1) over-specifying tests with too many assertions, 2) tests becoming coupled to the system clock, 3) database issues causing integration test failures, and 4) test code becoming too repetitive without proper reuse. Examples are provided for each obstacle along with approaches for addressing them like using fewer assertions per test, faking the system time, managing test database state, and implementing better code reuse in test files.
The Art of Questioning to improve Software Testing, Agile and Automating
The presentation was delivered at the National Software Testing Conference on 17th May. It draws on lessons learned from various forms of fast, brief and systemic psychotherapy. With a few simple points:
* Why? is a question that targets beliefs
* How, What, Where, When, Who - all target structure and process
* We all have models of the world and our questions reflect that model
* Answers we give, reflect our model
* Responses to answers give information on how well the models of the question asker, and answering person, match up
* Testing can be modeled as a questioning process
* Improving our ability to ask questions improves our ability to test, manage, and change behaviour.
Resource Leaks in Java
Resource leaks occur when a program fails to release resources it has acquired, like memory or file handles. While Java's garbage collector handles memory leaks, it cannot guarantee sufficient resources or clean up non-heap resources like database connections. A code example shows how failing to close a database connection statement can lead to a resource leak over time as the application continues to work with the database. Developers must explicitly close resources to avoid leaks and ensure resources are freed for future use.
OSS Java Analysis - What You Might Be Missing
We think FindBugs is a great tool for finding coding style and best practice types of issues, so we conducted a little experiment a few months ago. We analyzed Jenkins core code with both FindBugs and Coverity. These slides provide a high-level summary of our results.
Digital badges - NERCOMP Gameful Learning Presentation
Presentation given at NERCOMP Gameful Learning Professional Development workshop, September 2014. This presentation explored some aspects of applying a gamification framework toa Graduate Instructional Design course, and the initial application of digital badges to this course.
Strategies and Tools for Assessing ELs
My books- Hacking Digital Learning Strategies http://hackingdls.com & Learning to Go https://gum.co/learn2go
Resources http://shellyterrell.com/assessment
Confessions of an Accidental Security Tester
The slides for the Oredev 2014 talk "confessions of an accidental Security Tester" - describing the various approaches and bad habits that I use, which allow me to stumble on to security problems.
5-Why Training
The document discusses the 5 Why's technique for root cause analysis. It can be used for troubleshooting, quality improvement, and problem solving. The process involves repeatedly asking "Why?" five times to determine the root cause of a problem by drilling down through its symptoms. Tools like Ishikawa charts, design of experiments, and statistical analysis can also aid in root cause analysis.
James thomas
Elisabeth Hendrickson’s book, Explore It!, contains this definition: “Tested = Checked + Explored”. When I read it, I was fascinated. “What does that mean?”, I asked myself, “what does it /really/ mean?”
This talk described the journey I undertook to understand it, and other definitions of testing that I found along the way, and then to come up with a new definition that filled the gaps I saw in the others, without losing the aspects of them that I felt were valid and useful.
Essentially, I formalised what testing is for me. And, now that I have my definition, I can ask myself in any given situation whether my actions are consistent with the way I believe I want to behave.
Improving Your Debugging Skills In WordPress
In a world increasingly run by software, failures can be caused by bugs.
Failure to find and fix bugs quickly has a financial, personal and reputational cost to an organisation. It can impact on product delivery time as well.
A large portion of developer’s time is spent in debugging.
However, when was the last time we worked on improving our debugging skills?
This is one of the rarely discussed topics.
So let’s spend some time in improving our debugging skills, that can help us make it simpler to quickly find and fix critical bugs, so that we can deliver to ever-shortening deadlines and boosts overall productivity.
Functional test best practice
This document discusses best practices for functional test automation. It begins by describing common failure patterns seen in test results, such as single tests failing across browsers or browsers failing all tests. Problems like fragile selectors that don't work across browsers, timing issues, non-deterministic tests, and test dependencies are explained. Best practices to address these problems include using stable selectors, avoiding sleeps/waits and making tests self-contained. The document also introduces Test Armada as a solution for running tests across platforms and browsers, and collecting results and insights. It concludes with contact information for further questions.
Design Patterns
A presentation about Design Patterns. Here are mentioned all 23 design patterns from GoF. Also mentioned about some most common antipatterns
How did i miss that bug rtc
The document discusses how cognitive biases can cause testers to miss bugs. It explains that people have two types of thinking: System 1 thinking is fast, intuitive, and prone to biases, while System 2 thinking is slower, more deliberate, and logical. Common biases that can affect testers include the representative bias, the curse of knowledge, the congruence bias, and the confirmation bias. The document recommends that testers employ more System 1 thinking through techniques like exploratory testing to leverage their intuition to find bugs. It also suggests test managers create an environment where testers feel comfortable using more System 1 thinking approaches.
Agile2015: Explore with Intent - Self-Management
This document discusses exploratory testing and self-management techniques for exploratory testing. It covers:
1. Exploratory testing focuses on learning through exploration rather than creating testing artifacts. Notes and bug reports support the tester's memory rather than being the primary goal.
2. Testers can use various note-taking tools like physical notebooks, mind maps, or rapid reporting tools. The tool that works best for individual testers can vary.
3. When learning about a new feature, testers may choose different starting points like reading specifications first versus experiencing the feature first. This process uncovers bugs and questions that create more work.
4. Exploratory testing is an approach not a technique, aimed at
Santa Barbara Agile: Exploratory Testing Explained and Experienced
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.
SAM
The document discusses challenges with testing software without requirements documentation and provides some strategies to help with testing in such situations. It notes that QA teams may have to test without knowing what the application is supposed to do. It then suggests several paths that testing teams can take when faced with limited or missing documentation, such as UI teams creating screenshots and development teams creating technical design documents. The document also advocates for daily standup meetings between teams to help coordinate testing efforts in lieu of documentation.
Bug-Free Software? Go For It!
I consider whether we as testers can be too closed-minded in our attitudes, whether there are schools of thought or approaches that, even if we care deeply about context, we are very unlikely even to consider and perhaps that we sometimes favour our reputation over giving ourselves the chance to do the best job that we can.
From CEWT#2, http://cewtblog.blogspot.co.uk/2016/02/cewt-2-abstracts.html
Exploring with Automation
When considering how automation can be useful in testing, many people think only about identifying difference from some expected behaviour, for example with unit tests.
Much of my testing is about exploration, about learning, about finding things that might matter that we haven't already thought about. In this talk, I'll discuss how I use automation to help me to do that. In particular I'll demo some ways in which I ask questions of the product and use automation to find expedient ways to get answers.
A Rapid Introduction to Rapid Software Testing
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Paul Holland introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Paul to learn how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
A Rapid Introduction to Rapid Software Testing
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.
More Related Content
What's hot
Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses DateTime.Now? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests?
This presentation is about clearing away automated testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
Break to build - the mindset of the modern day tester
I spent last couple of years performing, talking, writing and listening about software testing.
But what is software testing? I am told my job is to “break software”. But why break it, it looks good?! I like the programmers, they are my friends. And, as Michael Bolton says, “We don’t break software, it was already broken when we got it”.
I sure don’t break software for living, but I do something way better and much more satisfying - I break clichés about software testing.
So, my job as your guide in your journey in testing will be to break some clichés from the past in order to build the mindset of the modern tester.
DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers
This document summarizes a presentation on overcoming obstacles, pitfalls, and dangers of automated testing. The presentation covers four main obstacles: 1) over-specifying tests with too many assertions, 2) tests becoming coupled to the system clock, 3) database issues causing integration test failures, and 4) test code becoming too repetitive without proper reuse. Examples are provided for each obstacle along with approaches for addressing them like using fewer assertions per test, faking the system time, managing test database state, and implementing better code reuse in test files.
The Art of Questioning to improve Software Testing, Agile and Automating
The presentation was delivered at the National Software Testing Conference on 17th May. It draws on lessons learned from various forms of fast, brief and systemic psychotherapy. With a few simple points:
* Why? is a question that targets beliefs
* How, What, Where, When, Who - all target structure and process
* We all have models of the world and our questions reflect that model
* Answers we give, reflect our model
* Responses to answers give information on how well the models of the question asker, and answering person, match up
* Testing can be modeled as a questioning process
* Improving our ability to ask questions improves our ability to test, manage, and change behaviour.
Resource Leaks in Java
Resource leaks occur when a program fails to release resources it has acquired, like memory or file handles. While Java's garbage collector handles memory leaks, it cannot guarantee sufficient resources or clean up non-heap resources like database connections. A code example shows how failing to close a database connection statement can lead to a resource leak over time as the application continues to work with the database. Developers must explicitly close resources to avoid leaks and ensure resources are freed for future use.
OSS Java Analysis - What You Might Be Missing
We think FindBugs is a great tool for finding coding style and best practice types of issues, so we conducted a little experiment a few months ago. We analyzed Jenkins core code with both FindBugs and Coverity. These slides provide a high-level summary of our results.
Digital badges - NERCOMP Gameful Learning Presentation
Presentation given at NERCOMP Gameful Learning Professional Development workshop, September 2014. This presentation explored some aspects of applying a gamification framework toa Graduate Instructional Design course, and the initial application of digital badges to this course.
Strategies and Tools for Assessing ELs
My books- Hacking Digital Learning Strategies http://hackingdls.com & Learning to Go https://gum.co/learn2go
Resources http://shellyterrell.com/assessment
Confessions of an Accidental Security Tester
The slides for the Oredev 2014 talk "confessions of an accidental Security Tester" - describing the various approaches and bad habits that I use, which allow me to stumble on to security problems.
5-Why Training
The document discusses the 5 Why's technique for root cause analysis. It can be used for troubleshooting, quality improvement, and problem solving. The process involves repeatedly asking "Why?" five times to determine the root cause of a problem by drilling down through its symptoms. Tools like Ishikawa charts, design of experiments, and statistical analysis can also aid in root cause analysis.
James thomas
Elisabeth Hendrickson’s book, Explore It!, contains this definition: “Tested = Checked + Explored”. When I read it, I was fascinated. “What does that mean?”, I asked myself, “what does it /really/ mean?”
This talk described the journey I undertook to understand it, and other definitions of testing that I found along the way, and then to come up with a new definition that filled the gaps I saw in the others, without losing the aspects of them that I felt were valid and useful.
Essentially, I formalised what testing is for me. And, now that I have my definition, I can ask myself in any given situation whether my actions are consistent with the way I believe I want to behave.
Improving Your Debugging Skills In WordPress
In a world increasingly run by software, failures can be caused by bugs.
Failure to find and fix bugs quickly has a financial, personal and reputational cost to an organisation. It can impact on product delivery time as well.
A large portion of developer’s time is spent in debugging.
However, when was the last time we worked on improving our debugging skills?
This is one of the rarely discussed topics.
So let’s spend some time in improving our debugging skills, that can help us make it simpler to quickly find and fix critical bugs, so that we can deliver to ever-shortening deadlines and boosts overall productivity.
Functional test best practice
This document discusses best practices for functional test automation. It begins by describing common failure patterns seen in test results, such as single tests failing across browsers or browsers failing all tests. Problems like fragile selectors that don't work across browsers, timing issues, non-deterministic tests, and test dependencies are explained. Best practices to address these problems include using stable selectors, avoiding sleeps/waits and making tests self-contained. The document also introduces Test Armada as a solution for running tests across platforms and browsers, and collecting results and insights. It concludes with contact information for further questions.
Design Patterns
A presentation about Design Patterns. Here are mentioned all 23 design patterns from GoF. Also mentioned about some most common antipatterns
How did i miss that bug rtc
The document discusses how cognitive biases can cause testers to miss bugs. It explains that people have two types of thinking: System 1 thinking is fast, intuitive, and prone to biases, while System 2 thinking is slower, more deliberate, and logical. Common biases that can affect testers include the representative bias, the curse of knowledge, the congruence bias, and the confirmation bias. The document recommends that testers employ more System 1 thinking through techniques like exploratory testing to leverage their intuition to find bugs. It also suggests test managers create an environment where testers feel comfortable using more System 1 thinking approaches.
Agile2015: Explore with Intent - Self-Management
This document discusses exploratory testing and self-management techniques for exploratory testing. It covers:
1. Exploratory testing focuses on learning through exploration rather than creating testing artifacts. Notes and bug reports support the tester's memory rather than being the primary goal.
2. Testers can use various note-taking tools like physical notebooks, mind maps, or rapid reporting tools. The tool that works best for individual testers can vary.
3. When learning about a new feature, testers may choose different starting points like reading specifications first versus experiencing the feature first. This process uncovers bugs and questions that create more work.
4. Exploratory testing is an approach not a technique, aimed at
Santa Barbara Agile: Exploratory Testing Explained and Experienced
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.
SAM
The document discusses challenges with testing software without requirements documentation and provides some strategies to help with testing in such situations. It notes that QA teams may have to test without knowing what the application is supposed to do. It then suggests several paths that testing teams can take when faced with limited or missing documentation, such as UI teams creating screenshots and development teams creating technical design documents. The document also advocates for daily standup meetings between teams to help coordinate testing efforts in lieu of documentation.
Bug-Free Software? Go For It!
I consider whether we as testers can be too closed-minded in our attitudes, whether there are schools of thought or approaches that, even if we care deeply about context, we are very unlikely even to consider and perhaps that we sometimes favour our reputation over giving ourselves the chance to do the best job that we can.
From CEWT#2, http://cewtblog.blogspot.co.uk/2016/02/cewt-2-abstracts.html
Exploring with Automation
When considering how automation can be useful in testing, many people think only about identifying difference from some expected behaviour, for example with unit tests.
Much of my testing is about exploration, about learning, about finding things that might matter that we haven't already thought about. In this talk, I'll discuss how I use automation to help me to do that. In particular I'll demo some ways in which I ask questions of the product and use automation to find expedient ways to get answers.
What's hot (20)
Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing
Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing
Break to build - the mindset of the modern day tester
Break to build - the mindset of the modern day tester
DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers
DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers
The Art of Questioning to improve Software Testing, Agile and Automating
The Art of Questioning to improve Software Testing, Agile and Automating
Digital badges - NERCOMP Gameful Learning Presentation
Digital badges - NERCOMP Gameful Learning Presentation
Santa Barbara Agile: Exploratory Testing Explained and Experienced
Santa Barbara Agile: Exploratory Testing Explained and Experienced
Similar to UK star ultimate testing survival
A Rapid Introduction to Rapid Software Testing
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Paul Holland introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Paul to learn how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
A Rapid Introduction to Rapid Software Testing
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.
A Rapid Introduction to Rapid Software Testing
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to learn how Rapid Testing focuses on both the mind set and skill set of the individual tester, using tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
Learn Learning + Prototype Testing
Slides from a 5/10/2017 talk at the Nasdaq Entrepreneurial Center (@theCenter) about a lean research mindset, the mechanics of learning from users, and the structure of a research prototype test session.
Things Could Get Worse: Ideas About Regression Testing
Michael Bolton, DevelopSense
Tester, consultant, and trainer Michael Bolton is the coauthor (with James Bach) of Rapid Software Testing, a course that presents a methodology and mindset for testing software expertly in uncertain conditions and under extreme time pressure. Michael is a leader in the context-driven software testing movement with twenty years of experience testing, developing, managing, and writing about software. Currently, he leads DevelopSense, a Toronto-based consultancy.
Michael Bolton - Heuristics: Solving Problems Rapidly
EuroSTAR Software Testing Conference 2008 presentation on Heuristics: Solving Problems Rapidly by Michael Bolton. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
AATC2016: Exploratory testing an API
My slides from my Agile Alliance Technical Conference 2016 -session. Includes a slide of the mindmap created with the mob in the session.
Influx/Days 2017 San Francisco | Baron Schwartz
WHAT GOOD IS ANOMALY DETECTION?
Static thresholds on metrics have been falling out of fashion for a while, and for good reason. Modern tooling lets you analyze and monitor a lot more data points than you used to be able to, resulting in lots more noise. The hope is that anomaly detection answers some of this, by replacing static thresholds (anomalies) with dynamic ones. But it doesn’t work as well as most people think it will. In this talk I’ll explain how anomaly detection works, so you can understand why it isn’t a good general-purpose solution, and which specific cases it’s good at.
Don’t Let Missed Bugs Cause Mayhem in your Organization!
This document discusses how cognitive biases can cause testers to miss bugs and provides strategies to overcome these biases. It explains that testers make judgments using both fast, intuitive System 1 thinking and slower, deliberate System 2 thinking. Common cognitive biases like representative bias, confirmation bias, and inattentional blindness are described as well as how they can influence testing. The document recommends techniques like exploratory testing to leverage more intuitive System 1 thinking and find bugs. It suggests test managers foster an environment where testers are comfortable using more subjective thinking and the QA profession shifts focus from requirements coverage to risk-based exploratory testing.
L15. Machine Learning - Black Art
Valencian Summer School 2015
Day 2
Lecture 15
Machine Learning - Black Art
Charles Parker (Alston Trading)
https://bigml.com/events/valencian-summer-school-in-machine-learning-2015
Presentation phinney abrf 2019
Not the best presentation, mostly a stream a consciousness about analyzing samples in a Core facility, although I do list some of my favorite methods. So maybe it will be useful to some? I repacakged this into a better talk (see my Genomeweb 2019 talk on SlideShare)
Automated Testing: Obstacles, Pitfalls, and Dangers
The document discusses the motivation, principles, and obstacles of automated testing. It motivates automated testing by noting how it provides visibility into problems, detects issues early, and acts as an advance warning system. The principles discussed are having tests that are zero configuration, fast, provide clear results, and are easy to maintain. Obstacles covered include tests becoming too specific over time, reliance on system time/date, dependency on databases changing test data, and tests becoming too coupled through overuse of reuse. Examples are provided to illustrate the points.
Software Security Initiative Capabilities: Where Do I Begin?
Where to begin your software security initiative including defect discovery, secure SDLC, vendor management and more.
Making disaster routine
This document discusses how organizations can prepare for disasters by making failures routine through practices like chaos engineering and active monitoring. It recommends:
1) Practicing failure scenarios as a team to improve disaster response procedures and checklists.
2) Introducing variables like server crashes and network issues in production environments using chaos engineering to test resiliency.
3) Monitoring application health over time to detect performance trends that could indicate future issues.
4) Treating failures as routine events by having established procedures and checklists to minimize panic and focus response efforts.
Making testability our mission
This is a call to action. On our cross functional teams and during our devops transformations we talk about how testing is for the whole team. Quality is everyone's responsibility. How much are we really doing to make this happen? Often we are working on systems that are hard to test for many reasons, but if we simply do more testing, write more automation we are neglecting what should be our main mission, advocating for increasing levels of testability, to truly get everyone involved in testing. We all have stories about how something is difficult to test, often never being tested or certainly left with the tester to figure it out. It doesn't have to be this way.
During my talk, I want to introduce a set of principles for testability engineering. A new way to approach our work as testers. These principles will tackle how we make our systems more observable, controllable, how we share knowledge across teams and improve the testability of our dependencies. I believe it is time to create a new focus on testability, as it affects everything we do, what our teams do and beyond into how value is delivered for customers.
I want you to take away from the talk:
* Why a focus on testability can multiply your effectiveness as a tester
* What the principles of testability engineering are and how to advocate for them
* How you can make iterative changes to what you do in order to embrace testability
New technology and complexity is rendering many software development techniques and paradigms obsolete at an increasing rate. We already exist in a space where an infinite number of tests of an array of different types can be performed. A new mission is needed, one that leverages the varied talents of all kinds of testers and culminates in a new focus on the exponential benefits that testability brings.
Refactoring Test Collaboration
Presented at Agile Testing Days US 2018
https://agiletestingdays.us/session/refactoring-test-collaboration/
Collective ownership for testing starts with understanding testing. Rework your team dynamics to evolve past duplication and improve performance through whole team testing. Take home practical patterns for improving your team's collaboration on testing. Because teams who own testing have more confidence in the customer value of their results.
As the Pragmatic Programmers say, "refactoring is an activity that needs to be undertaken slowly, deliberately, and carefully," so how do we begin? In this session, we will experience the complex interactions of an agile team focused on demonstrating customer value by answering a series a questions:
Where do testers get their ideas?
How are you planning to accomplish this proposed testing, tester?
Why not automate all the things?
Who is going to do this manual testing and how does it work?
How do we know whether we're testing the right things?
Build your own list of TODOs from these various practical collaboration approaches and begin deduping your team's testing for a better first day back at the office.
Waves keynote2c
David Topps gave a presentation at the WAVES Symposium in June 2016. He discussed scenario-based learning and how it can be used for more than just medical education. He also talked about measuring learning through activity metrics collected from various sources, and using cognitive computing to analyze large amounts of data from online programs. The presentation covered a wide range of topics in a non-linear way and emphasized learning from mistakes with safe environments and feedback.
How to Prepare for and Survive a Technical Interview
This document provides advice on how to prepare for and survive a technical interview. It begins with an introduction of the author and their relevant experience. It then discusses that interviewers have no real idea what they are doing and the goals are to see if candidates can demonstrate their claimed skills and experience, maintain composure, and be likable.
The document provides tips such as doing research on the company and interviewers, preparing for different types of technical challenges by practicing explanations and showing work, focusing on being interesting rather than just providing right answers, and preparing responses to common technical and non-technical questions. It emphasizes practicing answers out loud and prioritizing based on the job requirements and one's own strengths.
Advancing Testing Using Axioms
- The document discusses a new paradigm for testing called "Exploring v Testing" which focuses on exploration of knowledge sources to build test models that inform testing rather than traditional logistics-focused testing.
- It outlines three patterns of software development (structured, agile, continuous) but argues this is too simplistic and there are many approaches. A new model of testing is needed that is free from concerns about logistics.
- All testing is exploratory - testers explore knowledge sources to build test models that judge if models are adequate and inform testing. This changes what skills testers need and blurs the lines between testers and developers.
Taming Text
Presentation from March 18th, 2013 Triangle Java User Group on Taming Text. Presentation covers search, question answering, clustering, classification, named entity recognition, etc. See http://www.manning.com/ingersoll for more.
Similar to UK star ultimate testing survival (20)
Things Could Get Worse: Ideas About Regression Testing
Things Could Get Worse: Ideas About Regression Testing
Michael Bolton - Heuristics: Solving Problems Rapidly
Michael Bolton - Heuristics: Solving Problems Rapidly
Don’t Let Missed Bugs Cause Mayhem in your Organization!
Don’t Let Missed Bugs Cause Mayhem in your Organization!
Automated Testing: Obstacles, Pitfalls, and Dangers
Automated Testing: Obstacles, Pitfalls, and Dangers
Software Security Initiative Capabilities: Where Do I Begin?
Software Security Initiative Capabilities: Where Do I Begin?
How to Prepare for and Survive a Technical Interview
How to Prepare for and Survive a Technical Interview
Recently uploaded
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Recently uploaded (20)
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
UK star ultimate testing survival
- 1. Senior QA – Siteground - Bulgaria Viktor Slavchev Ultimate testing survival @thetestingtroll https://mrslavchev
- 2. 2 Once upon a time in testing …
- 3. 3 Stories people say about testing • We are told testing is easy • Everyone can test, with good guide • Just follow the docs, everything is there • You have the power to hold the release • If a task is complex, just automate it • In fact, automate everything • Everyone knows what they are doing • Especially managers
- 4. 4 Pretty much like a walk In the park
- 5. 5 This is where the story gets scary… We join a real life project and we ask for documentation Normally, the answer is:
- 6. 6 Oh, the automation Seems it’s not so clever, as well…
- 7. 7 And when you ask for guidance
- 8. 8 Seem like your walk in the park turns into • Survival in a hostile environment and limited resources • We lack knowledge • Tools are imperfect • Documentation is missing or confusing • We can only trust our skills, our tools and our ability to adapt
- 9. 9 Plus… It’s full of terrible, dreadful, scary bugs, like this one
- 10. How to survive in testing? Few tips to beat the odds
- 11. #1 Risk driven, rather then artifact driven Get to know the risks of your business
- 12. 12 Risk based testing Benefits • Get to know the core functionalities • Holistic understanding • Easier prioritization Techniques: • Premortem – “The nightmare newspaper headings game” • Postmortem – analyzing failure to learn • Risk lists – working backwards to turns risks into tests
- 13. #2 Introducing oracles Learn to spot problems
- 14. 14 What is an oracle? Definition: A concept by which we determine incorrect or incoherent behavior Commonly used oracles: Documentation, Common sense, previous experience But there’s much more to this… Consistency heuristic oracle (FEW HICCUPS), Regression oracle, constraints oracle, business logic oracle, model oracle, etc.
- 15. #3 Coded testing over test automation
- 16. 16 What is the purpose of automation? • To be consistent and efficient • To find problems • To support testing, not to replace it Techniques: • Pick what to automate, carefully • Short, deterministic test scripts • No E2E UI tests!
- 17. 17 #4 Exploration over scripting
- 18. 18 Artifact driven vs. performance driven testing Problems with test cases: • Early formalization, when not needed • Documenting over testing • Slow, time consuming Approaches to improve exploration: • Session based testing, mob testing, modeling, notes taking, framing
- 19. Q & A panel Slavchev and Person