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
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
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!
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
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.
Iām an actor pretending to be the real user.
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.
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.
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 
Iām a tester underneath but my superhero outfit is the clothes of a civilian e.g. a user