DEV Community

Discussion on: Stop Creating a Repo For Your QA Automated Tests

Collapse
 
turnerglynnmark profile image
Mark Turner

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.