And I think it even suits me 
I usually watch and learn how things work. In fact, I don’t like descriptions or instructions, I prefer to watch things happen. And when I feel that I understand it on some level, I take action… and in some cases I can even become a guide for others and use what I have learned by watching
1 Like
manual or automated testing doesn’t exist. if you exactly following a written test case then you are CHECKING that is not testing. Only if you make variations or using exploratory testing, then you are testing. btw you only can automatically check (that is not testing). only designing is testing
1 Like
I always introduce myself as a “lightweight tester” … sometimes with a cough.
So then the other people usually post this: (they made it for when the QA environment is on fire again) “job done”
But mostly I just say I’m Technical QA
I’d describe myself as an adaptable and detail-oriented explorer in the testing realm. Always ready to navigate through uncharted territories to uncover potential issues and ensure the quality of software products and committed to deliver it!
1 Like
By this Seven Kinds of Testers from James Bach I somehow consider my self the first 5 of this.
A administrative, technical, analytical, social, emphatic tester.
Maybe administrative the least. I want to see work properly ordered and status up to date.
But only in a helpful way, not as mean to itself.
The workflow is not working for the team? Change it. NOW!
There is only briefly a share workflow and most details rely on the issue you are working on? The order the work properly issue by issue.
1 Like
A product and UX-focused, straightforward, bold, direct, and effective
1 Like
I’m almost a Sage I think.
Everyone knows I’m in the office though and I’ve only written one book. I think my many testing stories are hilarious as well. I was once called a ‘testing gameshow host.’ Which I took as a complement.
1 Like
I’m an actor pretending to be the real user.
1 Like
For most of my career I’ve like to think of myself as a bug machine.
I was “technical” and used tools. I’d get involved when I could and would try to raise areas of potential defects as early as possible. I often liked to view myself as a great tool for leadership, especially the product owner, as I knew the software and could paint a picture of quality through my testing.
In the past 9 months I’ve had to change dramatically. I’m still that same tester in my blood but I’m something different now - I test people and processes (plus tooling 
) and report on that rather than our software itself.
1 Like
The Social Tester because I like to socialize and get along with people and my colleagues and friends say im good at it
The Day Dreamer
The Tester who has a Listening Ear on always
The Blissful Tester
The Crazy Tester because sometimes i am that.
1 Like
With a different take on this (bare with me)…
I call myself an exploratory tester, plain and simple. Why? Because as testers our career and industry is really really bad at standardising on naming conventions for things. I try to keep what I call myself simple and to the point to help others to understand what I do and how I can help them.
I know that’s not the point of this convo, which is supposed to be lighthearted fun 
1 Like
I’m a tester underneath but my superhero outfit is the clothes of a civilian e.g. a user
1 Like