3

IMHO, if your UI changes so often that your tests become utterly redundant over a single Sprint - which I am assuming is a 10-15 day period, then the actual issue lies with your UI developers rather than the QA/Testing team. Your UI team should focus on how to minimize the extent of impact of their changes. Completing a project, on time, with good quality, ...


3

I don't think there is a specific recommended test length threshold, but here are some of the things we've taken into account: measure code complexity of your tests and specify practical thresholds (we use grunt-complexity) enforce one top-level describe per file - this helps to avoid having multiple tests inside a single file group test specs by a "feature"...


2

This is completely ok, we did exactly the same for a while. I assume this is for historical reasons (it was in our case)? But in general, you will try to have the smallest number of systems possible. So for the medium future, it probably makes sense to unify on either SVN or Git(hub) as repository.


1

First of all follow the Page Object Model architecture to least the efforts. For reference follow the https://www.guru99.com/page-object-model-pom-page-factory-in-selenium-ultimate-guide.html Further QA testing companies while automating a test case or scenario prioritize the use the identifiers in order id > class > name > CSS and then least ...


Only top voted, non community-wiki answers of a minimum length are eligible