Sponsored Content
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Amazon CloudFront / S3 Small Object Test Results Post 302325556 by Neo on Monday 15th of June 2009 01:19:42 PM
Old 06-15-2009
FYI: I have also posted these results to the AWS CF forum.

-----Post Update-----

Earlier, I forgot to thank Stefan for his vB forum BBCODE that makes posting a nice table possible, BB Code [table]. Thanks Stefan!!
 

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Printer Error(the Object Instance Test Does Not Exist)

Hello, i need some help about how to set up a high velocity impact printer in UNIX SCO 5.05, this printer is attached with a parallel port in a PC(host), the host use tunemul to access unix.(this reference is just to ask you if this is a local or remote connection, just to be sure), so, i... (2 Replies)
Discussion started by: jav_v
2 Replies

2. Virtualization and Cloud Computing

CEP as a Service (CEPaaS) with MapReduce on Amazon EC2 and Amazon S3

Tim Bass 11-25-2008 01:02 PM Just as I was starting to worry that complex event processing community has been captured by RDBMS pirates off the coast of Somalia, I rediscovered a new core blackboard architecture component, Hadoop. Hadoop is a framework for building applications on large... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. Shell Programming and Scripting

PERL - traverse sub directories and get test case results

Hello, I need help in creating a PERL script for parsing test result files to get the results (pass or fail). Each test case execution generates a directory with few files among which we are interested in .result file. Lets say Testing is home directory. If i executed 2 test cases. It will... (4 Replies)
Discussion started by: ravi.videla
4 Replies
Test::Harness::Straps(3pm)				 Perl Programmers Reference Guide				Test::Harness::Straps(3pm)

NAME
Test::Harness::Straps - detailed analysis of test results SYNOPSIS
use Test::Harness::Straps; my $strap = Test::Harness::Straps->new; # Various ways to interpret a test my %results = $strap->analyze($name, @test_output); my %results = $strap->analyze_fh($name, $test_filehandle); my %results = $strap->analyze_file($test_file); # UNIMPLEMENTED my %total = $strap->total_results; # Altering the behavior of the strap UNIMPLEMENTED my $verbose_output = $strap->dump_verbose(); $strap->dump_verbose_fh($output_filehandle); DESCRIPTION
THIS IS ALPHA SOFTWARE in that the interface is subject to change in incompatible ways. It is otherwise stable. Test::Harness is limited to printing out its results. This makes analysis of the test results difficult for anything but a human. To make it easier for programs to work with test results, we provide Test::Harness::Straps. Instead of printing the results, straps provide them as raw data. You can also configure how the tests are to be run. The interface is currently incomplete. Please contact the author if you'd like a feature added or something change or just have comments. Construction new my $strap = Test::Harness::Straps->new; Initialize a new strap. Analysis analyze my %results = $strap->analyze($name, @test_output); Analyzes the output of a single test, assigning it the given $name for use in the total report. Returns the %results of the test. See Results. @test_output should be the raw output from the test, including newlines. analyze_fh my %results = $strap->analyze_fh($name, $test_filehandle); Like "analyze", but it reads from the given filehandle. analyze_file my %results = $strap->analyze_file($test_file); Like "analyze", but it runs the given $test_file and parses it's results. It will also use that name for the total report. Results The %results returned from analyze() contain the following information: 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) 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. EXAMPLES
See examples/mini_harness.plx for an example of use. AUTHOR
Michael G Schwern <schwern@pobox.com> SEE ALSO
Test::Harness perl v5.8.0 2002-06-01 Test::Harness::Straps(3pm)
All times are GMT -4. The time now is 03:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy