Over the years, I have been senior to a lot of testers. I've been in the position to refuse to give them work. I have been in the position to select what their primary focus in teams becomes. I've been in position to influence the fact they no longer work with the same thing.
Being in position of this kind of influence does not mean you have to be their manager. It means you need to have the ear of the managers. So from that position, inspired by the conversations we had with Exploratory Testing Academy Ask Anyone Anything session, I am going to give you advice on how to work to be appreciated by someone like me. (note: it means NOTHING really, but a thought exercise)
Let's face it: not all testers are that great. We all like to think we are, yet we don't spend enough time in thinking about what makes us great.
So lets assume I don't trust your testing and you want to change that - a tongue-in-cheek guide to how-to.
1. Talk about your results
I know I can search your bugs in Jira and no matter how much folks like me explain that not everything is there, in reality a lot of it is there in organizations that believe that work does not exist without a card in jira. Don't make me go and search.
Talk about your results:
- the information you have found and shared with the developers ("bugs")
- the information you have found and could teach others ("lesson learned", "problems solved")
- the changes in others you see your questions are creating
- the automation you wrote to test, the automation you rewrote to test, the automation you left behind for regression purposes
- the coverage you created without finding problems
- Had a fruitless argument over terminology with someone on the internet
- Set up a weather API and tried mocking it
- Read the BDD books - Formulation that I have been planning on getting at all week
- Played a fun game of Don't Starve Together