Worldspan and RTF

Pam Clark, WorldspanThiru Thirupuvanam, TPF SoftwareTPF Users GroupArlington, VA

Date: October 9, 2007

Worldspan and RTF2

Table of Contents

> Where We Started

> Requirements for Regression Testing

> What Is RTF?

> Our Decision on RTF

> Our Current Run Environment

> What We Like

> What We Have Built

> Stats

> Wish List/Future

> Questions

Worldspan and RTF3

Where we started

> Utilized the Test Unit Tape (TUT) product with flat files for input

> Small, folded down test system

> Static database, time stamped circa 1894

> Exception code for system id to compensate

> TUT product support eliminated

> Less than 30% of program base being tested

Worldspan and RTF4

Requirements for Regression Testing

> Run daily

> Integrate with Implementation process

> Monitor for abends and differences

> Log results

> Notify programmers on failure

Worldspan and RTF5

What is RTF ?

> TPF Software product• Regression Test Facility

> Purposes• Quality assurance

• Measure the impact of planned changes on the TPF environment

> Steps• Baseline data is collected during a test suite of input messages

• Changes are made to TPF environment

• Second run data is collected

• Data is compared (customer responsibility)

> Components of RTF• Configuration File (customizable)

• Input Files (user defined)

• Output Logs

Worldspan and RTF6

RTF Illustration

Planned changes are made to system

Input script is run again, producing new output log

Baseline and second-run data are compared

CMSTPF

TPFPROGRAMS

DATA

InputScript

OutputLog 1

EventsInput

Messages

21 =?

2

TPFPROGRAMS

DATA

Worldspan and RTF7

RTF Configuration File

> Describes how RTF is to be run (scripts, events, etc.)

> Events• File data

– Records to be logged– Records not to be logged– Tape/GDS data to be logged

• ECBs involved– Number of tasks/ECBs involved to run this transaction– Resources used

• Trace data– Program path (ENTER/BACKs)– Other macros

• Messages– Input/Output

• Other Data– Abends/Errors– Console Messages

Worldspan and RTF8

Our RTF Decision

> Proof of concept phase

> Reviewed existing user experience

> POC results• Scalable

• Good fit with existing tools

• Ability to convert TUT flat files to scripts

• Output was comparable files

• Easy to isolate problem occurrence

• Environment allows programmers to recreate

• Good experience with vendor support

Worldspan and RTF9

Our Current Run Environment

> Large Test System• Restored ‘Daily’• Gen’d CMSTPF systems against Daily• Test System Availability = 97.7%

> Run with multiple IDs / gen’d systems

> Non-prime time hours

> Re-runs during prime time

> Super C used for Compares

Worldspan and RTF10

What We Like

> Separate test system with all utilities and support no longer required (eliminated small test system)

> CTFS used for lines/external connections

> Ability to split the runs easily across multiple ids

> Much finer granularity of data can be collected

> Scenarios and inputs can be changed quickly

> Scripts are flexible, allowing targeting of specific applications

> RTF configuration files enable specific events to be logged• Record ID logging

• Console messages

• Abends / Errors

• ECB usage

Worldspan and RTF11

What We Have Built

> Program Logs (Plogs)• Library of programs called by each script

• Cross referenced by script and by program name

• Manually maintained with macro trace results (ENTER/BACK)– EXECs strip the RTF log for the trace data to create the Plogs

> Tracking method for problem follow up

> Statistics for management reports• Collected manually, automation in progress

> Filters (Rexx /Pipelines)• Heavy development investment to handle ‘known’ differences

> Integration of script updates into Development Framework

Worldspan and RTF12

Measures of Success

> 75% reduction in control dumps from last half of 2005 to first half of 2006 (not all attributed to RTF)

> Test scripts contain 26,591 lines of input

> YTD segments tested = 39,554

> Reject approx. 8.2%

> Currently testing 75% to 80% of our program base (up from 30%)

Worldspan and RTF13

Our Challenges

> Timing of test system availability

> Volume of entries required due to non-static database

> Off Hour Support / Management (Applications)

> Can consume significant VM resources

> Comparison tools / filters

> Updating input scripts

Worldspan and RTF14

Wish List

> Improved Comparison Tool

> Managed Libraries for Scripts

> Management Reports

> RTF Lite for programmers

Worldspan and RTF15

Future

> Delta migration to zTPF planned for 2008

> Worldspan working with TPF Software to migrate their products to zTPF• ZIG (zTPF infrastructure for TPF Software products)

• TPF/GI (graphical debugger for zTPF)

• TPF/IDE (development environment for zTPF)

• SOURCE VIEW (source-level trace)

• RTF

• GI/TERM (terminal emulator for zTPF)

• TTFS (external connectivity for TPF/GI client)

Worldspan and RTF16

Questions

???