Term::Shell lets you write simple command-line shells. All the boring
details like command-line parsing, terminal handling, and tab completion
are handled for you.
This module provides some drop-in replacements for the string comparison
functions of Test::More, but which are more suitable when you test against
long strings. If you've ever had to search for text in a multi-line string
like an HTML document, or find specific items in binary data,
this is the module for you.
Term::Size::Any is a unified interface to retrieve terminal size. It loads one
module of a list of known alternatives, each implementing some way to get the
desired terminal information. This loaded module will actually do the job on
behalf of Term::Size::Any.
Term::Size::Perl is yet another implementation of Term::Size in pure Perl, with
the exception of a C probe run on build time.
Term::UI is a transparent way of eliminating the overhead of having to
format a question and then validate the reply, informing the user if the
answer was not proper and re-issuing the question.
Simply give it the question you want to ask, optionally with choices the
user can pick from and a default and Term::UI will DWYM.
For asking a yes or no question, there's even a shortcut.
This is a subclass of Term::VT102 that will grow the virtual screen to
accomodate arbitrary width and height of text.
The behavior is more similar to the buffer of a scrolling terminal
emulator than to a real terminal, making it useful for output displays
in scrolling media.
Term::Visual is a "visual" terminal interface for curses applications. It
provides the split-screen interface you may have seen in console based IRC
and MUD clients.
Term::Visual uses the POE networking and multitasking framework to support
concurrent input from network sockets and the console, multiple timers, and
more.
Provides basic test runner via use_test_packages by base package or a list
of test packages. Allows you to choose your test paths.
Use Test::Able without a bunch of boilerplate.
An xUnit style testing framework inspired by Test::Class and built using Moose.
It can do all the important things Test::Class can do and more.
The prime advantages of using this module instead of Test::Class are
flexibility and power. Namely, Moose.
This module was created for a few of reasons:
To address perceived limitations in, and downfalls of, Test::Class.
To leverage existing Moose expertise for testing.
To bring Moose to the Perl testing game.
Aggregate perl test for better performance