Nathan Nutter

Recent Actions

• Commented on Test::More - New Maintainer, Also stop version checking!
  I was concerned only with the specific line I quoted as it seems to be putting blame on the wrong place. However, with the clarifications you have made it seems like the sentiment of it was more along the lines...
• Commented on Test::More - New Maintainer, Also stop version checking!
  Altering a programs behavior based on Test::More version is not appropriate. It seems much worse to release two different things named Test::More 1.5. It's counter to the whole purpose of versioning. I would even say it's completely appropriate to alter...
• Commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls
  Regarding the pipe to tee you can, at least in Bash, enable the pipefail option to resolve the issue with exit code. Here's an example: $ set +o pipefail && $(exit 200 | tee); echo $? 0 $ set -o...

Comment Threads

• Bruno P. Kinoshita commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls

  Hi there David!

  I have just created an issue for that: https://sourceforge.net/tracker/?func=detail&aid=3489038&group_id=351793&atid=1470127

  I will work on this in the next days. Feel free to add any comments, suggestions.

  When I wrote tap4j, I had a short deadline to deliver it for an internal project too. So probably there is room for improvements in both, tap4j and TAP Plug-in (in the latter, mainly due to the fact that I code Java everyday, but still have a loooot…

• Bruno P. Kinoshita commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls

  Thanks for reporting the issue! I'm back working on my Open Source projects, probably until July/August.

  I'm currently working on a YAMLish issue in tap4j (this was reported in GitHub), and after this one I'll focus in integration tests for Perl x tap4j.

  Feel free to drop a message and check the status if I take too long to update the issue.

  All the best,
  Bruno

• Mark Stosberg commented on Perl testing with Jenkins/Hudson: avoiding some pitfalls

  I also tried the TAP plugin for Jenkins/Hudson and couldn't get it to work.

  We are doing parallel testing with -j4, so the hack of manually running each script with "perl" won't work. and I couldn't get --archive to produce any results for me. (Perhaps it's not compatible with parallel testing). We also use "done_testing()", so perhaps that it is part of the issue as well.

  However, emitting JUnit works fine, I was just hoping to get TAP integration to work!

• exodist7 commented on Test::More - New Maintainer, Also stop version checking!

  Nathan,

  I agree that in 99% of cases it is fine to alter behavior based on version.

  There was never an official Test::More 1.5 release. There were experimental alphas only. Some people helped Schwern by downloading these alphas, or using them on their cpan-testers machines.

  Some people picked this up and started writing code that did things differently for versions greater than or equal to 1.5. This version specific code depends on the internals changed for 1.5, internals that have been put on hold, possibly forever. So 1.5 the experiment is done, and for now at least…

• Aristotle commented on Test::More - New Maintainer, Also stop version checking!

  Can’t wait to read what the new roadmap is.