Rene Rivera wrote:
On 2/1/2011 7:21 PM, Dave Abrahams wrote:
At Tue, 01 Feb 2011 10:12:45 -0600, Rene Rivera wrote:
That is, I don't think we can live without full trunk testing.
I'm curious why not. I'm fairly sure I don't want any resources wasted on it for my libraries.
Because in the three testing scenarios I mentioned it would be the only one to give you fully integrated testing without being in the release. Of course a full dependency integrated testing of an individual lib with a release base could be a substitute for full trunk testing. But for some components full dependency integrated testing might devolve back to close to full trunk testing. But again, this all depends on how close or far future procedures are to the current ones.
I would think that the decision to test any dependent libraries could be left to the tester. He could decide to do it if he had the resources - otherwise just test the library recently merged. Robert Ramey