"Now I want to run all the tests in all those projects, and I want to do it every day."

Just curious, do all those projects get modified/updated daily? If not, maybe only test those ones with CSV check in's.

An interesting thing will be project dependency. You might like to test a project, if what it depends on was changed, althought the project itself is not changed. That could starts something fun...

I really like what you are doing.

Recently I headed the system testing of a project, and lots of the testings involve GUI interfaces, so lots of those testing have to be done manually. I would like to hear from others, what they do in this case.


In reply to Re: Parallel maintenance on many projects, part II: The Testing by pg
in thread Parallel maintenance on many projects, part II: The Testing by brian_d_foy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":