Category: exploratory testing
-
Yes you can run exploratory testing with ai
AI can run your exploratory testing, but only as well as the charter, risk appetite and heuristics you give it. Here I show how you can do this.
-
Testing Doesn’t Just Happen at the End
In this post I say that testing isn’t a phase, it’s something that happens everywhere in your delivery.
-
How to Involve Developers in Exploratory Testing
Asking developers to start exploratory testing can be hard; many testers haven’t had the opportunity to practise this type of testing, let alone developers. This article will discuss the steps and tips for getting your team (with a focus on developers) involved in exploratory testing.
-
100% Tested is not 100% Covered
The misconception that 100% test coverage ensures a fully tested system can lead to false confidence among stakeholders. Various forms of undocumented scope—explicit, implicit, and unknown—mean that thorough testing may still leave gaps. To mitigate risks, teams should educate stakeholders, transparently share testing scope, and encourage detailed documentation of requirements.
-
Testers – Don’t wait to be asked
The whole point of being a tester is the ability to not only find but share information to teams. In this post I discuss how it’s not enough to do the testing, we have to share information about it too.
-
Don’t wait to test – Go explore!
In this post I advocate for exploring the unknown rather than testing what we already know.
-
Setting your own Testing Scope to Work With Uncertainty
I describe how I work out what to test when nobody explicitly tells me.
-
Why adhoc testing is not exploratory testing
Exploration shouldn’t be just clicking about, discover how we can structure it to add more value.
-
Ask Me Anything: Exploratory Testing
I answer your questions about exploratory testing in this post!
-
Why checking an AC isn’t enough
We need to look beyond just what’s written down in order to understand quality.