Achieving Continuous Integration With Tibco BW

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Achieving Continuous Integration With Tibco BW - Presentation Transcript

    1. Achieving Continuous Integration with Tibco BusinessWorks
      • Vijay Narayanan
      • http:// softwarereuse.wordpress.com /
    2. Technologies Involved
      • Tibco BusinessWorks
      • Apache Ant
      • Apache Axis & XML Beans
      • JUnit
      • Subversion for source code control
      • CruiseControl for Java
    3. Your team’s passion for quality code, defect detection, and prevention
    4. 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
    5. 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…
    6. 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
    7. Continuous Integration High Level Steps
    8. Some Sample Screenshots
    9. JUnit Results Summary Email
    10. CruiseControl Dashboard
    11. 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!
    12. But the biggest benefit...
    13. Is a charged up team ready to change, improve, and support the code base on a continuous basis!

    + Vijay NarayananVijay Narayanan, 7 months ago

    custom

    860 views, 0 favs, 3 embeds more stats

    Presentation on achieving continuous integration wi more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 860
      • 851 on SlideShare
      • 9 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 15
    Most viewed embeds
    • 5 views on http://softwarereuse.wordpress.com
    • 3 views on http://artofsoftwarereuse.com
    • 1 views on http://www.visualcv.com

    more

    All embeds
    • 5 views on http://softwarereuse.wordpress.com
    • 3 views on http://artofsoftwarereuse.com
    • 1 views on http://www.visualcv.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories