No - per prove-run, my approach would use the same shell for all runs. Maybe you can/want to use a shim in between your .t file and prove, that is something like:

#!/bin/bash
TESTSCRIPT=$1
for SHELL in ./test-shells/* ; do
    $SHELL $TESTSCRIPT
    if $? ; then
        exit $?
    fi
done

[download]

If you set this script as the interpreter of your test files, that should run each test with all shells (but still, single threaded). That way, you could at least achieve parallelism across your test files.

I'm sure there is a bash-way of stopping the interpreter script when any subprocess fails. Maybe it's set -e or something, but I'm sure you know that far better than I do.

In reply to Re^5: prove: parallel multiple shells by Corion
in thread prove: parallel multiple shells by almr

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.