Date post: | 06-Dec-2014 |
Category: |
Technology |
Upload: | vijay-narayanan |
View: | 7,303 times |
Download: | 4 times |
Achieving Continuous
Integration with Tibco
BusinessWorks
Vijay Narayananhttp://softwarereuse.wordpress.com/
Technologies Involved
• Tibco BusinessWorks
• Apache Ant
• Apache Axis & XML Beans
• JUnit
• Subversion for source code control
• CruiseControl for Java
Your team’s passion for quality code, defect detection, and prevention
Act I - Using simple, effective test tools
• Used command line tools for smoke testing deployments on a development environment via XML message payloads
• It was super easy to run and very effective in testing web services against BusinessWorks - We usually ran it after deploying our BusinessWorks engine on the Server
Act II - Automated Tests
• Used Apache Axis2 & XML Beans to generate web service stub classes and run each test case as a JUnit test case
• Created generic ant scripts for compiling JUnit tests and reporting test results using JUnitReport
• Ran our full battery of test cases as an automated Ant script daily. This was a manual event…
Act III - Cruising with Continuous Integrations• Found on the web a Apache Ant
script for deploying and starting BusinessWorks engine on windows Tibco Administrator
• Integrated CruiseControl with Subversion to build and deploy our ‘latest’ processes and JUnit to run our automated tests on a continuous basis
Continuous Integration High Level Steps
Some Sample Screenshots
JUnit Results Summary Email
CruiseControl Dashboard
3 Key Benefits
• Confidence that your processes work as expected prior to your client discovering broken code/functionality
• Agility – Upgraded to newer version of Tibco iProcess within a week
• Defect detection and prevention - discovered and fixed 600+ defects before deploying to server environment!
But the biggest benefit...
Is a charged up team ready to change,
improve, and support the code base on a continuous basis!