IBM OS/390 User Manual
32.5.6.1 Online Unit Testing
Prior to this task, an online test plan, and possibly detailed test scripts, have
been developed with and presented to the test team, together with
organizational instructions, during a pre-test orientation session.
been developed with and presented to the test team, together with
organizational instructions, during a pre-test orientation session.
CICS testing is an ideal place to begin the testing process. At least in theory,
CICS transactions are fairly transparent between OS/390 and VSE/ESA.
Assuming that the migration environment has been set up per the instructions in
Chapter 25, “Prepare the Migration Environment” on page 401 in this book,
CICS is the first area to be scheduled for testing and can occur very early in the
project.
CICS transactions are fairly transparent between OS/390 and VSE/ESA.
Assuming that the migration environment has been set up per the instructions in
Chapter 25, “Prepare the Migration Environment” on page 401 in this book,
CICS is the first area to be scheduled for testing and can occur very early in the
project.
The online unit testing results that are sought during this early testing are:
•
Get a screen to come up
•
Travel within the screen
•
Query a customer record
The testing continues with thorough sample unit testing of 30 to 50
representative transactions. The idea is to use limited resources (small test team
and DASD) to verify that the conversion specifications and the automated
conversion process generate sound OS/390 application material (programs,
screens and files), which execute without ending abnormally. Results and file
updates are verified. The conversion specifications and automated conversion
process usually need some adjustment before full-size resource-consuming
functional testing can start.
representative transactions. The idea is to use limited resources (small test team
and DASD) to verify that the conversion specifications and the automated
conversion process generate sound OS/390 application material (programs,
screens and files), which execute without ending abnormally. Results and file
updates are verified. The conversion specifications and automated conversion
process usually need some adjustment before full-size resource-consuming
functional testing can start.
32.5.6.2 Batch Unit Testing
Prior to this task, a batch test plan has been developed with and presented to
the test team, together with organizational instructions, during a pre-test
orientation session.
the test team, together with organizational instructions, during a pre-test
orientation session.
Batch application tests start with sample unit testing of 30 to 50 representative
daily jobs. The idea is to use limited resources (small test team and DASD) to
verify that the conversion specifications and the automated conversion process
generate sound OS/390 application material (JCL, code and files), which execute
without JCL error, abends or abnormal return codes. Report contents and file
updates are not verified at this stage. The conversion specifications and
automated conversion process usually need some adjustment before full-size
resource-consuming functional testing can start.
daily jobs. The idea is to use limited resources (small test team and DASD) to
verify that the conversion specifications and the automated conversion process
generate sound OS/390 application material (JCL, code and files), which execute
without JCL error, abends or abnormal return codes. Report contents and file
updates are not verified at this stage. The conversion specifications and
automated conversion process usually need some adjustment before full-size
resource-consuming functional testing can start.
32.5.6.3 Data Migration in Unit Testing
The topic of data migration is implied throughout all the phases of testing. In unit
testing transferring a couple of tapes of CICS data sets to MVS is sufficient for
testing. By the time you are performing test switchover dress rehearsals you are
copying data so that it matches exactly on both systems. In this way, data
migration and the testing phases are synchronized events. Discussions on data
migration will be included in each of the testing sections.
testing transferring a couple of tapes of CICS data sets to MVS is sufficient for
testing. By the time you are performing test switchover dress rehearsals you are
copying data so that it matches exactly on both systems. In this way, data
migration and the testing phases are synchronized events. Discussions on data
migration will be included in each of the testing sections.
32.5.6.4 Timing between Online and Batch Testing
Normally online unit testing will be completed early in the project. From a
project perspective, the focus frequently remains on the online workload and the
system testing phase of on-ine is started right after the unit testing ends. This is
because it is frequently too early in the project to begin batch unit testing. The
batch testing is more complicated than online due to the JCL conversion. This is
project perspective, the focus frequently remains on the online workload and the
system testing phase of on-ine is started right after the unit testing ends. This is
because it is frequently too early in the project to begin batch unit testing. The
batch testing is more complicated than online due to the JCL conversion. This is
512
VSE to OS/390 Migration Workbook