|step...@systml.co.uk||Sep 21, 2007 2:19 pm|
|Dave Pawson||Sep 21, 2007 10:10 pm|
|step...@systml.co.uk||Sep 22, 2007 1:47 am|
|Dave Pawson||Sep 22, 2007 2:06 am|
|step...@systml.co.uk||Sep 22, 2007 2:46 am|
|Dave Pawson||Sep 22, 2007 5:25 am|
|step...@systml.co.uk||Sep 22, 2007 1:43 pm|
|Dave Pawson||Sep 22, 2007 10:09 pm|
|step...@systml.co.uk||Sep 23, 2007 5:37 am|
|step...@systml.co.uk||Sep 23, 2007 5:51 am|
|Dave Pawson||Sep 23, 2007 6:11 am|
|step...@systml.co.uk||Sep 23, 2007 8:22 am|
|Dave Pawson||Sep 23, 2007 9:15 am|
|Subject:||Re: [tag] TA Model|
|From:||Dave Pawson (dave...@gmail.com)|
|Date:||Sep 22, 2007 2:06:47 am|
Without a test result the test is a waste of time. It may be an interim result eventually discarded, but there needs to be a result.
So following this through, if the result is a mandatory element of the flow but the other elements (I use the term element not necessarily in the XML sense) are all optional,
In what sense are you using 'element'? We seem to have quite different vocabularies.
A test? A TA? Something else?
then a flow can
at its simplest be just a formalization (perhaps in an expression language evaluating to a boolean) of the prose or pointer
-TA --prose --pointer --flow ---result
flow? The above list looks like its the process steps from reading a requirement through to running a test?
The more complex flow would cover joining flows together with in a series say where conditions guard the join between a result and the next trigger
-TA --prose --pointer --flow ---trigger ---result ---post --flow ---pre ---trigger ---result
Interpreting this into a test environment, is this the same as saying that running test n+1 depends on the success / failure of test n?
If that's the case, I'd agree, and note that 'test flow', i.e. the sequence of tests to be followed on any test run, has not been clearly addressed. Most generally, it utilizes the test numbers/ID values of tests. Then any test has
if pass, goto TestNumber XXX | Test(id='XXX') else goto TestNumber YYYY | Test(id='YYYY') fi
Perhaps an attribute in each element
Suggest that's insufficient, if my understanding of the terms is accurate.
I've not seen any evidence that XML is helpful here.
I was thinking there could be something in the model which describes the evaluation of the expression used (irrespective of whether it is XML), like:
-TA --prose isTrueFalse=true --pointer isTrueFalse=false --flow ---result isTrueFalse=true
Sorry Stephen. I've no context into which that may be placed. I dont understand it.
I still think any constraints forbidding keywords 'MUST' are best applied just to the flow, not to the prose and certainly (of necessity) not to the pointer/reference.
I think it would be folly to prohibit words from any TA. All it needs is clarity in terms.
-- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk