From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] udev-test.pl - automatic testing script
Date: Mon, 24 Nov 2003 03:04:05 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106964312230693@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106955971911524@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
On Sun, Nov 23, 2003 at 05:39:23PM -0800, Greg KH wrote:
> On Mon, Nov 24, 2003 at 02:33:42AM +0100, Kay Sievers wrote:
> > On Sat, Nov 22, 2003 at 09:49:18PM -0800, Greg KH wrote:
> > > On Sun, Nov 23, 2003 at 04:54:09AM +0100, Kay Sievers wrote:
> > > > On Sat, Nov 22, 2003 at 03:41:10PM +0100, Kay Sievers wrote:
> > > > > here is a automatic udev test script. To test place it in the test/
> > > > > directory of the current tree to find the sysfs tree copy and run it.
> > > > >
> > > > > The whole test is self contained, it only needs a matching sysfs tree.
> > > > > To extend the test add a hash to the @tests array inside the script.
> > > > > The script checks the created node and prints a summary of all tests.
> > > > >
> > > > > Please don't change $udev_root to something useful, its a temorary
> > > > > directory and will be removed after the test run.
> > > >
> > > > Here is a slightly better version that runs 'tree' on error
> > > > and prints a description for every test.
> > >
> > > Sweet, this blows away my mess of shell scripts. I've added this script
> > > to the test/ directory, thanks a lot for this.
> >
> > We don't want to test the "remove" if "add" fails.
>
> Why not? We should remove the same device, right? That way we end up
> with a clean directory :)
Yes, you are right. If we have two errors we don't want to list
at the second error the node from the first.
But I found two missing characters and optimized $PWD.
You see my queue is empty now :)
thanks,
Kay
[-- Attachment #2: 14-udev-test.pl-i-have-nothing-better-to-do.diff --]
[-- Type: text/plain, Size: 993 bytes --]
--- ../../udev/test/udev-test.pl 2003-11-24 01:23:25.000000000 +0100
+++ udev-test.pl 2003-11-24 03:46:19.000000000 +0100
@@ -21,9 +21,7 @@
use warnings;
use strict;
-my $PWD = `pwd`;
-chomp($PWD);
-
+my $PWD = $ENV{PWD};
my $sysfs = "sys/";
my $udev_bin = "../udev";
my $udev_root = "udev-root/"; # !!! directory will be removed !!!
@@ -80,7 +78,7 @@
EOF
},
{
- desc => "callout result subtitution, only last should match",
+ desc => "callout result substitution, only last should match",
subsys => "block",
devpath => "block/sda/sda3",
expected => "special-device-3" ,
@@ -93,7 +91,7 @@
EOF
},
{
- desc => "callout program subtitution",
+ desc => "callout program substitution",
subsys => "block",
devpath => "block/sda/sda3",
expected => "test-0:0:0:0" ,
@@ -151,7 +149,6 @@
system("tree $udev_root");
print "\n";
$error++;
-# next;
}
udev("remove", $config->{subsys}, $config->{devpath}, \$config->{conf});
next prev parent reply other threads:[~2003-11-24 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 3:54 [udev] udev-test.pl - automatic testing script Kay Sievers
2003-11-23 5:49 ` Greg KH
2003-11-24 1:33 ` Kay Sievers
2003-11-24 1:39 ` Greg KH
2003-11-24 3:04 ` Kay Sievers [this message]
2003-11-24 5:45 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-11-22 14:41 Kay Sievers
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=marc-linux-hotplug-106964312230693@msgid-missing \
--to=kay.sievers@vrfy.org \
--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).