1 / 7

SOA Testing Overview: Quarterly Software Upgrade Cycle and Developer Insights

This overview delves into the quarterly software upgrade cycle for SOA testing, focusing on the processes and challenges involved, such as customization, limited regression testing, and the need for developer tools. It highlights the significance of testing environments, business sponsorship, and the reliance on flash copy systems for testing. The document outlines the balance of maintaining production systems while ensuring software upgrades are effectively managed, along with the complexities of application reuse and collaboration among skilled personnel.

denzel
Download Presentation

SOA Testing Overview: Quarterly Software Upgrade Cycle and Developer Insights

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOA Testing Overview

  2. Quarterly Software Upgrade Cycle IVPs, customisation, exits, limited regression testing Developer testing Developer tools Only ACCT envt “Business testing” Flash copy DEV LPARS Flash copy PROD LPARS Sysprog test LPARS Development “is production” Service variance once per quarter. Sat 8pm – 6am Midnight testing DEV LPARS PROD LPARS Change controlled

  3. SOA Environment Z/OS AIX MQ OTMA MQ IMS WAS JVM MPR MPR MPR JVM DDF DB2 ODBA JVM SP SP SP

  4. SOA Testing • AIX development environments connect to development mainframe systems • No equivalent flash copy test systems • Use the ‘offline leg’ instead • DR “Mega test” • Connects offline leg to flash copy systems • Reduces production resiliency • Requires cross platform coordination, skill sets, etc • Still tests only a small percentage of applications

  5. Flash copy Environment No distributed Systems to drive the mainframe! OTMA MQ IMS MPR MPR MPR DDF DB2 ODBA SP SP SP

  6. SOA testing • Development systems are production • Developers geared towards testing new stuff • Development work has business sponsorship • Software upgrades seen as ‘keeping the lights on’ • What is more important?

  7. SOA testing • Application reuse is good but • People writing code don’t know what they are driving on the mainframe • Difficult to get/find the right people for an application • Errors are difficult to diagnose • Especially true for out of hours testing

More Related