QA teams can be responsible for a variety of automated test types, including UI, API, performance, and security tests. Many times, I see these auto...
For further actions, you may consider blocking this person and/or reporting abuse
I don’t agree that a single repo will solve these problems. I would be surprised if any devs waited for your changes just because you have a single repo?
All of these problems could be dealt with by having better communication amongst your team e.g. a little conversation explaining you need an aria identifier on an new frontend element ( you are doing accessibility testing? 😄)
A discussion about how you are going to approach a feature from a dev and qa perspective should be had before a story, so each person is aware of what is required.
Yes yes, a thousand times yes! I’ll be forwarding this to my leadership today.