forum.e-valid.com

How does eValid testing for SalesForce compare with use of the SalesForce native test engine "APEX"?

The eValid approch and that used by APEX as part of SalesForce are fundamentally different.

The eValid method is to use control of the browser from outside the browsed page's Document Object Model (DOM) to have the browser do the work of browsing, and then use the abillity to read [and write, though we seldom do that] the contents of the DOM to do the work of testing. For example, validating that a predicted result was present, or making sure that a particular property has a particular value for purposes of playback synchronization.

APEX tests using the DOM APIs but tests are written in a language that is very like JavaScript (JScript).

The problem we see with that approach is that you are using facilties entirely inside the browser to test what the web application is doing, versus the eValid approach that uses external control methods with very low overhead (typically < 0.1%). eValid leaves the browser alone, so the results achieve verisimilitude with what a user actually does. Tricking the browser using instantiated JavaScript (JScript) messes up that assumption.

Which is not to say SaleForce/APAX is a bad approach, but instead to say that the eValid approach is inherently better.

eValid Technology Team