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.

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

@joannalaine @fullsnacktester At the same time, I find it interesting how we so often then end up underemphasising documenting and extending with automation, and the fact that while you code some (individual contribution), you talk some to existence (social software testing). It is always a balance, and learning to play with that balance beyond what each of us does alone is such a key skill (of #ExploratoryTesting).

When I set up the #ExploratoryTesting Foundations course https://dev.to/maaretp/exploratory-testing-foundations-4lb3 and chose E-Primer as target, I ended up surprised with the 34 bugs I listed.

Now I am setting up course with a second target, todo mvc and humouring myself with the completely different experience one can have when one tests the developer's better work. This takes me from foundations to next level: what do you do as tester when devs do more than the bare minimum?

In today's video I am talking about a new tool I found some weeks ago. The tool is called Headlamp test and is a browser extension that helps you while doing your testing activities.

See it in action in the video https://www.youtube.com/watch?v=vRQLz56p2go

#softwareTesting #exploratorytesting #testing

Blogged: The Perpetual Apprentice https://qahiccupps.blogspot.com/2023/01/the-perpetual-apprentice.html #ExploratoryTesting

Going back to #ExploratoryTesting the Verb (doing it) and the Noun (framing it). Some of the techniques I teach around this are on the Verb and others on the Noun, and management approaches can really dilute doing by framing it to a short leash.

RT @darktelecom@twitter.com

I wrote an article about the Exploratory Testing Principles, a first version. Check it out and hope it is helpful.

https://sergiofreire.com/post/exploratory-testing-principles

#testing #exploratorytesting #softwaretesting #QA #quality

🐦🔗: https://twitter.com/darktelecom/status/1618962117494992902

"All actions are gambles" and "tyranny of tickets" are lovely ways of phrasing something I know and struggle to explain. #Testing is not a step in moving a ticket to done. It is hard to describe what good #ExploratoryTesting folks do and @qahiccupps has posted a nice article explaining the multidimensionality of consideration for picking tasks that does not fit jira neatly. https://qahiccupps.blogspot.com/2022/12/granularity-familiarity.html

A prettified model of what we were creating as we were testing #ChatGPT in an #ExploratoryTesting session. Modeling inputs, transformations and outputs was not an easy task for #TestingDozen.

A poem about #ExploratoryTesting.

Thank you @testingtechnews for sharing my blog post on "Using plan-do-study-act to improve testing"
#Testing #SoftwareTesting #TDD #Deming #ExploratoryTesting

https://www.testingtechnews.com/posts/29502231

Blogged: Using plan-do-study-act to improve #testing

#SoftwareTesting #Deming #TDD #ExploratoryTesting

https://testandanalysis.home.blog/2022/11/29/using-plan-do-study-act-to-improve-testing/