[Console] testing with askConfirmation/ask

[sstok]

The documentation is missing an example how to test a command that uses askConfirmation() or ask().

/** @var \Symfony\Component\Console\Helper\DialogHelper $dialog */
$dialog = $this->getHelperSet()->get('dialog');

if (!$dialog->askConfirmation(..)) {
  // Do something.
}

As this is a really useful feature and not to hard document (I guess), I suggest adding this for Symfony Docs Hack Day.

[sstok]

OK, this is a little troubling. it seems you need to send the response BEFORE the output can be read/asserted.

[wouterj]

Testing it can be done by using DialogHelper::setInputStream (a \n in the stream means an enter in the console):

public function testInteractiveCommand()
{
    $application = new Application();
    $application->add(new GreetCommand());

    $command = $application->find('demo:greet');
    $tester = new CommandTester($command);

    $dialog = new DialogHelper();
    $dialog->setInputStream("Wouter\n\n");
    /**
     * This is equivalent for doing:
           'Your Name': Wouter

           Confirm?
           yes
     */

    $command->setHelperSet(array($dialog));

    $tester->execute(array(...));
}

This should be documented in a new section in the components/console/helpers/dialoghelper article.

[sstok]

This can be done a little simpler.

$dialog = $command->getHelperSet()->get('dialog');

And setInputStream() expects a stream.

$dialog->setInputStream($this->getInputStream("y\nyes\n"));

With.

protected function getInputStream($input)
    {
        $stream = fopen('php://memory', 'r+', false);
        fputs($stream, $input);
        rewind($stream);

        return $stream;
    }

But setting the response before the actual output can read is a little strange.
Not sure if this also works with select().