Linux Test Project 20081231 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Linux Test Project 20081231 (Default branch)
# 1  
Old 12-31-2008
Linux Test Project 20081231 (Default branch)

The Linux Test Project is a joint project with SGI, IBM, OSDL, Bull, and Wipro Technologies with a goal to deliver test suites to the open source community that validate the reliability, robustness, and stability of Linux. The project consists of well over 2000 individual testcases and a test driver to automate execution of the tests. License: GNU General Public License (GPL) Changes:
Numerous PIDNS tests were added. CPU Controller Latency tests were added. Video for Linux 2 (V4L2) API device driver tests were added. Options were added for block devices to runltp. ioctl03 and inotify03 tests were added. Autoconf is used for some more tests. Pounder21 updates were made. Ltp network, network stress, adp, autofs, exportfs, ro only fs, isofs, dmmapper, fslvm, fsnolvm, scsi_debug, sysfs, tirpc, and SELinux tests were integrated into runalltests. Fixes were made for numerous other tests. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
Test::NeedsDisplay(3pm) 				User Contributed Perl Documentation				   Test::NeedsDisplay(3pm)

NAME
Test::NeedsDisplay - Ensure that tests needing a display have one SYNOPSIS
In your Makefile.PL... use inc::Module::Install; # ... or whatever else you use # Check for a display use Test::NeedsDisplay; # ... your Makefile.PL content as normal And again in each test script that loads Wx #!/usr/bin/perl use strict; use Test::NeedsDisplay; # Test content as normal... DESCRIPTION
When testing GUI applications, sometimes applications or modules absolutely insist on a display, even just to load a module without actually showing any objects. Regardless, this makes GUI applications pretty much impossible to build and test on headless or automated systems. And it fails to the point of not even running the Makefile.PL script because a dependency needs a display so it can be loaded to find a version. In these situations, what is needed is a fake display. The "Test::NeedsDisplay" module will search around and try to find a way to load some sort of display that can be used for the testing. Strategies for Finding a Display At this time, only a single method is used (and a very simple one). Debian Linux has a script called "xvfb-run" which is a wrapper for the "xvfb", a virtual X server which uses the linux frame buffer. When loaded without a viable display, the module will re-exec the same script using something like (for example) "xvfb-run test.t". As such, it should be loaded as early as possible, before anything has a chance to change script parameters. These params will be resent through to the script again. METHODS
There are no methods. You simply use the module as early as possible, probably right after "use strict;" and make sure to load it with only default params. Specifically, need must always load it before you set the test plan, otherwise the test script will report two plans, and the harness will complain about it and die. # Use it like this ... use Test::NeedsDisplay; # ... not like this ... use Test::NeedsDisplay 'anything'; # ... and not like this. use Test::NeedsDisplay (); And that's all there is to do. The module will take care of the rest. TO DO
- Find alternative ways to launch a display on different platforms SUPPORT
Bugs should be reported via the CPAN bug tracker at <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Test-NeedsDisplay> For other issues, contact the author. AUTHOR
Adam Kennedy <adamk@cpan.org> COPYRIGHT
Copyright 2005 - 2009 Adam Kennedy. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of the license can be found in the LICENSE file included with this module. perl v5.10.0 2009-01-04 Test::NeedsDisplay(3pm)