Printer function test after distribution update
Print as Print Can
Cautious administrators will want to make sure a Linux installation is still working as intended after an update. A simple test suite offers that assurance.
If you are an administrator and regularly thrill your flock of users with Linux distribution updates, you will want to avoid annoying complaints and problems by actually testing the functionality up front. As an example of a potential approach, this article looks at how to check a shared printer.
When you type "Printers" into the Ubuntu search field, you are taken to a dialog displaying all the connected printers (Figure 1). You could select a printer manually at this point and talk it into printing a test page. But, how can you use an automated test to handle this task – and other tests for similar situations?
First Attempt
The Linux Desktop Testing Project (LDTP) [1] is dedicated to testing GUIs on all kinds of platforms, including Windows. LDTP relies on the accessibility features of window managers like Gnome or KDE and even lets you control them remotely. The project, however, does not look very healthy, and the documentation is gappy. Even following a request I sent to the developers, I was unable to talk the GUI into responding appropriately, because either the LDTP daemon crashed or did something unexpected compared with what the sparse documentation advertised. Definitely a good idea, but maintenance needs to be improved if the project is to be of any practical use.
At My Command
The command-line tools lpstat
, lpr
, and lpq
helped me out of this hole; they list all the configured printers, print a document, and let you visualize the print queue. When bundled into a Perl script, these commands find the standard printer, tell it to print a test document, and check whether the job first appears in the queue and then disappears again when done. If the output from the typical Perl TAP (Test Anything Protocol) is then ok
rather than not ok
in all disciplines, the printer has passed the test and the newly installed distribution is functional – at least, in terms of the printing environment. Figure 2 shows the output from a successful printer test.
The test script in Listing 1 [2] uses Perl's backquote mechanism to call the command-line tools and saves the output in variables for checking later on via regular expressions. Perl's Test::More test module exports the ok
and is
functions, which check return values and compare actual and expected results. ok
and is
also sound the alarm if an unexpected event occurs.
Listing 1
lptest-default
01 #!/usr/local/bin/perl -w 02 use strict; 03 use Test::More; 04 use Getopt::Long; 05 use Path::Tiny; 06 07 my $realprint = 1; 08 GetOptions( "realprint!" => \$realprint ); 09 10 my $lpstat = "lpstat"; 11 my $lpr = "lpr"; 12 my $lpq = "lpq"; 13 14 my( $default_printer ) = 15 ( `$lpstat -d` =~ /: (.*)/ ); 16 17 if( !defined $default_printer ) { 18 die "Cannot find default printer"; 19 } 20 21 ok 1, 22 "found default printer $default_printer"; 23 24 SKIP: { 25 if( !$realprint ) { 26 skip "printing disabled", 1; 27 } 28 29 ok !lpq_busy(), "lpq empty"; 30 31 my $temp = Path::Tiny->tempfile; 32 $temp->spew( "This is a test." ); 33 34 my $rc = system $lpr, "-P", 35 $default_printer, $temp->absolute; 36 is $rc, 0, "printing with $lpr"; 37 38 ok lpq_busy(), "lpq busy"; 39 40 while( lpq_busy() ) { 41 sleep 1; 42 } 43 44 ok !lpq_busy(), "lpq empty"; 45 } 46 47 done_testing; 48 49 sub lpq_busy { 50 my $queue = `$lpq`; 51 52 return $queue =~ /active/; 53 }
The ok()
function checks whether the first parameter passed in contains a true value, and is()
compares the value it sees (first parameter) with the expected value (second parameter).
Run at the command line, lpstat
in Figure 3 tells me that a multifunctional printer by the name of MFC7420 is configured on my Ubuntu installation, as well as an array of label printers by Dymo, which I introduced three months back in this Perl column [3]. Because the distribution test only tests the function of the default printer, the test script in Listing 1 calls lpstat -d
, grabs the output showing the default printer, and checks whether the output contains at least one line with a colon character.
Default Printer
If lpstat
finds a default printer, this is a good sign that the newly installed distribution is working properly. For further tests, the script actually has to send a print job. If you don't want to waste paper on printing, you will want to call lptest-default
with the --norealprint
option, which tells the test script to skip the section marked SKIP
at line 24. In this case, the output shows the restricted test coverage:
$ ./lptest-default --norealprint ok 1 - found default printer MFC7420 ok 2 # skip printing disabled 1..2
The GetOptions()
function called in line 8 defines the --realprint
command-line parameter for this purpose; line 7 sets it to 1
by default, that is, it prints for real unless you say otherwise.
The exclamation mark at the end of the realprint!
option tells GetOptions()
that the negation with --norealprint
at the command line sets the $realprint
variable to a false value in the script, thus disabling actual printing.
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
The Gnome Foundation Struggling to Stay Afloat
The foundation behind the Gnome desktop environment is having to go through some serious belt-tightening due to continued financial problems.
-
Thousands of Linux Servers Infected with Stealth Malware Since 2021
Perfctl is capable of remaining undetected, which makes it dangerous and hard to mitigate.
-
Halcyon Creates Anti-Ransomware Protection for Linux
As more Linux systems are targeted by ransomware, Halcyon is stepping up its protection.
-
Valve and Arch Linux Announce Collaboration
Valve and Arch have come together for two projects that will have a serious impact on the Linux distribution.
-
Hacker Successfully Runs Linux on a CPU from the Early ‘70s
From the office of "Look what I can do," Dmitry Grinberg was able to get Linux running on a processor that was created in 1971.
-
OSI and LPI Form Strategic Alliance
With a goal of strengthening Linux and open source communities, this new alliance aims to nurture the growth of more highly skilled professionals.
-
Fedora 41 Beta Available with Some Interesting Additions
If you're a Fedora fan, you'll be excited to hear the beta version of the latest release is now available for testing and includes plenty of updates.
-
AlmaLinux Unveils New Hardware Certification Process
The AlmaLinux Hardware Certification Program run by the Certification Special Interest Group (SIG) aims to ensure seamless compatibility between AlmaLinux and a wide range of hardware configurations.
-
Wind River Introduces eLxr Pro Linux Solution
eLxr Pro offers an end-to-end Linux solution backed by expert commercial support.
-
Juno Tab 3 Launches with Ubuntu 24.04
Anyone looking for a full-blown Linux tablet need look no further. Juno has released the Tab 3.