Test automation is typically introduced into a project to address issues such as repetitive manual work, working with large datasets, or getting faster feedback in the CI / CD pipeline. Because of this buzz around test automation, you might consider automating “everything”. You may have already chosen a testing framework and a team that will perform test automation. But have you seriously thought about what you should automate or how feasible it is for you?
. . , , , , , . , , , , . : , UI . , .
, , , , , , . , . . , , , .
/, , .
, , . CI / CD, , . , . , , , . :
, , /-, , .
. . , -, . , , .
. CI/CD . , QA, .
, . , , , . . , :
, , . .
. , , . , , , .
, .
, , , , , . , . , , , . . , , , . .
,
. - . , . ( Dev, QA, Staging, Integration PROD), . , , . CI, CircleCI, , , . , , .
, . , , . , , , . , , . , Fandango - ( 36 ), , « : ». , . QualityWorks , , . , , , - .
, , , QA. . QA, , . «» . , , , . , , - , , , .
Translated by the QApedia team . You will find even more translated articles on our telegram channel .