Re: Q: Designer, forms testing, automation

From: Malcolm Dew-Jones <yf110_at_vtn1.victoria.tc.ca>
Date: 26 Jun 2006 11:37:33 -0800
Message-ID: <44a0296d$1_at_news.victoria.tc.ca>


[Quoted] Frank van Bortel (frank.van.bortel_at_gmail.com) wrote:

: DA Morgan schreef:

: >
: > I personally think of Designer as one of the worst places to build and
: > test forms.

: I will disagree with you on the builing part. Personally : speaking, of course :)

There are lots of forms, they all work reliably relative to the definitions of what's in each form, so Designer seems "good enough" for all I care here.

And no, the user in this case doesn't get much say in whether a box is mauve or not (suitably amused) - if a field is on the form, has the right length, etc etc, then it's good enough for the user to be able to do their job, that's all that counts here.

The data has lots of constraints on what is allowed and who can do what to it, often depending on the values of the various fields. For example, which details can be modified about an item might depend on the contract with the facility that is storing the item, and what roles the user has, and what time of day it is.

The code for that is all in designer as a series of constraints. Designer copies it all into the various forms, all is well, but are the correct rules then in the correct place in all the forms? and do the rules all interact correctly?

It ought to be feasible to pull out all the code into a format that could be tested in some kind of batch mode, and then have reams of test cases that call the constraint code just like it would be called in the form, or maybe create a routine in the form to push values into the fields and then fire the triggers, or something. I will likely come up with that something over time, but first I thought I'd check for what existed. Received on Mon Jun 26 2006 - 21:37:33 CEST

Original text of this message