Forum Discussion
TonyMro
12 years agoOccasional Contributor
Rachel,
If you hope to some day seamlessly integrate your automated testing process with your build delivery and deployment process, you'll need to work with your build engineers to come up with a strategy to support that goal. Here's a brief
overview of the method I've been using for integrating automated build acceptance
test suites with continuous integration build environments. This approach has been successfully implemented using test automation based on the TestComplete, QTP, SilkTest, and Rational Robot test tools on numerous projects over the last 10 years.
-
Upon successful completion of a nightly build, our build tools create a
Build Synchronization file that contains the version number of the
build, the date and time of the build, and the full path to the install
package. This build sync file is written out to a location on the
network that is monitored by our test automation systems. An example of a build
sync file is below:
[Build_Sync]
TARGET_APP=\\PDX-BUILD21\CPS_110_Staging\CPS-11.0_20110425_cps_11_main_D1_rb001.zip
VERSION=11.0.0.1
BUILD_NUMBER=11.0.0.1N_20110425_050318
BUILD_DATE=4/25/2011
BUILD_TIME=13:21
-
Our automated test suites are running on multiple VMs using the
TestExecute runtime engine and the TestCentricityâ„¢ Core Framework script extension. They monitor the network share, waiting for a
new Build Sync file to appear. When it does, each test system reads the
data out of the build sync file, then copies the install package to the
local hard drive, extracts the contents from the .zip file, runs the
silent installer to install the application, and then begins running the
test suites.
- When testing is completed, each test system
writes PC name into the build sync file so that they won't retest the
same build. Then they wait for receipt of a new build sync file.
-
We use both Hudson and Cruise Control for our various build process,
but both tools are capable of generating the build sync file.
If you hope to some day seamlessly integrate your automated testing process with your build delivery and deployment process, you'll need to work with your build engineers to come up with a strategy to support that goal. Here's a brief
overview of the method I've been using for integrating automated build acceptance
test suites with continuous integration build environments. This approach has been successfully implemented using test automation based on the TestComplete, QTP, SilkTest, and Rational Robot test tools on numerous projects over the last 10 years.
-
Upon successful completion of a nightly build, our build tools create a
Build Synchronization file that contains the version number of the
build, the date and time of the build, and the full path to the install
package. This build sync file is written out to a location on the
network that is monitored by our test automation systems. An example of a build
sync file is below:
[Build_Sync]
TARGET_APP=\\PDX-BUILD21\CPS_110_Staging\CPS-11.0_20110425_cps_11_main_D1_rb001.zip
VERSION=11.0.0.1
BUILD_NUMBER=11.0.0.1N_20110425_050318
BUILD_DATE=4/25/2011
BUILD_TIME=13:21
-
Our automated test suites are running on multiple VMs using the
TestExecute runtime engine and the TestCentricityâ„¢ Core Framework script extension. They monitor the network share, waiting for a
new Build Sync file to appear. When it does, each test system reads the
data out of the build sync file, then copies the install package to the
local hard drive, extracts the contents from the .zip file, runs the
silent installer to install the application, and then begins running the
test suites.
- When testing is completed, each test system
writes PC name into the build sync file so that they won't retest the
same build. Then they wait for receipt of a new build sync file.
-
We use both Hudson and Cruise Control for our various build process,
but both tools are capable of generating the build sync file.
Related Content
- 4 years agomats2021
- 9 months agooriShalhon
- 3 years agoAAB
- 8 years agoMarcovS
Recent Discussions
- 14 hours agoSvetaG