Let's go back to the basics of what testing is supposed to be doing.
"Oh, how convenient, a machine can now do testing for me, let me send my brain cells on a well-earned holiday".
If that is you, please, don't be like that. As a tester, your brain is your most important asset, so it pains me to see that so many people in the testing community seem eager to offload important cognitive testing tasks to a machine that doesn't care, feel, or can take responsibility.
Using LLM's without question or care is highly irresponsible. This is ironic for us testers because we are supposed to be the critical realists in any project. We should aim to find problems, not blindly let a machine do...whatever.
As an antidote, let's go back to the basics of what testing is supposed to be doing. Let me show you how and why you can use the Context-Driven Testing approach in your work. Using your brain isn't optional for this, it's the basis for everything.
I'll keep repeating this: testing is a cognitive profession, and tools play a smaller role in doing it well than you think.
Topics that we'll cover:
- what sets Context-Driven Testing apart from agile testing
- how are we telling a compelling story about the testing we do
- how do you create a test strategy and why should you
- how does a context-driven tester handle test automation and other test tooling that's focused on automation.
Context-Driven Testing in 2026: It matters more than ever.