Database Connectivity

[unsigned]

While I was working on your product, few questions crossed my mind. Just
wanted to get them cleared, thats it.

If you don't mind please clarify the following queries.

1. Provision for Database Connectivity.

2. If we want check any input field for different values class of test data.

Thank you,

[functionaltesting]

Thanks for writing...

Did you get the two responses from last night? It appears
the first one answered some of the questions you also asked
in the second one, so in the second on I referred to the
first one's answers.

Please confirm you got them both.

1. If your applications connects to a database then that operates
normally because, as you have seen, eValid is a complete
browser.

Some users want to vaklidate database activity and that is
perfectly ok if you have a web page to that shows what
you want to validate. To eValid that is "just another web
page" -- I mean, eValid sees that as a web page and treats
it normally.

If you mean, does eValid data fit into a database, the answer
is no -- at least not directly. EVERY output file in eValid
is blank/white-space delimited and CSV-style versions of such
files as the EventLog are trivial to construct.

Basically, to interface eValid outputs into SQL you
use existing facilities in SQL to import a CSV file...

2. If you are filling in a value from a script, the value
is shown in the script.

If you want to confirm the content of a field you can
use ValidateSelectedText if you can highlight the field,
or you can use ValidateSelectedObjProporty if you can't
(but then you'll have to look up the DOM index and the frame
path with the PageMap).

* The eValid PageMap facility -- which reveals the contents of the
current page eValid is showing you -- gives you a direct look into
the document object model (DOM) of the page. Here's how to use it:

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

N. I'm concerned that all of these questions are kind of
peripheral to the thing that I understood you were doing,
which was to confirm eValid operation in functional testing
and server loading.

There are many alternative designs for test engines, and eValid
steers a course between 100% power and operational simplicity.
We do this to keep costs in line and also to make eValid very,
very easy to use.

Are there specific requirements you're matching eValid up against?
Perhaps if you could list your requirements I could match them
up with eValid capabilities?