IBM OS/390 User Manual
test phase will have its own test plan. The key application development people at
the installation must be involved when the test team is assembled.
the installation must be involved when the test team is assembled.
Testing should not be something that just happens. Testing activities are an
integral part of any migration plan and must be designed and controlled. When
some plans are drafted, all too often, the word
integral part of any migration plan and must be designed and controlled. When
some plans are drafted, all too often, the word
″
testing
″
is all that appears on the
task list or PERT chart. More thought and design should be devoted toward
testing activities, so that proper resources and schedules can be allocated at the
outset. Relative to testing, DP management has the responsibility to determine:
testing activities, so that proper resources and schedules can be allocated at the
outset. Relative to testing, DP management has the responsibility to determine:
•
What applications are to be tested.
•
What constitutes a test (for example, parallels, data to be used, and so on).
•
What audit information is necessary (SMF accounting information, operator
logs, and so on).
logs, and so on).
•
What acceptance criteria is required to show proof of success (timings,
output compared magnetically, and so on).
output compared magnetically, and so on).
•
Who has the completion sign-off responsibility.
Jobs selected during the specifications phase, typically those scheduled to run
within four weeks after the actual conversion and switchover, are regression
tested in the OS/390 environment. OS/390 regression tests require careful
planning and organization, OS/390 machine time and disk space, full access to
VSE production procedures and documentation, availability of data and criteria to
validate test results and direct participation of the customer. Problems
discovered during the OS/390 regression tests are analyzed both in nature and
in frequency. Typical solutions for problems with multiple occurrences involve
improvements to the automated mass conversion process (conversion tool
within four weeks after the actual conversion and switchover, are regression
tested in the OS/390 environment. OS/390 regression tests require careful
planning and organization, OS/390 machine time and disk space, full access to
VSE production procedures and documentation, availability of data and criteria to
validate test results and direct participation of the customer. Problems
discovered during the OS/390 regression tests are analyzed both in nature and
in frequency. Typical solutions for problems with multiple occurrences involve
improvements to the automated mass conversion process (conversion tool
′
s
custom modification) followed by new trial mass conversions.
The OS/390 regression tests and repetitive trial conversions are organized into
an interactive loop of tasks including:
an interactive loop of tasks including:
•
Orientation to the regression test phase
•
Defining a regression test plan with scenarios for batch job scheduling and
for execution of online transactions
for execution of online transactions
•
Defining a procedure to verify batch and online test results
•
Executing online transactions
•
Preparing and executing batch jobs
•
Verifying and validating test results
•
Identifying and analyzing test exceptions
•
Applying short-term solutions to promptly resume the tests in progress
•
Reviewing the nature and frequency of test exceptions
•
Designing and developing permanent solutions based on the improvement of
the automated mass conversion process
the automated mass conversion process
•
Refining the conversion tools custom modification
•
Supplying fresh copies of the conversion inventory for each new trial
conversion
conversion
•
Performing trial mass conversions
•
Supplying new OS/390 JCL and programs for test in OS/390
Chapter 32. Conversion Process
509