70 likes | 189 Views
SOA Testing Overview. 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”.
E N D
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
SOA Environment Z/OS AIX MQ OTMA MQ IMS WAS JVM MPR MPR MPR JVM DDF DB2 ODBA JVM SP SP SP
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
Flash copy Environment No distributed Systems to drive the mainframe! OTMA MQ IMS MPR MPR MPR DDF DB2 ODBA SP SP SP
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?
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