Say that I am a sole QA in a new project, and a first-timer in automation testing in the department (no prior experience or support network). Initial participation in the project (handful of weeks) ran smoothly and even received positive comments from the team. The problem is that in the last sprint, creation of any further testing is blocked due to:
- lack of new features (I've automated what I have available),
- devs do not want me to "test CSS" but only work on visual regressions (without elaborating why, are the design or the requirements expected to change?)
- I only have a local environment and cannot access/authenticate with the "dev" environment, and everyone is too busy to unblock me.
Now, I've been told that as part of this sprint I need to "prove/sell" the idea of automation testing to a high-level manager.
I have already written wiki documentation regarding my setup and what is tested (which I also have in spreadsheet form), I do visual regression with cypress, and I generate mochawesome reports.
Based on your experience, how should I approach this situation? How can I produce a testing plan and potentially track metrics/KPIs that showcase the time earned from not having to do manual effort, or how the tests protect from visual/functional regressions?
p.s. I've read more than 50 potentially relevant questions but I do not think they covered the concerns of my question, so I will attempt to provide some context for my case. Note that I considered posting in "workplace.SE" but I am not concerned about the team dynamics or potential "cost cutting" at this point.