Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ... that they feel the need to stick it up as a separate card rather than doing continual refactoring. I'd want to work with them on that :-)

    Adrian

    • What if you suddenly wake up an realize you have a large volume of duplicated test code (which may be the case, I have no idea)? Wouldn't you want to schedule time to make a serious difference?

      I think the presence of a card is a very un-sad thing for various reasons (they identified the problem, took action, got on scheduled time for it).

      • Yes. You're right. I was obviously feeling especially grumpy when I wrote that. The presence of the card is certainly a good sign that folk are paying attention to the code and know improvements need to be made. Yay :-)

        That said - I've seen too many folk who get into this nasty cycle of hack-code-until-mud... oh bugger.... better write some refactoring cards.... spend time persuading product owner than they really, _really_ need to do the refactoring cards.... refactor.... hack-code-until-mud... repeat...

        Re

  • It took my a long time to get it in my head that I should be writing my tests just like I wrie the code I'm testing: Modular and Reusable.

    It really hit home with me when I was writing tests for classes I knew other people would inherit or subclass. In that case, why not make it easier for the new distant coder to also reuse as much of your test suite as possible to also test their new code.

    That's sort of easy with Test::Class. Sometimes, it takes a little more effort in things like NUnit in .NET, where you'

  • In a former job I saw a system where every object was given a method to instantiate itself from a YAML data file. And by "instantiate itself" I include "Go and insert itself in the test database you are using." (You want your stored procedures and views properly tested, right?) And (this is important important), every field not specified in the YAML was automatically given a sensible default.

    Then in the test files they set up a nested YAML data structure that was automatically turned into a slew of relat