Callscript Solution

[sumnews]

Thanks for these scripts.

Rupali has successfully did load testing with 5 agents chating with 5
customers with repeat count of 3. We are doing login-acceptchat-logout loop
3 times where as 5 customers repeatedly open support center chat and send
chat requests.

We are getting very close to our use scenario.

What our agents to do is login; wait for chat requests, when then come
accept/process and again go back to wait for chat requests(ie goback in
available state); They never logout; and the URL does not change.

So what we really need is in Agent-chat script after login and sync-on-chat
and process that chat go back to the step where they are again sync-on-chat.
(either we can do indefinitely or few number of times; whatever feasible by
eValid is fine with us).

In this context I was asking for control statements in e-Valid script.
Only GoBackTo command comes to closest to our needs. I do not think it will
work with us. As you see after the agent logins the URL does not change. It
is like gmail or google spreadsheet application. After login, the URL need
not change; the application state changes and what is being displayed
changes.

Please help me or let me know how we can work around/resolve this.

Thanks,

[functionaltesting]

We can think of several solutions to this.

(1) Put the script you want to repeat in a separate file, e.g.
synconchat.evs, then:

CallScript synchonchat.evs.
CallScript synchonchat.evs.
CallScript synchonchat.evs.
CallScript synchonchat.evs.
CallScript synchonchat.evs.
CallScript synchonchat.evs.
...

(2) You can amplify this by making a script called 10synchonchat.evs
that does the above 10 times, then...

CallScript 10synchonchat.evs.
CallScript 10synchonchat.evs.
CallScript 10synchonchat.evs.
CallScript 10synchonchat.evs.
CallScript 10synchonchat.evs.

to get 50 total...etc.

(3) Script A.evs is actually prohibited from CallScript A.evs (which
would be recursive)...did you try this? But -- a little secret here --
if you have A.evs calling B.evs, B.evs can call A.evs, and now you
have an infinite loop. Yeah, not clean, but it really is infinite.

Good practice is to use some kind of OnErrorGoScript in each one so
it escapes the loop in some way.

(4) You can use the EPI interface, but this requires writing the
script in C++ and creating an executable with your local C++ compiler...

In that case you could have a function that you invoke inside a while
or a for...etc.

The eValid Programmatic Interface (EPI) is described in detail in this
this introductory page:

http://www.e-Valid.com/Products/Documen ... ction.html

But at this point you probably don't want to do this...

Of these four, I like (1) and (2) the best...