I've included my modified documents, so others can be able to rebuild the DBM files. You may need a Unix like system because of newline conventions. This current 0.30 version is not intended to become "installed", just run everything from this path.
$ ./bin/make_data.sh
This will take a while (48 seconds on my Sun 3/60 :-) and you
hopefully have a working database. Any foo.ext changed
messages are a bad thing, and is probately based on a failure
with packing/unpacking of this distribution.
You can now test XML::Edifact it with:
$ perl bin/edi2xml.pl examples/nad_buyer.edi
You can try other example files, and if you have own EDI files try them: I really want to know how your EDI messages look like, if they break anything, what about your code list extension, ...
Testing different real examples should show some bugs, I hav'nt
thought about. Think about the O'Reilly
invoice or the
Dubbel:Test
and you should catch the clue. I've tried to implement
the UNA
right, but this may need some additional debugging.
Take a look at the difference between the edi.tst files from Frankfurt
and the Springer message. The last one is using newline as a 9th
character in UNA, so its nearly human readable.
To run a complete test, type
$ perl bin/make_spool.pl
This will transform my EDI examples into XML and place them together
with a DTD in the ./spool directory. You already have those files,
they are compared with them in the example directory and, if you
see any foo.bar changed
message, something went wrong.
Lets talk about the perl way of regression test in the 0.4 version.