Where to keep your UI automation tests?
I had to work in different projects and different teams with completely different approach to automation and places of storage of UI automation tests and the most common are: Keep UI automation tests in the same repository with code of the application Keep UI automation tests in different repositories saving the link between them (e.g. maven pom.xml) Don’t store automation in the repository in general I don’t want to talk about the last approach since it is NOT a correct way of working. Let’s describe pros and cons of the first two. Keep UI automation tests in the same repository Pros You don’t need to update the link between versions of code and tests Higher standards to quality of the automation since failures are highly visible and very sensitive Developers will become aware if test are breaking after applying application code changes. Easier to involve developers in test development and maintenance Easier to add test execution to CI/CD pipelines Cons If...