Hi,
Thank you very much for your evaluation licence
to test the eValid product as well as your follow up email. Our Software
Verification/Validation team is primarily interested in evaluating eValid
to see how easily it can be configured to assis
t our team with functional testing of our product.
We will in the future look to see how eValid can be used further, but
our first interest is primarily field validation/range checking. Our product
has a large number of web based provisioning pages. These provisioning
pages usually have a number of input fields where the customer can enter
their data. When the customer enters their data, there is
validation performed by the web page. This is done using javascript
validation/range checking e.g. a phone number would be checked to ensure
that no alphabetic characters are entered etc.
If the user entered valid data, then a new Confirmation web page
is displayed so that the user can confirm that they would like to
proceed with submitting the details into the database.
If the user had entered invalid data
(e.g. ABCDEF for a phone number), then a Javascript generated Modal
Dialog box is displayed stating which field is invalid and what the
field's valid range of data is. This Modal dialog box contains an OK
button so that it can be clicked away and the user can try again.
We would like to see how eValid automatically:
* Authenticates with the provisioning server (this is a web page i
that requests a username and password and has a submit button).
* Attempts to navigate to a particular web page
* Perform checks to see that the correct web page title
is being displayed before proceeding with testing each
field. If we have not been able to navigate
to a particular web page, then we give up with a fatal error.
* If we have been able to navigate to the correct web page,
proceed to enter valid & invalid data (this data can be
hard coded in the eValid script). We would only
test invalid data in one field at a time to ensure that
the page validation is picking up that particular field
as being i ncorrect e.g. enter ABCDEFG for a phone number
and all other fields containing valid data.
* Confirm that an Error message is generated in
a Javascript created Modal dialog box when invalid data is entered.
* If an unexpected Modal dialog box appears for valid data,
it should be recorded in the eValid completion report
but not hold up the testing of other fields.
* If the Confirmation web page is disp layed when we
have entered invalid data it should be recorded in
the eValid completion report but not hold up the
testing of other fields.
I hope this gives you a better understanding of what I am aiming to achieve
with eValid.
forum.e-valid.com
eValid™ — Automated Web Quality Solution