I concur with John. Generally, LTKPerl is the
right tool for building tests. The only exceptions
I can think of are tests that are performance
sensitive. Such are a very small minority of
the things an LLRP reader implementor would
like tested.
To answer Kyle's earlier question:
dx101 is a self-test that does not talk to a reader.
It exercises the particular tool kit implementation
to verify its frame decode, frame encode, and XML encode.
I envision all stand-alone self-tests as being
named dx1XX, where XX is the uniqifier kept in
sync between LTK implementations.
More in LTK{C,CPP}/README.TXT
dx201 does talk to a reader. It does much more
than is necessary to achieve its simple inventory
operation. I think it ain't a bad exercise for
a reader implementation. It could be overwhelming
as a starting place.
Regards,
-gww
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of John R. Hogerhuis
Sent: Mon 8/6/2007 9:16 PM
To: LLRP Toolkit Development List
Cc:
Subject: Re: [ltk-d] Reorganize LTK repository -- please comment [heur]
On 8/6/07, Kyle <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was just wondering about the testing tools (dx101 and dx201) that were
> mentioned in this email. We are very interested in testing our reader
> against these. I had a look around the cvs tree and couldn't find them.
> I was just wondering if there was any more information about them
> anywhere (what exactly they test, and how to use them).
>
/LTK/LTKC/Tests
/LTK/LTKCPP/Tests
/LTK/LTKPerl/ has some examples.
For writing tests generally, I recommend the Perl stuff. You need to
write almost no code; you just create your messages with a XML text
editor and LLRP.xsd, you can use the messages as separate XML files or
you can paste them into your Perl code as "here" files. Use transact()
to send a message and get a response, or throw an exception upon
error. monitor() can be used for polling the socket.
Try it, I think you'll like it. You don't need to know much Perl to
write tests with LTKPerl (though it doesn't hurt).
BTW, I asked on the rifidi devel list for help building rifidi and got
no response.
-- John.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
