[Anthill-pro] Anthill Pro Testing Code

[Wai Lun Poon]

Does this mean that a change in testing code would trigger a rebuild of
the tools as well? That is a scenario we would like to avoid.

 

-Wai Lun

 

________________________________

From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Yanko,
Curtis
Sent: October 1, 2009 10:52 AM
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] Anthill Pro Testing Code

 

The 'testing code' can be it's own project that 'publishes' what is
needed to codestation so 'tools projects' can resolve them as
dependencies for use in build or secondary processes.

 

==========

Curtis Yanko

Application & Developer Infrastructure Services

Source->Build->Deploy

W: 860.702.9059

M: 860.881.2050

 

 

________________________________

From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Wai Lun
Poon
Sent: Thursday, October 01, 2009 10:37 AM
To: anthill-pro at lists.urbancode.com
Subject: [Anthill-pro] Anthill Pro Testing Code

Hi all,

 

 

There are a set of standalone tools built under our main build workflow,
we would like to test these tools with a suite of test scripts written
in python. These test scripts are currently stored in our CVS
repository. What would be the best method to utilize anthill with the
tools deployment and testing? From my understanding, it is possible to
create an additional non-originating workflow to the project and run a
secondary process, but with this method, it is not possible to check-out
the test scripts. Creating an additional originating workflow so that we
may check out test-scripts from the repository seems cumbersome. How is
testing accomplished in your setups? What are some good ways for
implementing this? Keep in mind that we do not wish to check out
testing-code as part of the project, we would like to keep the source
and testing code separate.

 

 

Thank you,

 

Wai Lun

 
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20091001/f469a1cc/attachment.htm