Hi Vladimir, || -----Original Message----- || From: [EMAIL PROTECTED] || [mailto:[EMAIL PROTECTED] On Behalf Of Vladimir || R. Bossicard || Sent: maandag 24 februari 2003 12:21 || To: [EMAIL PROTECTED] || Subject: Re: Tests and other things || || || so why the "insert before" and "insert after" methods if || only a "insert" || method is needed? (I'm sure I'm missing the point, but I ask || nevertheless :-) )
Are you asking me a fundamental question the existence of an insert-before and insert-after method in the WD or are you wondering why insert-before and insert-after are tested when there is no order in the attributes defined? In the latter case I think the answer is because XUpdate allows you to use the insert-before operation on attributes it should be tested even though the result is the same using the insert-after operation. My aim with setting up the unit-tests for Lexus was a sort of exhaustive set of simple use-cases that can also be used for educational usages. || I'm maintaining junit-addons on sf (collection of classes || for JUnit) and || if you want to donate the NodeMatcher class, let me know || :-) I'm sure || this class will be very helpful to other users. If you maintain the name XhiveNodeMatcher and keep the reference to our company in the top of the file (like it has right now) you can use it in the junit-addons project on sourceforge. Regards, Jeroen -- X-Hive Corporation e-mail: [EMAIL PROTECTED] phone: +31 10 2818080 http://www.x-hive.com ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
