comment on

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks