i am using solaris 5.10. i can create two different files "test" and ".test" in the same directory. now suppose i want to change the attribute of the hidden file .test to visible is it possible???
since "." is just an attribute to mark a file hidden why is unix allows creation of "file" and... (14 Replies)
Hi! I'm using
echo $string | grep "" -c
to test in a script if a string is a number and it seems to work. But how can i find, for example, if a string is a four figures number ?
Thanks to all! (2 Replies)
Hi,
I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
I am testing shc to see if it would help with my need.
Im at a point where Im trying to compile and test the "test.ksh" file that comes in the tar ball :
shc-3.8.9> shc -v -r -f test.ksh
shc shll=ksh
shc =-c
shc =exec '%s' "$@"
shc =
shc opts=
shc: cc test.ksh.x.c -o test.ksh.x... (7 Replies)
Discussion started by: popeye
7 Replies
LEARN ABOUT OSX
test::harness::results
Test::Harness::Results(3pm) Perl Programmers Reference Guide Test::Harness::Results(3pm)NAME
Test::Harness::Results - object for tracking results from a single test file
SYNOPSIS
One Test::Harness::Results object represents the results from one test file getting analyzed.
CONSTRUCTION
new()
my $results = new Test::Harness::Results;
Create a test point object. Typically, however, you'll not create one yourself, but access a Results object returned to you by
Test::Harness::Results.
ACCESSORS
The following data points are defined:
passing true if the whole test is considered a pass
(or skipped), false if its a failure
exit the exit code of the test run, if from a file
wait the wait code of the test run, if from a file
max total tests which should have been run
seen total tests actually seen
skip_all if the whole test was skipped, this will
contain the reason.
ok number of tests which passed
(including todo and skips)
todo number of todo tests seen
bonus number of todo tests which
unexpectedly passed
skip number of tests skipped
So a successful test should have max == seen == ok.
There is one final item, the details.
details an array ref reporting the result of
each test looks like this:
$results{details}[$test_num - 1] =
{ ok => is the test considered ok?
actual_ok => did it literally say 'ok'?
name => name of the test (if any)
diagnostics => test diagnostics (if any)
type => 'skip' or 'todo' (if any)
reason => reason for the above (if any)
};
Element 0 of the details is test #1. I tried it with element 1 being #1 and 0 being empty, this is less awkward.
Each of the following fields has a getter and setter method.
o wait
o exit
perl v5.10.0 2007-12-18 Test::Harness::Results(3pm)