greenbay wrote:We've been comparing eValid and LoadRunner/TruClient and we're wondering, at a design level, why eValid makes so much detail explicit...rather than hiding detail and "making things work" no matter what, like TruClient does?
This is the kind of philosophical question that could take hours or days or more to answer completely. But, to save time here is the short answer.
A fundamental idea of eValid approach to the design of a web test engine is to
tell the user the truth. In QA/Testing/Performance Analysis work you
must have 100% confidence in what is going on. So, eValid, in attempting to comply with this commonsense rule, errs on the side of perhaps giving too much detail, rather than too little.
But there is an even deeper reason why eValid outputs are so explicit, and that has to do in the rare case when an eValid requested operation doesn't work as expected. It is crucially important, if you mean to maintain the credibility of the output of an engine like eValid, to
NEVER mask the truth from the user. Even if the truth that's revealed is unpleasant.
In other words, full disclosure combined with verifiability implies trustworthiness.
eValid Team
Posted: Mon Feb 07, 2011 3:34 pm