Ideally, I'd like to start writing automated test scripts once all my test cases are completed AND and I have an application. Usually, this is never the case for me and I have to write the automated test scripts between builds. I'm not saying this is the right way but this is what would be ideal, and what works for me.
Definatively verify? Not me... but I can say that based on everything I've read recently, and research I've done, that would be a true statement, or at least 'one of the' leaders. The 'ideal' time is exactly when they're doing it, but in most environments that is impossible to achieve.
I'd have to agree with Droman - I define and plan for automation, and it generally ends up being completed in between builds, or at the very least after the first baseline is completed.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Jules: Our automation specialists start writing scripts as soon as there is a reasonably firm system design or specification.
It takes a lot of close communication with the developers to achieve this.
They only need the actual system to record navigation and object recognition plus a bit of tweaking to get it going.
Very impressive stuff and they claim to be world leaders with this approach. Can anyone verify this claim?
I can verify that they are, indeed, world leaders.
By the way, who is "they"? George Bush? Tony Blair?
- Joe (firstname.lastname@example.org)
[This message has been edited by jstrazzere (edited 10-11-2001).]