view release on metacpan or  search on metacpan

t/App-Fetchware-new  view on Meta::CPAN

#!/usr/bin/env perl
use warnings;
use strict;

# Tests the cmd_new() subroutine that uses Term::UI to ask the user questions.
# This "test script" is called by t/bin-fetchware-new.t's using Test::Expect,
# if its optionally installed. And Test::Expect answer's the questsions that
# this script asks thereby testing add_mirrors() Q&A interface.

# Needed so perl can find App::Fetchware.
use lib 'lib';

use Test::More;
use Test::Builder;
use Term::ReadLine;

use lib 'bin';
require 'fetchware';
fetchware->import(':TESTING');

my $term = Term::ReadLine->new('testing fetchware new');

my $fetchwarefile_path_or_package_path = cmd_new();

ok (-e $fetchwarefile_path_or_package_path,
    'checked cmd_new() Fetchwarefile creation success.');

ok (unlink $fetchwarefile_path_or_package_path,
    'checked cmd_new() delete test Fetchwarefile.');


# Spit out # of tests run.
done_testing();

# Print a bogus "prompt" to keep Expect from freaking out, because it presumes
# the prompt works like it does in a shell, but fetchware new is not a shell.
print "Bogus shell: \n";

# Because we're in a child process not the same one that is running the main
# test suite, if any tests fail this failure will not be reported back to our
# caller. So, we use Test::Builder to check if our tests have passed, and if
# they have we do nothing and return succes, but if not we throw an exception.
my $test = Test::Builder->new();
unless ($test->is_passing()) {
    diag explain \[$test->details()];
    die <<EOD;
add_mirrors test file for testing add_mirrors() using Test::Expect has failed!
The details() method of this process's Test::Builder object should have been
printed above to help you figure out what went wrong.
EOD
}