Something I whipped up just this morning. It should work with Test::Harness, it may be missing some of the Test::More methods, let me know if I've mised the mark or something else needs to be added. 
#!/bin/bash
# This is a shell library for interfacing with Perl's Test::Harness fr
+amework
# Copyright 2004. Michael Grubb

SHOULD_PRINT_PLAN=0
TEST_PLAN=0
TEST_COUNTER=0
MATCH_PROG=/bin/egrep
MATCH_ARGS="-q"

plan()
{
    if [ "${1}" == "no_plan" ] ; then
        SHOULD_PRINT_PLAN=1
        TEST_PLAN=0
    else
        TEST_PLAN="${1}"
        SHOULD_PRINT_PLAN=1 _printPlan
        SHOULD_PRINT_PLAN=0
    fi

}

endtests()
{
    _printPlan
}

ok()
{
    _updatePlan
    if [ $1 != 0 ]; then
        echo -n "not "
    fi
    echo "ok ${TEST_COUNTER} ${2} # \$1 is '$1'"
}

is()
{
    _updatePlan
    if [ $1 != ${2} ] ; then
        echo -n "not "
    fi
    echo "ok ${TEST_COUNTER} ${3} # expecting '$1' got '$2'"
}

match()
{
    _updatePlan
    echo "$2" | ${MATCH_PROG} ${MATCH_ARGS} ${1}
    rv=$?
    if [ $rv -ne 0 ] ; then
        echo -n "not "
    fi
    echo -n "ok ${TEST_COUNTER} ${3} "
    if [ $rv -ne 0 ] ; then
        echo "# '$2' did not match '$1'"
    else
        echo
    fi
}

diag()
{
    echo "# $1" 1>&2
}

_updatePlan()
{
    TEST_COUNTER=$((${TEST_COUNTER}+1))
    if [ ${SHOULD_PRINT_PLAN} ] ; then TEST_PLAN=${TEST_COUNTER} ; fi
}

_printPlan()
{
    if [ ${SHOULD_PRINT_PLAN} -eq 1 ] ; then
        echo "1..${TEST_PLAN}"
    fi
}

[download]

And here is a script that shows it's usage: 

#!/bin/bash

. ./Test.sh

plan "no_plan"

diag "# TEST_PLAN=$TEST_PLAN"
ok 0 "Test 1"
ok 0 "Test 2"
ok 2 "Test 3"
is "this" "this"
is "this" "that"
is 1 0
is 0 1
is 1 1
match "^ab[cd]efg$" "abcefg"
match "^ab[cd]efg$" "abdefg"
match "^ab[cd]efg$" "abcdefg"
match "^ab[cd]efg$" "abhefg"
endtests    # only needed when "no_plan" is used

[download]
Hope this helps. Oh, and by default the "match" function uses egrep -q but you can override that if you set MATCH_PROG and MATCH_ARGS after you source Test.sh. Let me know if this is useful. Also note that getting Test::Harness to run this is an excercise left to the reader.

In reply to Re^2: using Test::* modules for generic testing of non perl stuff? by linux454
in thread using Test::* modules for generic testing of non perl stuff? by jfroebe

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.