aktime wrote:Can you tell me more about what it means, "Browser User"?
A "browser user" is a term we use in describing how eValid handles server loading.
The basic idea is, a user is represented by a test script that tells eValid what to do to act like a browser. Then, to generate load on your application eValid runs multiple instances of itself, with each one running its own script. We call these independent execution threads "browser user" or BU.
In practice, a single Windows machine can run upwards of 100 BUs per user partition, where the advantage is that each BU can be running its own script. They can all be alike or they can all be diferent.
The main point is that in terms of the load imposed on your server each BU is a 100% realistic user.
The eValid Team
by aktime » Wed Jul 28, 2010 2:31 pm