#exploratorytesting — Public Fediverse posts

@eatyourgreens Ah yes. That old apostrophe gets 'em every time 🙄
#ExploratoryTesting

“These stakeholders share a common concern, and that's the risk we should be migitating with testing. First.” https://elizabethzagroba.com/posts/2021/complete_the_main_quest_first/ #ExploratoryTesting

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.
https://speakerdeck.com/maaretp/exploratory-unit-testing-with-and-for-genai

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.

Udita Sharma's and my #AgileTD 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 😁

https://agiletestingdays.com/2024/session/collect-your-explorer-badge/ #exploratoryTesting

Udita Sharma's and my #AgileTD 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 😁

https://agiletestingdays.com/2024/session/collect-your-explorer-badge/ #exploratoryTesting

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.

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

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 :)

https://hubs.li/Q02HZQTY0

#softwaretesting #QA #quality

[Blog] Gilded Rose for Exploratory Testing
https://visible-quality.blogspot.com/2024/08/gilded-rose-for-exploratory-testing.html

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. :)

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.

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

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.

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.

#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.

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 :)

https://hubs.li/Q023h0vm0

#ExploratoryTesting #testing #quality #softwaredevelopment #QA

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! :)

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

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.

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.

I did two 1:1 benchmarking sessions this week. One with Pedro Pimenta where we compared notes on supporting #ExploratoryTesting and another with @joeposaurus where we compared notes on facilitative roles.

Our #Playwright learning group transformed into regretful managers peer support group.

Next week I also have one ext conversation already scheduled. I get a lot of our these meaningful conversations, they inspire me, they drive my thinking and provide ladders to the answers I am seeking.

Modeling #ContemporaryExploratoryTesting, bits worth remembering.

Meeting another company's managers reminded me that we model what and where is #ExploratoryTesting very differently. Instead of drawing the box of exploratory testing that includes all worthwhile parts of test case -based testing, I split this to timeline of activities.

#ExploratoryTesting is about extending with research not sticking to anyone’s prefiltered information.

Second release ongoing with <10 days for this old thing. Well, going from 40 days to 10 days is quite significant.

Now that we don't do stupid testing, we should have some time available to do smart testing. Cutting away the unnecessary is much easier than replacing it with what we have always missed out on. #ExploratoryTesting

For a year, I was disciplined with writing down acceptance criteria. I learned that my best effort before left 20% for me to find while doing #ExploratoryTesting. I systematically collected also ’the NO list’ of acceptance criteria I thought could be in scope but clarified what was not. Yesterday I pasted a year of incremental acceptance criteria on a page. 18 things from ’the NO list’ had vanished but all acceptance criteria remained valid. Surprised.

Results and outputs of #ExploratoryTesting can be bug reports, but they can also be better testers, authoritative documentation, or test automation.

‘But #ExploratoryTesting means they test only with their understanding and point out everything that might be a problem’ is such a misrepresentation of opportunity-cost aware learning-centric testing. Results of value are not ‘all bugs’ in all projects. Sometimes exploratory testing produces authoritative documentation.

Blogged: Am I Wrong? https://qahiccupps.blogspot.com/2023/05/am-i-wrong.html #ExploratoryTesting

Collecting things that should be repeated more. Like this one.

There is a reason why #ExploratoryTesting does not use those and instead discusses things like charters and session notes.

Testing vs. Checking is making rounds again on LinkedIn to the extent that the number of new people jumping to correct my language of "tests" to "checks" is approaching overwhelming.

I think the language correction - and this particular language correction - hasn't driven a positive change in the last 10 years even though I have a sense of small improvement on understanding #ExploratoryTesting and #AutomationInTesting (#ContemporaryExploratoryTesting).