Agile, test-driven development
It All Started with a Test
Test-driven development with a full-coverage regression test suite as a useful side effect promises code with fewer errors. Mike "Perlmeister" Schilli enters the same path of agility and encounters a really useful new CPAN module.
A few weeks ago, my employer sent me to a course about test-driven development (TDD) and agile methods, and to implement my newly gained knowledge practically, I am dedicating today's Perl snapshot to this principle.
Fast and flexible developers typically set off immediately without paying attention to details. They always write a test first before they get down to implementing a function. The test suite thus grows automatically with tests relevant to system functions. They clean up dirty code by refactoring later; this is possible without any risk thanks to the safety net provided by the test suite.
Nothing but Errors – and Rightly So
The tests developed before writing a function will fail, of course, because the desired feature either does not exist or is only partially or incorrectly implemented at first. When the code arrives later on, the test suite passes and turns to green; development environments such as Eclipse actually visualize it this way.
For example, to write a User.pm
class for a login system that later supports methods such as login()
, TDD disciples first create a test case. It checks whether the desired class can actually be instantiated. Listing 1 shows the test file for simple test cases, Basic.pm
. It is located in the directory t
and uses the brand new CPAN Test::Class::Moose module from CPAN. The latter runs all methods with the test_
prefix and the test utility routines they invoke.
Listing 1
Basic.pm
Listing 1 [1] defines test_constructor()
and runs the command
can_ok 'User', 'new';
from the Test::More module in it. Thus, test_constructor()
verifies whether the User
class is capable of calling its constructor new
.
Listing 2 shows a script for running the test suite. At first, it draws in the Load
module, which loads all Perl modules with the .pm
suffix that exist in the specified subdirectories (.
and t
). The runtests()
method then executes all test_*
routines found in these modules. In this phase of the project, the User
class does not yet exist, and the test case in test_constructor()
thus fails (Figure 1).
Listing 2
runtests
A Sense of Achievement
The test-driven developer naturally expected this outcome and now does everything possible to add code until the test suite completes without error. Because the class does not exist, the developer creates a new User.pm
file and then adds the following content:
package User; use Moose; 1;
Old hands like your very own Perlmeister might rub their eyes in disbelief at this, because the User
package does not define a new()
constructor that welds an object hash $self
onto a package using bless()
. The Moose [2] CPAN module does all of this behind the scenes, so every packet that Moose looks at automatically owns a new()
constructor.
A new run of the test suite using ./runtests
returns these promising results:
<[...]> ok 1 - TestsFor::User
The suite therefore finds the new .pm
file, the class it contains, and the new()
constructor.
Once More into the Agile Fray
Green light – the signal for TDD developers to add a new feature. The User
object needs methods to set and query the user's email address. A developer working conventionally would probably immediately start typing the seemingly simple code. Not so TDD followers; they first write a test that again fails.
Listing 3 defines the test_accessors()
method, which the test module later also finds and calls due to the prefix. It creates a new object of the User
type and passes the parameter pair email => 'a@b.com'
to the constructor. One line later, the erstwhile undefined accessor retrieves the email string set by the constructor, and the is
function from the Test::More module compares the value with the one set previously. If the contents match, is
writes the ok
string to the TAP output of the test suite. The suite will recognize this as a successfully executed test case.
Listing 3
Accessors.pm
This test is followed by a test of the setter, which uses the email()
method to set a new value for the user's email address and then runs the accessor (also email()
but without an argument) to retrieve the stored value again and compare it with the original. But the User.pm
class still does not have the necessary code; the new test therefore fails immediately.
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
-
Latest Cinnamon Desktop Releases with a Bold New Look
Just in time for the holidays, the developer of the Cinnamon desktop has shipped a new release to help spice up your eggnog with new features and a new look.
-
Armbian 24.11 Released with Expanded Hardware Support
If you've been waiting for Armbian to support OrangePi 5 Max and Radxa ROCK 5B+, the wait is over.
-
SUSE Renames Several Products for Better Name Recognition
SUSE has been a very powerful player in the European market, but it knows it must branch out to gain serious traction. Will a name change do the trick?
-
ESET Discovers New Linux Malware
WolfsBane is an all-in-one malware that has hit the Linux operating system and includes a dropper, a launcher, and a backdoor.
-
New Linux Kernel Patch Allows Forcing a CPU Mitigation
Even when CPU mitigations can consume precious CPU cycles, it might not be a bad idea to allow users to enable them, even if your machine isn't vulnerable.
-
Red Hat Enterprise Linux 9.5 Released
Notify your friends, loved ones, and colleagues that the latest version of RHEL is available with plenty of enhancements.
-
Linux Sees Massive Performance Increase from a Single Line of Code
With one line of code, Intel was able to increase the performance of the Linux kernel by 4,000 percent.
-
Fedora KDE Approved as an Official Spin
If you prefer the Plasma desktop environment and the Fedora distribution, you're in luck because there's now an official spin that is listed on the same level as the Fedora Workstation edition.
-
New Steam Client Ups the Ante for Linux
The latest release from Steam has some pretty cool tricks up its sleeve.
-
Gnome OS Transitioning Toward a General-Purpose Distro
If you're looking for the perfectly vanilla take on the Gnome desktop, Gnome OS might be for you.