Hi Marc,
With the PARSE command being the key component of XXXPARSE you can see why I think it would be a perfect verification tool for testing the integrity of any code changes to the parse statement.
So I say again.  Can someone show me how I can get on board and test my XXX parse command to verify new releases?
well, unfortunately, I have not quite understood what you are trying to achieve, so I can not comment on xxxparse per se. (Though from your post it seems to be the case that you are already on "something", which seems to work for you.)

If you are looking for a means to create tests which should assert that the defined behaviour is indeed followed, then I suggest that you employ the "ooRexxUnit" framework, which is modeled after the documentation of "junit" (cf. <http://www.junit.org/>). Just get the attachment from my post to this list with the subject "[Oorexx-devel] testUnit for PARSE (ooRexxUnit-package)", unzip it and read the brief infos in the "*.txt" files.

Then make a copy of "testUnits\ooRexx\base\ooRexx.Base.PARSE.testUnit" e.g. to "testUnits\marcIrvin\xxxPARSE.testUnit" and edit the program. Each method starting with the string "test" represents a testcase and will get invoked and run if you issue "rexx xxxPARSE.testUnit" giving a very brief result about the number of tests carried out, number of successful assertions and number of failures.

So what you would do is add methods starting with the name "test" which each test different parts of the functionality. Use the assertions of the framework, such that they (and possible failures to assert) can be counted. Should an assertion fail then that method will return prematurely (ie. should there be additional code after the failing assertion in that method, then it will not get carried out). Therefore it makes sense, to break up the test-code into functional closely related testcases (= testmethods).

Hope that helps,