Before we dive into the importance of Exploratory Testing, I would like to clear three things up.
Firstly, I align with this definition of Exploratory Testing, by Cem Kamer, it is an approach to software testing that consists of simultaneous learning, test design and test execution.
Secondly, I don’t think Exploratory Testing has to be a substitute for test cases, it can complement test cases. (It’s up to you, how or if you choose to combine both Exploratory Testing and Test cases when you test a feature)
Lastly, exploratory testing is not adhoc testing – adhoc testing is random, unstructured testing, exploratory testing forced you to think critically about the application under test. (For more about the difference go here.)
Continue reading “Bloggers Club: The Importance of Exploratory Testing”
If you haven’t already, you may one day find yourself in a project where there are no (explicit) requirements or very little requirements to go off.
Software can be created from conversations and assumptions. People may also assume that the little requirements they do write is enough to easily code against or test off, but then you later realise that the few lines that have been written actually pose more questions than provide answers.
You first time testing on a project without requirements can be a bit scary but I’m hoping this step by step guide will help you. Continue reading “Step by step guide: Testing without requirements/ little requirements”
As I am helping introduce Exploratory Testing to our current project, there is one thing I’ve had to remind myself over and over and over again.
One’s experience shapes one’s point of view.
When having a discussion, or trying to convince someone of my point of view, I try to consciously remember this.
Continue reading “Reminding myself about how one’s experience shapes one’s point of view”
Well, this is a bit of a rant – but seriously.
I don’t like people calling an activity exploratory testing when it’s actually ad hoc testing.
Get it right.
I think using the term “exploratory testing” loosely – takes away from the value that actual exploratory testing can add to a project.
Continue reading “Don’t call it exploratory testing (if it’s not exploratory testing)”
Earlier this week I was a co-presenter for a 2 day workshop on SBTM (Session Based Test Management) at Unity.
While I have a solid amount of relevant experience (speaking at conferences, organising and speaking at meet-ups, being a co-instructor for BBST Foundations course multiple times, mentoring and coaching testers in previous projects and mentoring and coaching speakers at Toastmasters), actually facilitating a 2 day workshop for over 40 attendees is another kettle of fish! All of the experience I mentioned helped me prepare for this workshop but it was almost definitely the hardest thing I’ve done in my career so far.
Continue reading “What I learned from giving my first ever workshop”