From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Hollis Subject: Re: Fw: Network driver test suite? Date: Wed, 12 Jan 2005 11:24:24 -0500 Message-ID: <1105547064.5940.5.camel@dhollis-lnx.centricconsulting.com> References: <20050105152635.290ad9c0@dxpl.pdx.osdl.net> <1105493554.28674.49.camel@bullpen.pdx.osdl.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-YVP34LeWtuxlMyQ4Q1by" Cc: netdev@oss.sgi.com, cliffw@osdl.org, shemminger@osdl.org Return-path: To: Craig Thomas In-Reply-To: <1105493554.28674.49.camel@bullpen.pdx.osdl.net> Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org --=-YVP34LeWtuxlMyQ4Q1by Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2005-01-11 at 17:32 -0800, Craig Thomas wrote: >=20 > Would there be a desire for someone to collect the tests or at least > create an index to all their locations? If so, then developers can > scan a library of potential tests to run against newly developed code. >=20 > OSDL can start incorporating some of these tests into their test > platform as well. I would love to see a collection of the types of tests that should be performed. As it appears now, there is nothing defined that a driver author should do to verify that their driver performs properly, or supports the right capabilities etc. Some things may be difficult to automate, but simply having a checklist would be great. For the things that can be automated, that would be even better. --=20 David Hollis --=-YVP34LeWtuxlMyQ4Q1by Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQBB5U83xasLqOyGHncRAkaZAJ0Xr9DaurPOGiFGpTUZLiIa8Ech2QCeK0gn bwrt/78Ido63QRgggnCetZo= =bFzE -----END PGP SIGNATURE----- --=-YVP34LeWtuxlMyQ4Q1by--