RenatoB wrote:Afternoon:
I'd like to know: How does eValid at the EPI level compare with Visual Studio's
CUIT system?
Thanks
Hey RenatoB:
In case you are aware, the EPI interface in eValid lets you create a C++ script that, when you compile it, will run the commands that correspond to the script if you run it in eValid in the normal natural mode of playback.
The CUIT system introduced with VS2010 is very similar. During test recording CUIT constructs C++ (or other language variants) code that capture the user actions. It uses some of the same kinds of signals that eValid uses to extract critical information about how the user interacted with the application while it was in the browser.
So superficially, CUIT is a kind of subset of the EPI interface.
eValid's interface offers simplified synchronization and validation commands...you don't have to write C++ or C# code to do basic actions.
Also, many eValid features such as natural playback synchronization and adaptive playback are already "built in", whereas they have to be custom programmed in CUIT.
--eValid Support