forum.e-valid.com

Afternoon.

Great product you have there, very flexible.

A quick question for you:

How do you interface into the Windows system when your tests has a lot of windows and tabs open?

Thanks

TGehring wrote:Afternoon.

Great product you have there, very flexible.

A quick question for you:

How do you interface into the Windows system when your tests has a lot of windows and tabs open?

Thanks

Thanks for posting TGehring.

You have a couple of options in eValid to communicate to the outside world:

The command: SystemCall "command" will run the "command" as a command-line execution for you.

If you want eValid to wait until that command finishes running, then you use the command: SystemCallWait "command"

In either case, please be warned that if your "command" does something weird, then eValid can't be held responsible.

As a further caution, you ought to know that if you happen to issue or use the command: WindowClose 0 this tells eValid to close the window with wid = 0, which is the current instance of eValid itself.

So don't be surprised if this does actually what you tell it to do, which is turn itself off.

We left this without checking because, who knows, someone might want to do that!

-- eValid Support