#ExploratoryTesting

Maaret Pyhäjärvimaaretp@mas.to
2025-04-15

On my way to speak at #HelPy meetup on exploratory unit testing. There is a theme to stuff I talk about now and it seems to be that the bar for ‘testing’ can be too low. I know weird things of things I’ve tested. Too many don’t know even the basics. Learning is at the heart of #ExploratoryTesting.
speakerdeck.com/maaretp/explor

imbus Canada Corporationimbus_CA
2025-03-04

ISO 29119 calls testing a testing approach in which tests are designed and executed dynamically, based on knowledge, exploration of the test object, and the results of previous tests.

An overview of the main elements of -based and their context can be found in the attached graphic.

Learn more: zurl.co/u7Ror

Maaret Pyhäjärvimaaretp@mas.to
2025-02-24

Going back to a mandate levels model I used in building up teams with two different mandate levels at previous place of work.

#ExploratoryTesting has always been an idea about increasing agency in testing by keeping things together that should stay together (design - execution), and #ContemporaryExploratoryTesting was adding automation and deciding.

A lot of our salary models are based on ideas of having beginners in low mandate roles.

Lisi Hockelisihocke
2024-11-20

Udita Sharma's and my workshop "Collect your explorer badge" is done! 🎉 It was a blast, seems participants had a great time as well generating new test ideas to explore and inspiring each other 😁

agiletestingdays.com/2024/sess

Lisi Hockelisihocke
2024-11-20

Udita Sharma's and my workshop "Collect your explorer badge" is done! 🎉 It was a blast, seems participants had a great time as well generating new test ideas to explore and inspiring each other 😁

agiletestingdays.com/2024/sess

Maaret Pyhäjärvimaaretp@mas.to
2024-08-11

Today I wonder if it is really that essential to say #ExploratoryTesting is manual testing because people need a way of allowing people who don't program to be a part of this thing we do in software development. Someone is really insisting that my way of wrapping programmatic tests as a possible output is so wrong.

Maaret Pyhäjärvimaaretp@mas.to
2024-08-10

#ExploratoryTesting is 40 years old this year. #Selenium is 20 years old. Round years for two of my favorite things.

Sergio Freiredarktelecom@c.im
2024-08-05

I've written a small article focused on data and #ExploratoryTesting. We can use data as a driver for brainstorming new test ideas and expanding existing ones. It's more than just doing data-driven testing to run the same tests against different data/conditions. Check it out and feel free to add your own perspectives on how you use data to somehow guide your #testing :)

hubs.li/Q02HZQTY0

#softwaretesting #QA #quality

Maaret Pyhäjärvimaaretp@mas.to
2024-08-02

[Blog] Gilded Rose for Exploratory Testing
visible-quality.blogspot.com/2

Since I documented how I facilitate Gilded Rose as an #ExploratoryTesting exercises, many months have passed. Teaching is not my primary focus but sharing is a byproduct of figuring out the next things I have on the agenda. No better way to reflect than writing. Well, experiential learning watching others is even better, and that is what I wrote about. :)

Maaret Pyhäjärvimaaretp@mas.to
2024-05-31

For purposes of #ExploratoryTesting, I have been discussing the idea that the software you are testing is your external imagination. I am now watching people (including myself) using LLMs as external imagination, and realizing that the successful pairing of me with the application is the same kind that is needed for doing much of anything beyond fun. But fun and funny are important for external imagination. I love being better than the average model.

Maaret Pyhäjärvimaaretp@mas.to
2024-05-28

I watched @ez test on video and narrate for a full length talk, and I recommend that.
vimeopro.com/newcrafts/newcraf

My highlights:
- Definition of #ExploratoryTesting: testing, thinking what and why it matters while doing it
- Reference to microheuristics, decision rules for the moment and shoutout to @alex_schl
- #curious as polite way saying you have degrees of disagreement on how great things are

Thanks for recording #NewCrafts, many talks worth watching there.

Maaret Pyhäjärvimaaretp@mas.to
2024-04-10

Things people do for fun: #ExploratoryTesting of
git blame -C -C -C

The first C detecting lines moved or copied in same commit.
The second C the commit that created that file
The third C any commit at all.

Not the most intuitive UX but super fun for exploratory testing.

Maaret Pyhäjärvimaaretp@mas.to
2024-01-24

#ExploratoryTesting was coined by Cem Kaner in 1988. Well, that is the earliest publication you can find of it, and the storyline says he was using the word earlier to describe the style of skilled multidisciplinary testing common in Silicon Valley. I have found references to this style of testing in 1973 at Kela, the Social Insurance Institution in Finland and attribute some of my learning and enthusiasm on it for long-retired Mervi Hyvönen from Kela.

2023-12-04

In today's video, I am talking about exploratory testing. ET is one of the most powerful test techniques. It provides so much value and insights for software development teams.
Sad but true, many in the industry don't see the value in it and just want to automate all the testing.

Take a look at the video to get an idea about ET in case you never tried it.

Also, let me know, are you performing ET in your team/ company?

📺 youtube.com/watch?v=2gGm_TOIhB

#softwareTesting #ExploratoryTesting #Testing

Sergio Freiredarktelecom@c.im
2023-09-25

How to plan and prepare for exploratory testing? This is a broad topic so I narrowed it down. In my latest article I touch a few points, focusing a bit more on the "what to test". That implies also improving understanding and collaboration, before and throughout the whole process of delivering value in the form of software to our users. Check it out and share your thoughts and experience :)

hubs.li/Q023h0vm0

#ExploratoryTesting #testing #quality #softwaredevelopment #QA

Sergio Freiredarktelecom@c.im
2023-09-07

As more and more teams adopt exploratory testing to test software and hardware, then the question arises: How can we measure its success? It's a hard and broad topic but I took a bit to try to uncover it. Hope it helps or that at least triggers some thoughts and/or discussions in your team. In the end, we learn by exploring, iterating, like in exploratory testing! :)

hubs.li/Q021t1f10
#SoftwareTesting #ExploratoryTesting #QA #Testing

Maaret Pyhäjärvimaaretp@mas.to
2023-09-06

It's fascinating how it is called "using and exploring the feature" while you know the feedback you could get of trying out your changes and "manual testing" when you don't. I don't see these as particularly helpful distinctions though.

#ExploratoryTesting includes looking at your #ProgrammaticTests status, need of updating those, and even seeing if they are trustworthy by using the feature.

Maaret Pyhäjärvimaaretp@mas.to
2023-08-29

This exercise forced me to think about trust while testing. I don't trust my past self. I don't trust others. I need to tell myself to trust (with expiration as a technique) to allow for holding smaller things in my head.

I can control my intent, and box my intent, but my intent grows out of the box in my control, as always with #ExploratoryTesting.

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst