David, >> I guess I'm not sure what to do here. What do other folks advise? > > Contact the individual testers, I guess.
I'm not sure what to say though ... "hey, dude, your automated testing is being rude to my tests, so go fix that?" I mean, I wouldn't put it that way, obviously, but i can't help but feel like it would come out sounding that way ... > This seems to vary from one place to another - I'm not sure exactly what > the differences are that cause it, but in some places some of my > long-running tests *do* output some kind of count of how far they've > got, and in some they don't. It's probably something to do with output > buffering. Hunh. Well, I suppose I could specifically put something (like a diag call) in there to spit out something every now and again, only if $AUTOMATED_TESTING. Maybe that would keep people's scripts from assuming the thing is hung? No, wait: a diag gets eaten by Test::Harness too, doesn't it? What could I do to get the output through Test::Harness without making it think there's a failure? -- Buddy
