headers
Trygve Laugstøl | 1 Aug 2010 02:11
Picon

TCK documentation

Hi Dan and gang

I was wondering if there is any extra documentation on what tests the 
TCK suite actually is performing? I'm having a hard time following the 
logic in the more advanced TCK tests. I'm looking for the list of 
configurations/interfaces/endpoints and their expected behavior in 
particular right now.

--
Trygve

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
Permalink | Reply | 1 comment |
headers
Dan Streetman | 9 Aug 2010 17:02
Picon

Re: TCK documentation

Hello,

To be honest, I was only primarily involved in developing the
javax.usb API and implementations - the TCK work was done by some
other IBM developers and testers and I was only consulted for
clarifications.

I believe all the documentation on the TCK is in the package's docs/
directory.  The PDF file in there should describe all topology
configurations that the TCK expects, and the behavior of any
endpoints/pipes where communication is tested.

If there are any TCK tests that are wrong, or any that have specific
dependencies that are no longer reproducable (like on a specific
device that's no longer available), please do let Brian (and the
mailing list, and me) know.  The TCK should be runnable by anyone,
with reasonable restrictions (like needing a single USB dev board).

Thanks for doing this implementation work, it is definitely needed!

2010/7/31 Trygve Laugstøl <trygvis <at> inamo.no>:
> Hi Dan and gang
>
> I was wondering if there is any extra documentation on what tests the
> TCK suite actually is performing? I'm having a hard time following the
> logic in the more advanced TCK tests. I'm looking for the list of
> configurations/interfaces/endpoints and their expected behavior in
> particular right now.
>
> --
(Continue reading)

Permalink | Reply | 0 comments |

Gmane