Page 1 of 1

Field Validation Steps

PostPosted: Thu Oct 30, 2008 1:46 pm
by searchnet
I would say at present we are mainly concerned with things like field
validation - what types of characters and max lengths of characters
different types of fields can support. For example if you were filling out
an online form where you have your name, address, mobile number, email
address etc, you would want to be sure that the person filling in the form
can only enter valid data.

Another thing I am testing is that all buttons and links work and point to
the correct place. Then eventually as we close in on completing the
application we will be looking at load and stress testing or basically
seeing what how many requests the server can peform at once and how fast it will function over the internet protocol in comparison how we currently test
it over our local LAN using only a handful of machines.

Any advice will be most appreciated.

Re: Field Validation Steps

PostPosted: Thu Oct 30, 2008 1:47 pm
by regressiontesting
Thanks for writing.

(1) For validation...

* Here is the complete description of eValid's Validation modes: ... ation.html

* eValid has a powerful built-in facility that lets you Validate
page properties in terms of the internal page DOM, and the capability
can also be used to set up Validations that apply Adaptive Playback
to prevent Validation failures when pages experience maintenance: ... bject.html

You might also be interested in the AJAX autocompleter example:

* Here is an example of AJAX usage that shows how several kinds of
eValid commands are used to completely test an AJAX-type
autocompleter function: ... mple1.html

(2) Check out the form and link wizard...

* eValid's wizards give you a great deal of power in generating
complex scripts with minimal effort, as described here: ... izard.html ... izard.html ... izard.html

Bottom line is, I think all you are asking for is present.

Keep on testing and let me know if you have any questions...