shunit with xml output

[sunitha kumar]

Is this integrated in 2-2.1.6 ?

[Kate Ward]

I never found enough interest for it. How strong are you interested in it?

- kate

On Mon, Dec 17, 2012 at 10:02 PM, sunitha kumar <sunitha...@gmail.com> wrote:

Is this integrated in 2-2.1.6 ?

--
You received this message because you are subscribed to the Google Groups "shunit2-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/shunit2-users/-/T7yDtYte6vYJ.
To post to this group, send email to shunit...@googlegroups.com.
To unsubscribe from this group, send email to shunit2-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/shunit2-users?hl=en.

--
Kate Ward <kate...@forestent.com>

[thomas....@teamaol.com]

Hi,

the tool is very nice but there are a few small things I would improve ...

 a) I cannot say "shunit2 test_*.sh". Instead I have to do following:
      for TEST in `ls test_*.sh`; do shunit2 $TEST; done

 b) Providing fix signature with information passed and failed like:
      test_all_ip_addresses [passed]
      or
      test_all_ip_addresses [failed]

     Preferrable with colors ... maybe ...

    # update stats
    if [ ${__shunit_testSuccess} -eq ${SHUNIT_TRUE} ]; then
      __shunit_testsPassed=`expr ${__shunit_testsPassed} + 1`
      echo "${_shunit_test_} \033[1;98m[passed]\033[0m"
    else
      __shunit_testsFailed=`expr ${__shunit_testsFailed} + 1`
      echo "${_shunit_test_} \033[1;31m[failed]\033[0m"
    fi

    This would also solve the problem that everybody can decide on his/her own to convert this into that XML he/she likes.
    I would use this on Jenkins.

 c) You have a nice documentation (homepage) but honestly I like it that a tool tells you all you need.
     So I would print out the version of the tool on each "run" and would provide "--version" and "--help"

That's it, basically.

Regards,
Thomas