Hi Alexei,
Thanks for your detailed response:
The only section of your comment I don't quite get is:
"You must treat test automation as a 'smaller
development project within the bigger one'. Your automation efforts must be
correlated with the development flow and this must be done from the very start
of the development."
Right now what is happening is:
We have a sprint, we are attempting to automate, then spend a lot of time fixing the automation. Then new code/changes are introduced (though it may not be in the particular section we automated) yet the automation run gets broken.
I'm wondering would it make more sense to just automate when the application is more stable & there aren't as many high chances of new code constantly being introduced?
