Product Pipelines Swapnil Gupta – QA Manager Rushikesh Prabhune – Software Technical Consultant PTC Software India Pvt. Ltd.

Abstract Product release timelines and delivery schedules are getting shorter and shorter in the new era. In the efficient model for product delivery it becomes critical to get the product build in continuous delivery model and even tested/validated as well. In continuous delivery model, the changes in the product are continuous and it needs to be tested quickly to get the instant feedback and corrections required if any. Our product builds are following continuous delivery mode. Each build contains the changes which have come into the system from source control after previous build. The build has and displays the details about the changes incorporating it. During the process of the build there are multiple phases. Starting from creating the installer for that particular build, installing the build, validating the installation phase for any of the issues. Once the installation phase is completed successfully, the testing phase happens in a staggered manner. Each successful build goes through the round of BCO (Build Check Out) checks. If the build passes through the BCO phase and no issues are observed then the canary phase of automation testing happens which covers majority of the product functionalities. Once the criteria for the canary phase is met then the build is made available to the entire organization for testing and validation purpose.

Basic Questions Product Pipelines Can we deliver it faster? I have submitted code – When can I see the results? What is the status of my code? What the state? What is the state of product?

Developer Integration Tester Code Fix Integrate Build Test Report Roles Developer Code Fix Integration Integrate Build Tester Test Report

DevOps Culture

WindchillProduct Pipeline Product Pipeline Cycle WindchillProduct Pipeline Code Integrate Build Test Analyze Report

Tooling available

Jenkins - DevOps

Product Pipeline – Detail

Product Pipeline – Detail Development – Continuous Code inflow Integration – Integrate and Build every 4 hours Build Check Out – Basic checks for Build validation Canary Phase – Automated testing of the build Analyze – Results and report Deploy – Build released to All

Product Pipeline – Dashboard Provides the details about incoming submissions Gives snapshot of ongoing builds Gives preview of each phase like Install, Deploy, Test etc. Gives quick indication of failure Provides the way for analysis of failures (links) Provides the overview of Testing phase Gives Test Automation results overview Quick access to detailed test results (Hector)

Product Pipeline – Unique features Git – Source control system used In-house built radar framework for automated testing Selenium – Automation tool used In-house built Hector for automated tests results collection

References & Appendix https://www.google.co.in/

Author Biography Swapnil Gupta Working as QA Manager @ PTC Software Work experience 12+ years in QA Currently leading Enterprise Upgrade, Migration and Cross Product Services Team Rushikesh Prabhune Working as QA Technical Consultant @ PTC Software Work experience 10+ years in QA Currently leading Automation Infrastructure Team

Thank You!!!