Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Test-Run 0.0115 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Test-Run 0.0115 (Default branch)
# 1  
Old 04-05-2008
Test-Run 0.0115 (Default branch)
ImageTest-Run is an improved test harness for scriptsthat emit TAP (Test Anything Protocol). It wasforked from Test::Harness, and it usesTAP::Parser. It is used to analyze the output ofthe scripts and present it to the user in asummarized form. Test-Run features separation ofthe test-running backend and the command linefrontend, a "runprove" utility for running testsfrom the command line, a plugin-system, and colorsfor the summary line.License: MIT/X Consortium LicenseChanges:
The code was fully converted to a BSD-style-licence, and in the process heavily refactored. The Test::Run::Plugin::TrimDisplayedFilenames plugin has been added to remove components of extremely long paths. This release has full documentation coverage. Some API compatibility was broken.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Run sequential test files

I have c program that I run like this: ./a.out t1 And my test files look like this all the way up to 100: t1 t2 t3 Is there a way to run this more efficiently so I don't have to hit up and change the number every time? (4 Replies)
Discussion started by: cokedude
4 Replies

2. Programming

Run ruby test and include require

I want to run a test for the gem mini_magick: https://github.com/minimagick/minimagick I got the directory lib, inside of which i got: - mini_magick.rb - mini_gmagick.rb and inside of the test folder is the test i need to run: - image_test.rb and a helper file called: - test_helper.rb ... (1 Reply)
Discussion started by: tornow
1 Replies

3. HP-UX

test program(dlopen) fails on hp but run well on solaris

Hi, I have a c test program which test dlopen call. This program run well on solaris but fails on hp-ux. The program load jvm library successfully on solaris. On hp-ux it displays error I compile this program as $cc -o testjvm testjvm.c What am I missing? I have tried... (2 Replies)
Discussion started by: shriashishpatil
2 Replies
Login or Register to Ask a Question

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)