Running an editor in a test with "prove" command

[nysus]

Given this test in test.t:

#/usr/bin/env perl
use Test::More;
use strict;
use warnings;
use Proc::InvokeEditor;

my $edited_text = Proc::InvokeEditor->edit('edit me');
is $edited_text, "edit you\n", 'can edit text';
done_testing();

The Proc::InvokeEditor spawns a new editor instance. When this test is run with prove test.t, you get:

test.t .. Vim: Warning: Output is not to a terminal

The test runs fine with perl test.t. What's the best fix for this?

[haukex]

Tests that require an interactive TTY don't mix well with non-interactive test environments; consider for example what would happen if this test were to be run on CPAN Testers. An alternative to the below is to use something like prompt from ExtUtils::MakeMaker, which can be forced to use defaults if run non-interactively.

use warnings;
use strict;
use Test::More;
use Proc::InvokeEditor;
use IO::Interactive qw/is_interactive/;

SKIP: {
    skip "running non-interactively", 1 unless is_interactive;
    my $edited_text = Proc::InvokeEditor->edit('edit me');
    is $edited_text, "edit you\n", 'can edit text';
}

done_testing;

[nysus]

Nice. I was scratching my head wondering if there was a way I could determine if I was running the script as a test or not. IO::Interactive is exactly what I needed. Thanks!

[ikegami]

I think -t STDOUT would also do it.

[Anonymous Monk]

https://metacpan.org/pod/CPANPLUS::Config#allow_build_interactivity

Automated smoke testers should set $ENV{AUTOMATED_TESTING} to a true value. This allows authors to skip certain tests (or include certain tests) when the results are not being monitored by a human being.

https://metacpan.org/pod/ExtUtils::MakeMaker#PERL_MM_USE_DEFAULT