From: "Nick Yin" <nickyin@hotmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: some udev code coverage results
Date: Wed, 28 Apr 2004 01:01:10 +0000 [thread overview]
Message-ID: <BAY7-F85QqeViRi3yk700013e2d@hotmail.com> (raw)
In-Reply-To: <1083019150.26612.148.camel@ibm-d.pdx.osdl.net>
Greg,
I will try to work out some test scripts for udevinfo, udevstart, udevtest
binaries when i have more time. In fact there have been some test scripts
for these binaries in our inner test but those are not so good to put them
into source tree. I will improve them and then submit them to you.
Nick
>From: Greg KH <greg@kroah.com>
>To: Leann Ogasawara <ogasawara@osdl.org>
>CC: Nick Yin <nickyin@hotmail.com>, hotplug
><linux-hotplug-devel@lists.sourceforge.net>, Mary Edie
><maryedie@osdl.org>
>Subject: Re: some udev code coverage results
>Date: Tue, 27 Apr 2004 09:43:13 -0700
>
>On Tue, Apr 27, 2004 at 09:34:16AM -0700, Leann Ogasawara wrote:
> > Hi Nick,
> >
> > I do not have a test suite for the whole udev project and thus have no
> > results to compare with yours :( I was only reporting on the results of
> > the tests provided by udev. I have rerun gcov for udev for all the udev
> > tests including udev/test/udevd/udevd-test.pl and enclosed the results
> > below (link also provided). Greg, would you be interested in patches to
> > expand/add some udev tests to hit the untouched portions of code or are
> > you satisfied with the current coverage provided by udev/test/?
>
>Code coverage reports by themselves don't really mean anything. But if
>you have real, useful tests that exercise the functionality of the code,
>instead of just trying for complete coverage, that's useful.
>
>So yes, I'm always interested in adding more tests to the test script to
>try to exercise more functions in udev, mainly to make sure we don't
>break anything in the future, and to validate that everything works
>today (much like your last patches did.)
>
>thanks,
>
>greg k-h
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
>For a limited time only, get FREE Ground shipping on all orders of $35
>or more. Hurry up and shop folks, this offer expires April 30th!
>http://www.thinkgeek.com/freeshipping/?cpg\x12297
>_______________________________________________
>Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
>Linux-hotplug-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8.
http://join.msn.com/?page˛atures/junkmail
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-04-28 1:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 22:39 some udev code coverage results Leann Ogasawara
2004-04-27 1:03 ` Nick Yin
2004-04-27 16:34 ` Leann Ogasawara
2004-04-27 16:43 ` Greg KH
2004-04-28 0:56 ` Nick Yin
2004-04-28 1:01 ` Nick Yin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY7-F85QqeViRi3yk700013e2d@hotmail.com \
--to=nickyin@hotmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).