Simple tools to fight the bigger Quality Battle Continuous Integration using batch files and task scheduler www.testinggeek.com By: Komal Joshi Director:Atlantis Software Ltd. Patrick Martin Sr Software Engineer (Consultant)

Agenda www.testinggeek.com Introduction to CI How it works CI suitable for our needs Challenges Faced Our Solution Implementation Q/A

Introduction to CI

How it works

CI suitable for our needs

Challenges Faced

Our Solution

Implementation

Q/A

Say Hello to CI.. www.testinggeek.com Software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Integration verified by an automated build (including test) integration errors are detected as quickly as possible. Significantly reduced integration problems Teams develop cohesive software more rapidly and to higher quality standards.

Software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day.

Integration verified by an automated build (including test) integration errors are detected as quickly as possible.

Significantly reduced integration problems

Teams develop cohesive software more rapidly and to higher quality standards.

www.testinggeek.com

Why CI ? www.testinggeek.com Last minute changes Resource Crisis Quality was very important for financial application Tight schedule

Last minute changes

Resource Crisis

Quality was very important for financial application

Tight schedule

Challenges www.testinggeek.com

Challenges Faced www.testinggeek.com Application Delphi based Standalone desktop Resources Few Not highly technical So we needed a solution that was: Easy to implement Not tied to a specific technology Could be easily replicated Should be a simple one click solution. Easily configurable.

Application

Delphi based

Standalone desktop

Resources

Few

Not highly technical

So we needed a solution that was:

Easy to implement

Not tied to a specific technology

Could be easily replicated

Should be a simple one click solution.

Easily configurable.

Solution was www.testinggeek.com No heavy weight Client/Server application but task schedulers No XML but easily configurable text files No fuss-setup but one click execution of batch files 'Out of the box' continous build batch process

No heavy weight Client/Server application but task schedulers

No XML but easily configurable text files

No fuss-setup but one click execution of batch files

'Out of the box' continous build batch process

Key Features www.testinggeek.com Distributed in nature No web tools commonly associated with modern distributed architecture. The entire system was achieved by simple text files. No fuss batch files Open source and simple tools Technology Agnostic

Distributed in nature

No web tools commonly associated with modern distributed architecture.

The entire system was achieved by simple text files.

No fuss batch files

Open source and simple tools

Technology Agnostic

High Level Implementation www.testinggeek.com developer tester repository build appliance test appliance App1 more... more... App2 step 0 step 1 step 2 step 2 App4 App3 step 3 step 4 step 5 - test! test appliance

Process Steps www.testinggeek.com step 0: run the product build script creates / updates checkout step 1: develop / test product can be developer, tester or ad-hoc testing step 2: commit changes can be developer, tester or ad-hoc testing step 3: post-commit actions repository post-commit actions queues up revisions to be built (perhaps) step 4: build revision (perhaps) build appliances run product build script: build if required due to update step 5: test (perhaps) test appliances run product update script and test

step 0: run the product build script

creates / updates checkout

step 1: develop / test product

can be developer, tester or ad-hoc testing

step 2: commit changes

can be developer, tester or ad-hoc testing

step 3: post-commit actions

repository post-commit actions queues up revisions to be built (perhaps)

step 4: build revision (perhaps)

build appliances run product build script: build if required due to update

step 5: test (perhaps)

test appliances run product update script and test

www.testinggeek.com Subversion Repository Build Machines Test Machines VbSend Mail Utility

Overall Flow www.testinggeek.com repository post-commit + task drop markers to build machine(s) tasks on build machines pick up revisions; build successful build tasks drop test markers; notify tasks on test machines pick up revision build for test run tests; archive tested revisions summarise results and notify team commit to repository

Subversion Repository www.testinggeek.com Post Commit Hooks Copy the build-markers Scheduled tasks after 10 minutes Poll to check for markers Kick off scripts to Parse the machines names from .txt files Copy the markers to remote machines Run the scheduled tasks remotely

Post Commit Hooks

Copy the build-markers

Scheduled tasks after 10 minutes

Poll to check for markers

Kick off scripts to Parse the machines names from .txt files

Copy the markers to remote machines

Run the scheduled tasks remotely

www.testinggeek.com Repo: Config File with machine name and build Repo: Config File with machine name and task names

Build Machine www.testinggeek.com Build-Scripts Kicked off by the parameters in Schedule tasks Scheduled tasks after 10 minutes Poll to check for markers/Kicked off remotely Kick off scripts passed as parameters Copy the markers from build-rev to ‘done-revs’ Kick off scripts to Parse the Test machines names +Tests from .txt files Copy the markers to test machines Config files Normal text files containing- Test machine name Name of tests Type of release (Debug or normal)

Build-Scripts

Kicked off by the parameters in Schedule tasks

Scheduled tasks after 10 minutes

Poll to check for markers/Kicked off remotely

Kick off scripts passed as parameters

Copy the markers from build-rev to ‘done-revs’

Kick off scripts to Parse the Test machines names +Tests from .txt files

Copy the markers to test machines

Config files

Normal text files containing-

Test machine name

Name of tests

Type of release (Debug or normal)

www.testinggeek.com Build-Machine: Config File with machine name and Test

Test Machine www.testinggeek.com Automated-Test-Scripts Kicked off by the parameters in Schedule tasks Scheduled tasks after 10 minutes Poll to check for markers Kick off scripts passed as parameters Send Mail utility + Log Mail the results to people in the list from the log Any automation tool Should be invoked from command line

Automated-Test-Scripts

Kicked off by the parameters in Schedule tasks

Scheduled tasks after 10 minutes

Poll to check for markers

Kick off scripts passed as parameters

Send Mail utility + Log

Mail the results to people in the list from the log

Any automation tool

Should be invoked from command line

www.testinggeek.com sendmail.bat

www.testinggeek.com All sounds quite complex... How about a demo?

A CI Template www.testinggeek.com The process Commit to repository post-commit hook appends new revision notification to revs queue (asynchronous) post new revision notification post any revs found into revs queue of build appliance (asynchronous) build appliance pick-up of revs queue walk the revs queue: update and if file changes noted, build - move to done-revs notify team if successful build then post build notification to test appliance (asynchronous) test appliance pick-up of revs queue walk the revs queue: update and test - move to done-revs; notify team

The process

Commit to repository

post-commit hook appends new revision notification to revs queue

(asynchronous) post new revision notification

post any revs found into revs queue of build appliance

(asynchronous) build appliance pick-up of revs queue

walk the revs queue: update and if file changes noted, build - move to done-revs notify team if successful build then post build notification to test appliance

(asynchronous) test appliance pick-up of revs queue

walk the revs queue: update and test - move to done-revs; notify team

A Boot Strap Script www.testinggeek.com The complete bootstrap script simply takes a root folder argument and creates: the repository + extra folders/files if required in the repo sub-folder an example project in the repository the revision queue check task the folder for the "build appliance" checkout the folder for the "test appliance" checkout the post-commit hook the script to post new revisions the scheduled task to invoke the post new revisions script the update/build/test scripts for the appliances in the scripts folder the scheduled task to update and build the "build appliance" checkout the scheduled task to update and test the "test appliance" checkout

The complete bootstrap script simply takes a root folder argument and creates:

the repository + extra folders/files if required in the repo sub-folder

an example project in the repository

the revision queue check task

the folder for the "build appliance" checkout

the folder for the "test appliance" checkout

the post-commit hook

the script to post new revisions

the scheduled task to invoke the post new revisions script

the update/build/test scripts for the appliances in the scripts folder

the scheduled task to update and build the "build appliance"

checkout

the scheduled task to update and test the "test appliance"

checkout

A Boot Strap Script www.testinggeek.com Final output of the script: ROOT - scripts - repo - build-appliance - test-appliance

www.testinggeek.com boot-strap.bat It's that simple #1

www.testinggeek.com post-revs.bat It's that simple #2

www.testinggeek.com build-revs.bat It's that simple #3

www.testinggeek.com test-revs.bat It's that simple #4

www.testinggeek.com SHOW Me the DEMO please #$*#

www.testinggeek.com setup of CI system using bootstrapper

www.testinggeek.com CI tasks created by bootstrap

www.testinggeek.com example developer change

www.testinggeek.com output from CI system due to change

QUESTIONS??? www.testinggeek.com

www.testinggeek.com Thanks Contact : Komal Joshi: [email_address] [email_address] Patrick Martin: [email_address] Thanks To our team: Colin Towers, Ben Murray and Fergus Bown