![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Integration Testing Tasks Topic Summary: Created On: 8-Aug-2007 13:12 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We have a need to alter the classpath file for our integration testing projects. These changes are specific to the Integration Testing projects and should never be passed back to the developers working projects. Note that we have created a custom purpose for these projects because their update properties are not the same as the OOTB configurations for projects with the integration testing purpose.
We checked the objects into the "test" state in the hopes that it would not be included in the developers projects, but unfortunately the OOTB configuration for collaborative simply picks up all completed tasks and will apply objects in the test state to their projects. I would like, if at all possible, to refrain from changing the OOTB configuration for collaborative development. Since our integration testing is not using the OOTB configuration, I would like to keep the customization for task pickup there, but am not sure what to do with this task to keep it in integration testing, and out of collaborative. Anyone else experiencing this situtation? Would appreciate any suggestions! Thanks! ------------------------- Angela Kim |
|
![]() |
|
![]() |
|
Angela,
You should be able to do this simply by creating a new component/release pair for integration. Then, since the integration would belong to this release, it would not be automatically brought into the collaborative for the standard development release. This could also be taken care of at the build level in the source itself, but that would take some development resources, and the change would be visible to the developers, the build would just check to see if it is being run as integration and update the classpath at that stage rather than in the reconfigure step. Your choice. The latter leaves you will less maintenance, however, the former is all under your control, so you can change it easier, it just means that each new release would require this parallel release for integration testing. Have Fun, RoN ------------------------- RoN Zorn Beacon Associates Inc. RZorn@beaconassociates.net |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
Integration Testing Tasks
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.