bing wrote:How do you determine the simple set of rules you call a "recording protocol" when you start working with an application?
Just to be clear on this, a "recording protocol" is a short set of rules on how to use eValid on a particular application. We call it a "protocol" because it refers to the way you set the various options and how you make a recording -- the goal is to make a recording that plays perfectly without requiring modification.
99% of the time you don't need this. But in the other 1% you probably need to have an application-specific little list of DO's and DON'Ts -- that list is your "recording protocol". The rules that work on one place of the application more than likely will work in all places in the application because in most cases web applications are developed in a uniform way.
The way WE create the protocol for a particular application is to make a number of "throw-away" recordings just to find out what, for
THAT application works and doesn't work. In other words, we concentrate on gaining experience first.
Once we have a good feel, then we proceed to the step of writing down in a short memo a series of instructions that read like this: "When you see X, then you record it by doing Y..."
Another important added note is that your protocol probably will never be quite complete...we find that we often are adding our short instructions (injunctions) even out to the end of a project.
The eValid Team
by bing » Mon Dec 13, 2010 5:42 pm