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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
An excellent essay... (Score:1)
Kirrily "Skud" Robert perl@infotrope.net http://infotrope.net/
Re: (Score:1)
It makes testing a hell of a lot simpler.
But back to Skud's case. Personally, I'm finding I'm using environment variables a hell of a lot more for giant testing sets (in my case, say 27000 tests in 80 scripts).
That way I can factor out problems.
For example, I want to be able to test as much of my app as possible, even without a working database setup.
So
Re:An excellent essay... (Score:1)
*sigh*, it's a hard problem. And I recognise that Schwern's comments do indicate the Right Thing -- and certainly what we had at the last job where I got to dictate such things -- but unfortunately my current team didn't have such a thing in place before I started there and was getting away with it because the team was small. Suddenly the team doubles, the server starts groaning, and there's such a legacy of centralised development that moving to desktop development is a very very difficult process.
Which we're starting on. But meanwhile I need to do something about these broken windows. Sigh.
Kirrily "Skud" Robert perl@infotrope.net http://infotrope.net/
Reply to This
Parent