Your SlideShare is downloading. ×
6.11.2013   - 2013 - Continuous Delivery - Testing for Agile Through Continuous Delivery
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

6.11.2013 - 2013 - Continuous Delivery - Testing for Agile Through Continuous Delivery

1,075
views

Published on

Series Name: Continuous Delivery …

Series Name: Continuous Delivery

Webcast Title: 2013 - Continuous Delivery - Testing for Agile Through Continuous Delivery

Date: June 11, 2013

Presenter: Chandra Venkatapathy

Published in: Technology, Business

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,075
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Continuous Delivery – Agility with ContinuousTestingChandra VenkatapathySr Product Manager, DevOpsChandrav@us.ibm.com© 2013 IBM Corporation
  • 2. Software innovation is crucial to competitiveness
  • 3. 3Market shifts are fundamentally changing the waybusinesses approach software driven innovationMacro Business EnvironmentIncreasing regulatory environments drivethe need to reduce riskEmpowered UsersConsumerization of IT drivesthe need for apps with highquality customer experienceTechnology TrendsMobile, social, big data, cloud,intelligent/connected systemsdrive the need for agilityMobileCloudIntelligent/Connected Systems  SocialBig DataClients are trying to rapidly innovate and become agile with systems of engagementAt the same time need to evolve their systems of records and manage regulatory compliance,reduce costs by outsourcing and provide world class customer experienceMulti-sourcingIncreasing outsourcing drivethe need for governance3
  • 4. Enterprises are using Systems of Interactions to drivebusiness innovation…Systems of InteractionContinuousclient experiencePartner valuechainCloud-basedServicesSystems of Engagement Systems of RecordCRM HRDB ERPMaintain stability andcompliance of corebusiness systemsProvide differentiating servicesand customer experience togrow market share andrevenueRapidly improve and evolveservices based on customerfeedback and success metrics
  • 5. … however, they are struggling to do soSystems of InteractionContinuousclient experiencePartner valuechainCloud-basedServicesSystems of Engagement Systems of RecordCRM HRDB ERPIT Operations:Pressure for rapid apprelease impacts overallsystem stabilityLine-of-business:Limited capacity toinnovate on newproducts and servicesDevelopment/Test:Speed mismatches between faster movingfront-end and slower moving back-endsystemsapplications rolledback due to qualityissues escapinginto production51%experience delaysin integration,configuration andtesting of applications41%Of resources devotedto maintainingexisting systems andproducts80%to deliver applicationchanges tocustomers4-6 Weeks
  • 6. 6Accelerate Software DeliveryExpanding collaboration to include customers, LOB and others to eliminate organization silosBalance speed, cost, quality and riskAutomating manual processes across delivery lifecycle to eliminate waste/delays and compliance trackingReduce time to customer feedbackEnabling a customer feedback loop for continuous improvementDevOpsEnterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedbackDevOps LifecycleOperations/ProductionDevelopment/TestCustomers Business OwnersContinuous Innovation, Feedback and ImprovementsMonitor and OptimizePlan and Measure Develop and Test Release and Deploy
  • 7. DevOps Principles and Values Develop and test against a production-likeenvironments Iterative and frequent deployments using repeatableand reliable processes Continuously monitor and validate operational qualitycharacteristics Amplify feedback loopsPeopleProcessToolsPeopleProcessTools
  • 8. Agile in the real world Geographically distributed teams Independent test teams– Centers of Excellence– Economy of scale Complex, heterogeneous systems Mini-waterfall inside the sprint– Plan– Develop– Test
  • 9. Release Management and Risk9B u ildS e r v ic eABCDEF u n c T e s t S t a g eS y s T e s t P r o dLarge Batch Sizes• Services: Many• Dependencies: Many• Changes: Many• Complexity: Large• Impact of Failure: Large• Failure Analysis: DifficultBig Bang
  • 10. Patterns of challengesDifferences in dev andops environmentscause failuresBacklog of agilereleases that Opscannot handleManual (tribal)processes for releaselackrepeatability/speedLack of feedback andquality metric leads tomissed service leveltargetsDailyBuildMonthlyDeliveryWho didthis lasttime?Dave…Dave’s nothereman…DevProd
  • 11. EnvironmentEnvironmentSolution: Virtualize, Standardize and automate the deploymentOutput of a process, such,as Dev BuildConfigurations specific toDeployment definitions, SLAsApplicationApplication ConfigurationConfigurationPhysical or Virtual InfrastructureIaaSPaaSChangeFrequencyLowHighH/WOSOS/ConfigMiddlewareAppMiddewareConfigApp Config
  • 12. Standardize: infrastructure deployment with environment patternsCommunicate and share environment patternsIssues– Dev environments different from productionenvironments– Difficult to provision test environmentsSolution– Define standard Virtual System Patterns forenvironments– Share patterns between Dev and Ops to improvecommunications– Repeatable and reliable process to provisionbase environments (rubber stamps)FunctionalVerificationTestEnvironmentFunctionalVerificationTestEnvironmentUserAcceptanceTestEnvironmentUserAcceptanceTestEnvironmentProducts:IBM PureSystemIBM SmartCloud OrchestratorIBM Workload Deployer
  • 13. Standardize: Content Delivery for the environmentApplication Release, and ConfigurationIssues– Difficult to keep track of content, versions andenvironments– Keeping up with speed of development– Errors in deploymentSolution– Automate deployments of applications andconfiguration across multiple environments– Repeatable and reliable process to deliver contentlinked to dev, test, and production processes(rubber stamps)– Release ApprovalsVersionedArtifactsQAEnvironmentProductionEnvironmentDevelopmentEnvironmentArtifacts Artifacts ArtifactsExecute Against Execute Against Execute AgainstQADeploymentProductDeploymentDevelopmentDeploymentApplication ModelProducts:Rational Automation Framework
  • 14. Problem: Dependencies slow down deployment ofproduction-like environments14Week 4ServiceABCDEStageSys Test ProdWeek 8• Service A dependent on Service B: Having different delivery schedules• Service D dependent on 3rdparty applications; available in system testApplicationApplication
  • 15. Virtualize: Test dependencies and test services Virtual Services created fromService specifications or from recording actualtraffic to existing services/applications Virtual Services further customizedTo simulate simple to complex behaviors (e.g.negative testing)To simulate latency, performance profiles, etc. Virtual Services published for consumption bydevelopers, testersTesting can start earlier: Testers can now createtheir tests against virtual services Systems can be incrementally tested as sub-systemsbecome available15VirtualVirtualIssues– Test services / System dependencies notavailable on-time; or costly to provision andmanageSolution : Test VirtualizationProduct: Rational Test Virtualization
  • 16. Incremental Integration TestingIncremental Integration TestingActual ComponentStubbed ComponentUnits are introduced into the continuousintegration cycle in a prioritised, controlledfashion.Units not yet built can be simulated and testedagainst.Incremental Integration Testing16
  • 17. Integration Testing lags astep behind the codeProblem: Agile Delivery BacklogTesterSetup integration testenvironmentDeveloperWrite & delivercodeNightly build(s)Compile, unit test, publishDeveloperDeveloperDeveloperDeveloperDeveloperN days to install & configureIteration 1 Design, Code,TestWeeks 2 - 6Integration testiteration #1IterationplanningWeek 1Iteration 2 Design, Code,TestWeeks 8 -12Integration testiteration #2SVTprepIterationplanningWeek 7N nightly builds are piling up
  • 18. Solution: Continuous Integration testing for Builds (with self-service)Nightly build is not publisheduntil integration tests run.Nightly build is not publisheduntil integration tests run.Compile Unit TestInstall &ConfigureIntegrationTestEnvironmentPublishResultsRun TestsRational QualityManager•Smoke Tests•Sandboxes•Self-provisioning•Smoke Tests•Sandboxes•Self-provisioning
  • 19. Testing continuously19Small Batch Size• Services: Few• Dependencies: Few• Changes: Few• Complexity: Small• Impact of Failure: Small• Failure Analysis: SimpleABC
  • 20. Continuous Delivery PipelineDevelopment BuildVerificationEnvironmentsSystem Integration TestEnvironments-Iterative Testing,Performance TestingUser AcceptanceTest EnvironmentsProductionEnvironmentConsistent Delivery of Environments, Content, and Deliverable
  • 21. DevOps Tool ChainApplication Release ManagementCloud ProvisioningApplication Deployment AutomationRational Collaborative LifecycleManagement SolutionRational Test WorkbenchRational Test Virtualization Server SmartCloud Control DeskJenkinsRational Build ForgeSmartCloud OrchestratorIBM Pure ApplicationSystemSmartCloud ApplicationPerformance ManagementuBuild21
  • 22. Continuous testing with virtualized servicesAutomating deployment and testing to production-like environmentsDatabases MainframeapplicationsThird-partyServicesRational Test Virtualization ServerApplicationchangesbeing testedvirtualized servicesDevDev QAQADeployRationalTeamConcertJenkinsBuildDeployRational Test WorkbenchTestConfigureUrbanCode UDeploy
  • 23. Enabling the DevOps lifecycle23DevOps FoundationOpen Lifecycle and Service Management Integration PlatformDevOps LifecycleOperations/ProductionDevelopment/TestCustomers Business OwnersContinuous Innovation, Feedback and ImprovementsEcosystemBestPracticesMonitor and OptimizePlan and Measure Develop and Test Release and DeployOSLC
  • 24. Call-to-Action Identify the customer pain for Quality– Patterns of Challenges– Cost– Time Show how IBM Solves with DevOps / Continuous Delivery for Testing– Issues, Solution, Capabilities– IBM UrbanCode, Rational Test Virtualization Get Acquainted with IBM UrbanCode, and Rational Test Virtualization
  • 25. Sales ResourcesThis site is updated weekly with new collateralBOOKMARK THIS PAGEhttps://w3-03.sso.ibm.com/software/xl/portal/content?synKey=O227209M89128T39
  • 26. 26Contacts for UrbanCode Lotus Notes Help ID: AskUrbanCode/Dallas/IBM Sellers Resource: http://w3.ibm.com/software/xl/portal/content?synKey=O227209M89128T39 WW Sales Integration Executive: Ann Marie Somerville: amsomerville@us.ibm.com Transition Executive: Peter Spung: paspung@us.ibm.com Rational Product Management: Albert (Wing Hong) Ho: winghong@us.ibm.com More information on UrbanCode: http://www.youtube.com/user/UrbanCodeSoft26
  • 27. 27
  • 28. 28© Copyright IBM Corporation 2013. All rights reserved. The informationcontained in these materials is provided for informational purposes only, and isprovided AS IS without warranty of any kind, express or implied. IBM shall not beresponsible for any damages arising out of the use of, or otherwise related to,these materials. Nothing contained in these materials is intended to, nor shallhave the effect of, creating any warranties or representations from IBM or itssuppliers or licensors, or altering the terms and conditions of the applicable licenseagreement governing the use of IBM software. References in these materials toIBM products, programs, or services do not imply that they will be available in allcountries in which IBM operates. Product release dates and/or capabilitiesreferenced in these materials may change at any time at IBM’s sole discretionbased on market opportunities or other factors, and are not intended to be acommitment to future product or feature availability in any way. IBM, the IBM logo,Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM productsand services are trademarks of the International Business Machines Corporation,in the United States, other countries or both. Other company, product, or servicenames may be trademarks or service marks of others.

×