On Thu, 07 May 2009, June Kim wrote:
> >> 1. It should be easy to locate the failing test in the source code.
> >
> > The output tells the script name and verb name, which are unique.
> > If it is hard to find a place within the code of a single verb,
> > the verb should be revised or split.
>
> The key is reducing the cognitive load. How many step do we need to
> get to the failure point in the code?
>
> 1. read and parse the failure
> 2. copy, paste the file location to open up the file
> 3. ctrl+f to find the verb
> 4. scan through the line
>
> Each step takes time and if there is some non-distinctiveness, which
> happens often, among a few test lines in one verb, the step 4 would
> take a long time.
I think that it can't be done. A contrived example would be the
definition was input from the ijx window. I would use assert for QA
but not for debugging.
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩182 杜甫 蜀相
丞相祠堂何處尋 錦官城外柏森森 映階碧草自春色 隔葉黃鸝空好音
三顧頻煩天下計 兩朝開濟老臣心 出師未捷身先死 長使英雄淚滿襟
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
