Testing reports

[Derek Atkins]

"Colin Scott" <gnucash at double-bars.net> writes:

>> So basically what you would like to test is that the normalized HTML
>> output is "the same".  This would require:
>
> Actually, no.  Were I doing this I would automate a test for whether
> the HTML text has changed.  At the point a change is found, it would
> probably require human intervention to see what has changed and why -
> *any* change is an error unless there is a legitimate reason for it,
> and automating the legitimacy test is probably too expensive a task to
> be worth doing.

Define "html text"?  For example, would you consider this:

  <A HREF="foo">foo</A>

and this:

  <a href="foo">foo</a>

to be the same or different?   What about:
  <a href="foo">foo</a>    and    <a href="bar">foo</a>
?

To me I would normalize in such a way that the first two would be
considered "the same" but the second two would be considered
"different".

I'm not sure how I would implement that, tho.  But those would be my
requirements.  Similarly, I would want these two to result in a "match":

  <p>This is a paragraph</p>

and

  <p>This
  is
  a parahraph</p>

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available