Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Integration build process


Thanks for raising this topic. I agree with the approach. We need to start applying more testing discipline to our builds.

I'd like to see each component publish a document that describes what should work and how to test it. This could be the tutorial for the component and could evolve over time. This document would be useful for the other developers. They could run the test and report success of failure to the mailing list.

The same document could also be the basis for the Milestone exit criteria. We don't declare the Milestone unless the tests pass. IMHO, a Milestone is not a date. It is a set of function that works. If the function doesn't work, we delay the Milestone until it does.

I suggest we post all component test plans in a well-known place, e.g. for WST server tools:

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx

Timothy Deboer/Toronto/IBM@IBMCA
Sent by: wtp-dev-admin@xxxxxxxxxxx

12/03/2004 08:35 AM

Please respond to

[wtp-dev] Integration build process


After asking around, no one has been able to tell me how an integration build is declared or when it happens. Therefore, I'd like to propose the following process:

*Component leads* are responsible for testing their component before an integration build occurs, to ensure that we catch last minute defects before the IB and go into it expecting to declare it immediately. Once the candidate integration build occurs, they must test again and let the subproject leads know whether the integration build is good for their component, or whether there are defects that they want to fix.

Note that the component leads do not actually need to do the testing themselves. :) They are just responsible for getting it done, and this may be using a combination of passing JUnit tests, manual testing by anyone familiar with the component, smoke testing, a formal FVT test, good reports on the newsgroup, etc.

*Subproject leads* are responsible for getting the reports from the component leads, following up if they haven't heard anything, and deciding together when to declare the IB. I'll assert that it is completely in their power to decide whether or not to declare the IB - for instance, they could declare an IB if they've heard good reports from 80% of the component leads but can't get ahold of the other leads and don't want to wait. And they can decide (with input from the component leads) whether a particular defect from one of the components is important enough to delay the IB and respin.

Once an IB is declared, or if it is delayed more than usual, the subproject leads are responsible for posting the information, either on the build page or to the mailing list.



Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503  (tieline 969)

Back to the top