How does eValid's EPI compare with, say, VS2010 in C++?

[mf209]

How does eValid's EPI compare with, say, VS2010 in C++?

[eValid]

How does eValid's EPI compare with, say, VS2010 in C++?

These are two entirely different beasts, it turns out.

VS2010's C++ "coded tests" compile and execute at the desktop level using COM resources and, through the COM interfaces, DOM facts when needed.

eValid's C++ EPI results in an executable that drives the eValid browser directly via the DOM interface.

As you may be aware, eValid regular playbacks can occur in multiple instances on the desktop -- that's how we do server load generation. And, when you convert a scipt to EPI format and compile it with the EPI DLLs, you also get an executable that can be replicated on the desktop.

VS2010 tests don't have that kind of scaling, whereas eValid tests do scale very nicely.

(This is just a surface layer of the full answer, by the way, because there are many other ways in which eValid is deeply different from VS2010 -- and in many ways complements VS2010 when it is applied specifically to testing web applications.)

eValid Support