I’ve seen this question pop up so often recently in various forms!
how we make our day to day activity as testers visible to stakeholders (devs, management, etc)?
@ckenst had some excellent advice about this when the latest question came up:
My suggestion is to talk with your stakeholders and figure out the best way for them to consume this.
which @tybar backed up with
This…I spent way too long at the start of my career trying to write up lots of documentation that no one ended up reading…figuring out what people actually want to know from your work is pretty big.
IMO the best way to increase the visibility of your testing activities by making the outputs of said testing visible to the stakeholders who matter to you. This might be through narrative testing reports (perhaps with screenshots and a list of findings) on Jira issues, or via a test results dashboard that shows recent runs of your automation. You could also make it so that certain automation failures block deployments, which would have the secondary benefit of making your colleagues aware of the specific guards you have put in place to stop certain feature regressions from being deployed.
What have you tried to make your testing visible to your stakeholders?