From: Bill Walton <bill.walton@...>
Date: 2008-07-07T22:43:57+09:00
Subject: advice needed on testing strategy

------=_NextPart_000_0060_01C8E00C.6BE135D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greetings!

I'm working on a library that wraps REXML processing of a specific XML =
format (CCR - Continuity of Care Record).  The objective is to process =
the XML so that the developer doesn't have to.  So, for example, I can =
do...

ccr =3D RubyCCR::Document.open('demo.xml')  #open file / read the XML =
into a set of objects
ccr.actors.each do |this_actor|
    @first_name =3D this_actor.current_name.family
    @last_name =3D this_actor.current_name.family
end

From a testing perspective, my objective is to make sure that all the =
content in the XML file actually ends up in the appropriate objects / =
attributes.  Right now I'm loading specific XML files per testcase / =
test and hardcoding the expected values in my unit tests based on =
knowing what's in the XML file being loaded.  This seems wrong.  If =
anybody's got a better idea, I'd sure appreciate hearing it.

Thanks,
Bill
------=_NextPart_000_0060_01C8E00C.6BE135D0--