Re: [Ccnet-devel] Integration CruiseControl .NET with UI tools

[Jeff B. <Je...@in...>]

Actually, I ended up using CCNet to run all of my tests including GUI
tests on a separate server.  So the main build server fires off a
force-build command to the test server which pulls up a zip file of the
last build, installs it and runs the tests.  Works pretty well.
=20
So you can indeed use CCNet to run yours tests, just set it up on
dedicated build and test servers and configure them accordingly.
=20
Jeff.

________________________________

From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Foster,
Richard - PAL
Sent: Friday, September 29, 2006 6:21 AM
To: ccn...@li...
Subject: Re: [Ccnet-devel] Integration CruiseControl .NET with UI tools


Chris,
=20
I would agree completely with your comments... but so far I have no
experience doing what you describe. Do you? If so, do you have any
pointers for how to accomplish GUI testing on a remote (possibly
virtual) machine?
=20
I'd also love to be able to perform some kind of "smoke test" on the
installation itself, but for precisely the reasons you describe I don't
want to be doing so on the build machine. Any hints you (or anyone else)
can offer on automated installation testing would be appreciated.
=20
Regards,
Richard
________________________________

From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of
Christopher Guest
Sent: Thursday, September 28, 2006 19:16
To: ccn...@li...
Subject: Re: [Ccnet-devel] Integration CruiseControl .NET with UI tools



Hi,

            It's not a direct answer to your question  [about running UI
tests from CI build scripts] .

=20

Personally I'd steer clear of running tests like this on a build
machine.  If I were tasked with this - I'd move towards batching tests
off to another (virtual) machine for them to be completed remotely.  I'd
come to this conclusion because I'd want to keep my build machine as
clean as possible.=20

Interacting with a UI for testing suggests to me that some kind of
installation may take place before the tests can be run.  A dodgy
installation can then=20

damage the build.  Installation procedures are notorious for going wrong
in development.  Consequently tracking down reasons for broken builds
can be difficult and time consuming. =20

=20

However, if your project is simple and doesn't have complicated
installations then unfortunately I have nothing more to offer than what
has already been said. =20

=20

Thanks,

Chris.=20

=20

________________________________


* C O N F I D E N T I A L I T Y N O T I C E *
-----------------------------------------------------------
The content of this e-mail is intended solely for the use of the
individual or entity to whom it is addressed. If you have received this
communication in error, be aware that forwarding it, copying it, or in
any way disclosing its content to any other person, is strictly
prohibited. Peek Traffic Corporation is neither liable for the contents,
nor for the proper, complete and timely transmission of (the information
contained in) this communication. If you have received this
communication in error, please notify the author by replying to this
e-mail immediately and delete the material from any computer.