18
1 IBM _ Chapter Opening September 16, 2015 Presentation Title Shift left to drive continuous integration in mainframe software development

DevOps Enterprise Summit: Mainframe Automated Testing

Embed Size (px)

Citation preview

Page 1: DevOps Enterprise Summit: Mainframe Automated Testing

1IBM _

Chapter Opening

September 16, 2015Presentation Title

Shift left to drive continuous integration in mainframe software development

Page 2: DevOps Enterprise Summit: Mainframe Automated Testing

2IBM

@RosalindRad

Rosalind Radcliffe• IBM Distinguished Engineer• Chief Architect for DevOps for z Systems• 28 years in IBM• Started in ISPF Development• Worked in Services, responsible for SOA management,

modern development tooling for z/OS, and now DevOps

September 16, 2015Shift left to drive continuous integration in mainframe software development

Page 3: DevOps Enterprise Summit: Mainframe Automated Testing

3IBM _

@RosalindRad

The worlds leading

businesses run on z Systems

92 of the top 100 worldwide banks

23 of the top 25 US retailers

9 out of 10 of the world’s largest insurers

71% of global Fortune 500 companies

Shift left to drive continuous integration in mainframe software development September 16, 2015

Page 4: DevOps Enterprise Summit: Mainframe Automated Testing

4IBM _

@RosalindRad

~70% of all enterprise transactions touch a System z55% of all enterprise applications need the

mainframe to complete transactions

91% of surveyed CIOs said that new customer-facing applications are accessing the mainframe

The mainframe is here to stay with unmatched ability to support secure growth in data and transactions.

Mainframes process roughly 30 billion business transactions per day, including most major credit card transactions and stock trades, and money transfers.

It is estimated that 80% of the world’s corporate data resides or originates on mainframes.

IDC France, #mainframe spending represents 3% of the

spending but 65% of the mission critical applications

Shift left to drive continuous integration in mainframe software development September 16, 2015

Page 5: DevOps Enterprise Summit: Mainframe Automated Testing

5IBM

@RosalindRad

Mainframe Todayz13 – built for todays mobile workload• Reliability, Availability and

serviceability• Security• Scalability• 100 cyber Mondays each

day• Up to 10 TB of memory

September 16, 2015Shift left to drive continuous integration in mainframe software development

Page 6: DevOps Enterprise Summit: Mainframe Automated Testing

6IBM

@RosalindRad

System Reliability September 16, 2015Shift left to drive continuous integration in mainframe software development

Mainframe

Distributed

Less Reliable

More Reliable

Horizontal Scaling

Vertical Scaling

Page 7: DevOps Enterprise Summit: Mainframe Automated Testing

7IBM

@RosalindRad

Mainframe Testing problems today• Same process and tools for the last 30 years – it just

works why change it• No standard continuous integration procedures• Focus on separation of changes not early integration• Too costly to do automated testing• Shared environments

September 16, 2015

Region Shared Data

Region

Region

App 1

App 2

App 3

App 4

App 5

Shift left to drive continuous integration in mainframe software development

Page 8: DevOps Enterprise Summit: Mainframe Automated Testing

8IBM _

@RosalindRad

Solutions Automated Deployment for additional test environments

Application refactoring for

Services (APIs)

Process change for sift left testing

Integrated monitoring

Interface testing

Operations data used for

optimization

September 16, 2015Shift left to drive continuous integration in mainframe software development

Page 9: DevOps Enterprise Summit: Mainframe Automated Testing

9IBM

@RosalindRad

Automated Deployment for Environments• No MIPS charges• Create golden image • Dynamically deploy z/OS image • Automated deploy of application

updates and data • Used for development and

automated test runs

September 16, 2015Shift left to drive continuous integration in mainframe software development

IMS DB2

CICS

WAS MQ

z/OS

COBOL, PL/I, C++, Java,

EGL, Batch, Assembler,

X86 PC or HX5 Blade

running Linux

RD&T

RTC RDz RIT

Page 10: DevOps Enterprise Summit: Mainframe Automated Testing

10IBM

@RosalindRad

Process change for shift left testing• Developers need to be responsible for building unit tests • Run with code coverage to begin to understand what’s tested• Use virtual services to isolate to function changed• Don’t just do happy path testing, include negative testing• Also include code rules, and other code scanning on check-in• Automate testing as part of build

September 16, 2015Shift left to drive continuous integration in mainframe software development

Build Deploy Test Provision

Page 11: DevOps Enterprise Summit: Mainframe Automated Testing

11IBM

@RosalindRad

Interface Testing • Build interface tests to increase automated test coverage• SoE interface is first place to add testing, and define virtual

service to allow independent development • Use virtual services to isolate to function changed

September 16, 2015Shift left to drive continuous integration in mainframe software development

Phase 1 Phase 2 Phase 3

App

Test Case

Virtual Services

3rd Party Call

IMS Data Access CICS

Commarea Call

App

Test Case

Virtual Services

3rd Party Call

IMS Data Access CICS

Commarea Call

App

Test Case

Virtual Services

3rd Party Call

IMS Data Access CICS

Commarea Call

Page 12: DevOps Enterprise Summit: Mainframe Automated Testing

12IBM

@RosalindRad

Application refactoring for Services • Use automated testing to insure same results prior to

refactoring• Begin to break up monolithic programs• Create callable services

September 16, 2015Shift left to drive continuous integration in mainframe software development

API

API

APIReuses

Shares

APICombines

Shares

Composes

APIEnhances

External APIs

API

Consumes

API

API

Page 13: DevOps Enterprise Summit: Mainframe Automated Testing

13IBM

@RosalindRad

Integrated Monitoring• Use the production monitoring data to understand end

to end application performance• Examine the individual parts of the application to

determine areas for improvement• Use the same monitoring tools as in production to

configure monitoring thresholds while in development

September 16, 2015Shift left to drive continuous integration in mainframe software development

Page 14: DevOps Enterprise Summit: Mainframe Automated Testing

14IBM

@RosalindRad

Operations data used for optimization• Understand the most used or most CPU consuming

modules• Build automated tests to test these modules and update

with the latest compiler technology, if required• Understand the most common issues with

deployments, partner to reduce manual intervention, and improve process

September 16, 2015Shift left to drive continuous integration in mainframe software development

Page 15: DevOps Enterprise Summit: Mainframe Automated Testing

15IBM _

@RosalindRad

Financial Services ProviderTesting reduced from weeks to hoursGained visibility, transparency, and improved planning Used a common set of modern tools to improve overall development process. Adopted virtual services and automated testing as part of the process.

Bank Automated Testing reduced software development time by over 90% and decreased time to market by 40%Established automated virtual automated test environments to support the development and test teams, as well as move to automated testing.

Financial Services Company Automated deployment of resources to provide testing environments, can now deploy z/OS for a team in less than 40 minutes.

Internal z/OS Development Teams“With the modern tools JAT & Jenkins framework our BVT can run in half the time it used to take. This allows 50 additional regression test cases to be run with every build in less total time than the old tools required for just the BVT.”“Used to be very long to setup a system (VM). Can now setup 10 systems < 1/2 day” and “Easy to start a new system if my current instance hosed up” .

Success StoriesShift left to drive continuous integration in mainframe software development September 16, 2015

Page 16: DevOps Enterprise Summit: Mainframe Automated Testing

16IBM _

@RosalindRad

Mainframe Testing – Key Takeaways

1.Mainframe development must modernize, the practices and tools created 30 years ago are no longer appropriate. Automated testing for mainframe environments is a change that must be supported via tools and time.

2.Having the capacity needed for automated testing is critical. Development and test capacity for mainframes to support automated testing is required. To avoid the MIPS charges on existing hardware Rational Development and Test Environments for System z can be used.

3.The use of interface testing and virtual services can be a good way to get started. Mainframe applications are usually called via an external interface, use this to build automated interface testing to build up test cases for existing capability.

Shift left to drive continuous integration in mainframe software development September 16, 2015

Page 17: DevOps Enterprise Summit: Mainframe Automated Testing

17IBM

@RosalindRad

What I need help with• What are the metrics needed to show automated

testing is providing the coverage to stop all the manual testing for regression?

September 16, 2015Shift left to drive continuous integration in mainframe software development

Page 18: DevOps Enterprise Summit: Mainframe Automated Testing

18IBM _

Lorem Ipsum dolor sit, to amet consectetur irare a adispicing elit done etectals tempus.

Quote

“ “Author, Secondary Information

September 16, 2015Presentation Title September 16, 2015IBM

Thank You!

18