Answer the question
In order to leave comments, you need to log in
How to organize autotests when the project is actively changed?
We have a web project on which a fairly large number of developers are working, and only 1 QA who is engaged in automation, so there is often a problem when some pages are changed before these changes are made to auto tests and they fall accordingly during the build. Are there any good practices in such cases, or is it just to cut down the tests?
Answer the question
In order to leave comments, you need to log in
We always had a problem with autotests, I could have such a solution: organize autotests so that it would be convenient for programmers to add / change scripts. Programmers would then use them themselves during work.
This can either be your custom solution, or you can switch to BDD altogether. (Read, for example, here habrahabr.ru/post/52929 )
and at least write in the tracker in the test format :)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question