Search the courses, subjects, tracks, games and features, or jump straight to a page.
Learn it your way
A short class with Sarah and her students. The other ways are under More.
Sign up free to listen. Transcripts are free to read.
Today, we are going to discuss exploratory testing. Who can tell me what they think exploratory testing is?
Isn't it when testers explore the application without following strict scripts?
Exactly, exploratory testing happens simultaneously with learning, test design, and execution. By using unscripted testing, we can uncover issues that scripted tests might miss. Can anyone think of a situation where that might be particularly important?
It could be really important in early-stage applications where things are still changing.
Great point! Exploratory testing is indeed valuable in early builds and can help identify usability issues or confusing workflows. Remember that you want to document your discoveries as you explore. Why do you think this documentation is necessary?
So we can communicate findings back to the team and make modifications if needed?
Exactly right! Documentation helps maintain a clear line of communication.
Let’s talk about the value of exploratory testing in Agile. What are some benefits of this approach?
It can uncover edge cases that normal testing might miss.
Absolutely! It helps us discover how the application behaves in scenarios that weren't considered initially. Additionally, it focuses on user experience by addressing usability issues. Can anyone provide an example of an edge case that might be discovered through exploratory testing?
When a user tries to input an invalid email during registration?
Yes, that's a perfect example! By exploring these edge cases, we ensure a smoother experience for users. Now, let's discuss how we can structure our exploratory testing sessions. Does anyone know how to start a charter-based session?
We would choose a specific feature to focus on, like 'exploring the cart checkout flow for invalid inputs.'
Correct! By focusing on specific areas, we can use our time more efficiently.
Now that we understand exploratory testing, how do you think it can integrate with automated and scripted testing?
Maybe we can use exploratory testing to find more areas that should be automated later down the line?
Exactly! Exploratory testing allows for the creativity and adaptability needed to improve our automated tests over time. It fills in gaps that scripted tests might not cover. Why is it important that exploratory testing remains flexible?
So we can adjust to changes in the application or the feedback from users?
Precisely! Agile emphasizes adaptability, and exploratory testing encapsulates that. It fosters a culture of continuous improvement. Can anyone summarize why exploratory testing is such an essential practice in Agile?
Because it allows us to catch issues early, focus on user experience and adaptively improve our testing strategies!
Excellent summary!
A method of testing that focuses on simultaneous learning, test design, and execution.
Focused exploratory sessions aimed at a specific functionality.
Scenarios often overlooked in standard testing.
Problems affecting the user-friendliness of an application.
Explore the app without a map, discover bugs in your testing lap.
Imagine a hero testing a new castle, without knowing the layout, they seek out secret doors and hidden traps, learning as they go to find the best way to navigate.
E-UUC (Explore, Uncover, Understand, Communicate): The steps involved in exploratory testing.
TEST (Test, Explore, Share, Track): A guide to the exploratory testing process.
Term
What is exploratory testing?
Click to flip
Term
What are chartered sessions?
Click to flip
Term
What is an edge case?
Click to flip
A testing approach that combines test design, execution, and learning without predefined test scripts.
Structured exploratory testing sessions that focus on specific features or workflows.
Problems that affect how user-friendly an application or feature is.
Scenarios or inputs that occur outside of normal operating parameters, which may reveal issues during testing.
Exploratory testing in Agile emphasizes simultaneous learning and testing to uncover hidden issues within a product.
This section describes exploratory testing as a valuable practice in Agile software development, highlighting its role in discovering edge cases and usability issues through unscripted exploration. It provides strategies for effective exploratory testing, integrating it into Agile processes with a focus on collaboration and continuous feedback.
Exploratory testing is defined as a simultaneous process of learning, test design, and execution. Unlike traditional testing methods bound by predefined scripts, exploratory testing encourages testers to delve into the application and discover issues organically. This approach is particularly valuable during Agile sprints, as it allows QA teams to uncover edge cases and usability concerns that scripted tests may overlook.
Overall, exploratory testing complements the Agile approach, promoting a culture of collaboration and continuous improvement among team members.