Front page | perl.perl5.porters |
Postings from September 2001
> My motivation behind this patch was to enhance testing rather than to > detract from it. Its target audience was pumpkings and core hackers. > My reasoning was that since the test target now takes much longer than > it did, primarily due the the assimilation of new modules, it can be > tempting to test less frequently than might be prudent. A test target > which tested core functionality, used in the knowledge that > it was not a > complete test, seemed a useful addition. > > If it turns out that this target is weakening the test suite, then > something should be done about it. Ultimately this might > mean removing > the target. However, I would imagine that in a short time, if things > are left as they are, only those people who need the target will > remember it, and they will use it responsibly. I hope I am right. Actually, when I'm doing core patching and I need to run tests every time I change a C file (say, about once a minute), I'll often use make minitest to expose immediate problems with my patches - "FAILED at test 1" or "dumped core" or whatever. Then when I get a patch finalized I run it through the entire make test and check for problems. It reduces my development time quite nicely. R.Thread Previous