Re: [oiic-formation-discuss] Code walkthrough

["Dave Pawson" <dave.pawson@gmail.com>]

2008/7/1  <robert_weir@us.ibm.com>:
>
> "Dave Pawson" <dave.pawson@gmail.com> wrote on 07/01/2008 10:10:47 AM:
>
>> 2008/7/1  <robert_weir@us.ibm.com>:
>>
>> >> Are tests to include code-walk-through?
>>
>>
>> >> Suggest such testing be put out of scope explicitly within the
>> >> charter. Impractical and subjective.
>> >>
>> >
>> > If there are cases like that which are not testable based on easily
>> > observed
>> > external characteristics of the application, then I suggest we note the
>> > test
>> > case, but state that it is untestable in our test requirements document.
>> >  I'd rather not skip it entirely,
>>
>> I made no intention of skipping it.
>>
>> If you include the feedback in *your* deliverable, it would be duly
>> reported
>> to the main TC as untestable.
>>
>> I'd prefer it to be scoped out as unworkable.
>
> If the work of the TC is to define test cases, then something that is
> untestable is also ipso facto unworkable.


And hence should be reported back to the main TC as such.

Not the point Rob.

Reading (possibly commercial )code IMHO is out of scope for the TC.

-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk