d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
5e86a307e8
freebsd-nq/tools/regression/geom_gpt/gctl.t

208 lines
7.3 KiB
Perl
Raw Normal View History

Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.
2005-09-19 02:59:09 +00:00
#!/usr/bin/env perl -w
#
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
# Copyright (c) 2005, 2006 Marcel Moolenaar
Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.
2005-09-19 02:59:09 +00:00
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
# IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
# OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
# IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
# NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $FreeBSD$
my $srcdir = `dirname $0`;
chomp $srcdir;
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
my $cmd = "/tmp/gctl-$$";
Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.
2005-09-19 02:59:09 +00:00
my $out = "$cmd.out";
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
my $disk = "/tmp/disk-$$";
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
my $mntpt = "/tmp/mount-$$";
Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.
2005-09-19 02:59:09 +00:00
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
my %steps = (
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"000" => "gctl",
"001" => "gctl verb=bogus",
"010" => "gctl verb=create",
"011" => "gctl verb=create provider=bogus",
"020" => "mdcfg create pristine",
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
"021" => "gctl verb=create provider=%dev% entries=-1",
"022" => "gctl verb=create provider=%dev% entries=128",
"023" => "gctl verb=create provider=%dev%",
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
"024" => "gctl verb=modify geom=%dev%",
Update to match geom_gpt:1.35 o Change the result of gctl(001) now that a bogus verb still requires a valid geom, o Insert gctl(024) to test for an appropriate error when a bogus verb is given that does have a proper geom parameter.
2005-11-13 22:02:04 +00:00
"025" => "conf",
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"030" => "gctl verb=add",
"031" => "gctl verb=add geom=bogus",
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
"032" => "gctl verb=add geom=%dev%",
"033" => "gctl verb=add geom=%dev% type=bogus",
"034" => "gctl verb=add geom=%dev% type=ed0101b0-2a71-11da-ba81-003048416ace",
"035" => "gctl verb=add geom=%dev% type=ed0101b0-2a71-11da-ba81-003048416ace start=1",
"036" => "gctl verb=add geom=%dev% type=ed0101b0-2a71-11da-ba81-003048416ace start=34",
"037" => "gctl verb=add geom=%dev% type=ed0101b0-2a71-11da-ba81-003048416ace start=34 end=12345678",
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
"038" => "gctl verb=add geom=%dev% type=ed0101b0-2a71-11da-ba81-003048416ace start=162 end=417 entry=129",
"039" => "gctl verb=add geom=%dev% type=ed0101b0-2a71-11da-ba81-003048416ace start=162 end=417 entry:8=5",
"040" => "gctl verb=add geom=%dev% type=83d34ed5-c4ff-11da-b65b-000347c5d7f3 start=34 end=161 entry=5",
"041" => "gctl verb=add geom=%dev% type=83d34ed5-c4ff-11da-b65b-000347c5d7f3 start=34 end=546",
"042" => "gctl verb=add geom=%dev% type=83d34ed5-c4ff-11da-b65b-000347c5d7f3 start=162 end=417",
"043" => "gctl verb=add geom=%dev% type=83d34ed5-c4ff-11da-b65b-000347c5d7f3 start=100 end=300",
"044" => "gctl verb=add geom=%dev% type=83d34ed5-c4ff-11da-b65b-000347c5d7f3 start=300 end=500",
"045" => "gctl verb=add geom=%dev% type=83d34ed5-c4ff-11da-b65b-000347c5d7f3 start=34 end=161 entry:8",
"046" => "gctl verb=add geom=%dev% type=d2bd4509-c4ff-11da-b4cc-00306e39b62f start=418 end=546 entry:8",
"047" => "conf",
"050" => "gctl verb=remove geom=%dev% entry=5",
"051" => "gctl verb=remove geom=%dev% entry=2",
"052" => "gctl verb=remove geom=%dev% entry=1",
"053" => "gctl verb=remove geom=%dev% entry=1",
"054" => "conf",
"060" => "gctl verb=add geom=%dev% type=516e7cb6-6ecf-11d6-8ff8-00022d09712b start=34 end=546 entry:8=1",
"061" => "mount %dev%p1",
"062" => "gctl verb=remove geom=%dev% entry=1",
"063" => "umount %dev%p1",
"064" => "gctl verb=remove geom=%dev% entry=1",
"065" => "conf",
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"100" => "mdcfg destroy",
"110" => "mdcfg create corrupted",
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
"111" => "gctl verb=add geom=%dev%",
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"120" => "mdcfg destroy",
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
);
Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.
2005-09-19 02:59:09 +00:00
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
my %result = (
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"000" => "FAIL Verb missing",
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
"001" => "FAIL 22 verb 'bogus'",
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"010" => "FAIL 87 provider",
"011" => "FAIL 22 provider 'bogus'",
"020" => "",
"021" => "FAIL 22 entries -1",
"022" => "PASS",
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
"023" => "FAIL 17 geom '%dev%'",
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
"024" => "FAIL 87 entry",
"025" => "b1856477950e5786898c8f01361196cf",
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"030" => "FAIL 87 geom",
"031" => "FAIL 22 geom 'bogus'",
"032" => "FAIL 87 type",
"033" => "FAIL 22 type 'bogus'",
"034" => "FAIL 87 start",
"035" => "FAIL 22 start 1",
"036" => "FAIL 87 end",
"037" => "FAIL 22 end 12345678",
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
"038" => "FAIL 22 entry 129",
"039" => "PASS entry=5",
"040" => "FAIL 17 entry 5",
"041" => "FAIL 28 start/end 34/546",
"042" => "FAIL 28 start/end 162/417",
"043" => "FAIL 28 start/end 100/300",
"044" => "FAIL 28 start/end 300/500",
"045" => "PASS entry=1",
"046" => "PASS entry=2",
"047" => "50783a39eecfc62a29db24381e12b9d8",
"050" => "PASS",
"051" => "PASS",
"052" => "PASS",
"053" => "FAIL 2 entry 1",
"054" => "b1856477950e5786898c8f01361196cf",
"060" => "PASS",
"061" => "PASS",
"062" => "FAIL 16",
"063" => "PASS",
"064" => "PASS",
"065" => "b1856477950e5786898c8f01361196cf",
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"100" => "",
"110" => "",
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
"111" => "FAIL 6 geom '%dev%'",
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
"120" => "",
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
);
my $verbose = "";
if (exists $ENV{'TEST_VERBOSE'}) {
$verbose = "-v";
Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.
2005-09-19 02:59:09 +00:00
}
# Compile the driver...
my $st = system("cc -o $cmd -g $srcdir/test.c -lgeom");
if ($st != 0) {
print "1..0 # SKIP error compiling test.c\n";
exit 0;
}
# Make sure we have permission to use gctl...
if (`$cmd` =~ "^FAIL Permission denied") {
print "1..0 # SKIP not enough permission\n";
unlink $cmd;
exit 0;
}
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
$count = keys (%steps);
Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.
2005-09-19 02:59:09 +00:00
print "1..$count\n";
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
my $nr = 1;
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
my $dev = "n/a";
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
foreach my $key (sort keys %steps) {
my ($action, $args) = split(/ /, $steps{$key}, 2);
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
my $res = $result{$key};
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
$args = "" if (not defined $args);
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
$args =~ s/%dev%/$dev/g;
$res =~ s/%dev%/$dev/g;
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
if ($action =~ "^gctl") {
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
system("$cmd $verbose $args | tee $out 2>&1");
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
$st = `tail -1 $out`;
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
if ($st =~ "^$res") {
print "ok $nr \# gctl($key)\n";
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
} else {
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
print "not ok $nr \# gctl($key) - $st\n";
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
}
unlink $out;
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
} elsif ($action =~ "^mdcfg") {
if ($args =~ "^create") {
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
system("dd if=/dev/zero of=$disk count=1024 2>&1");
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
if ($args =~ "corrupted") {
system("gpt create -p $disk");
}
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
$dev = `mdconfig -a -t vnode -f $disk`;
chomp $dev;
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
} elsif ($args =~ "^destroy") {
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
$dev =~ s/md/-u /g;
system("mdconfig -d $dev");
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
unlink $disk;
Instead of saving the unit number of the md(4) device name, save the whole name. This does not unnecessarily close the door that in some future we want to test on something other than md(4) devices. Also add a "conf" action so that we can check whether a gctl actually did the right thing or not. It's one thing to check that the result strings are as expected, but it doesn't tell us if the end result is correct. This needs a bit more fleshing out, but for now a visual (i.e. manual) check suffices.
2005-11-12 20:17:08 +00:00
$dev = "n/a";
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
}
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
print "ok $nr \# mdcfg($key)\n";
MFp4: o Add mount and umount actions so that partitions can be in use. o Extend the testing of the add verb to include overlapping partitions. o Add tests for the remove verb. this includes tests to remove a partition when in use (i.e. is mounted). o Add a MD5 checksum to the output of the conf action so that it can be tested. Make sure the MD5 doesn't vary based on certain dynamic behaviour that is irrelevant to the output. o Add MD5 checksums to the expected result of conf actions.
2006-04-10 04:13:44 +00:00
} elsif ($action =~ "^conf") {
system("sysctl -b kern.geom.conftxt | grep -a $dev | sed -e s:$disk:DISK:g -e s:$dev:DEV:g | sort | md5 -p | tee $out 2>&1");
$st = `tail -1 $out`;
if ($st =~ "^$res") {
print "ok $nr \# conf($key)\n";
} else {
print "not ok $nr \# conf($key) - $st\n";
}
unlink $out;
} elsif ($action =~ "^mount") {
system("mkdir $mntpt-$args");
system("newfs $args");
system("mount -t ufs /dev/$args $mntpt-$args");
print "ok $nr \# mount($key)\n";
} elsif ($action =~ "^umount") {
system("umount $mntpt-$args");
system("rmdir $mntpt-$args");
print "ok $nr \# umount($key)\n";
o Extend the suite to run more than just the driver. We need to run mdconfig(8), because we need a disk to work on. o Extend the number of tests now that we have a disk. o Simplify the driver. All parameters are ASCII strings now.
2005-09-19 06:51:57 +00:00
}
Rough implementation of the create and add verbs. The verbs cause in-memory changes only and as such are only useful for prototyping and regression testing purposes.
2005-10-09 17:10:35 +00:00
$nr += 1;
Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.
2005-09-19 02:59:09 +00:00
}
unlink $cmd;
exit 0;
Reference in New Issue Copy Permalink