Skip to content

Latest commit

 

History

History

Automated-Test-Facility-for-Batch-Applications

README.md

Automated Test Facility for Batch Applications

This procedure allows Endevor processors to automate the tailoring, submission and evaluation of Batch application tests. Tests are triggered automatically by the Move or Generate actions of elements of any element type. For example, you may initiate automated tests when a COBOL program is Moved or Generated at a certain stage of Endevor. The test will locate, tailor, submit and evaluate results for one or more JCL elements whose names appear in the "OPTIONS" content of the COBOL program.

The use of "OPTIONS" is not a new concept to Endevor. Typically, they are objects that provide detailed instructions to the CONPARMX steps of an Endevor processor. To implement this procedure, it is not necessary that you be familiar with the use of OPTIONS or with the CONPARMX utility. Example OPTIONS and processors are provided with this procedure. However, if you would like to know more about the use of OPTIONS in an Endevor processor, see this doc.

With this procedure, sample processor code is provided in the form of "Includes". Endevor optionally supports either a Panvalet include ("++INCLUDE"), or a Librarian include ("-INC"). If you are not using either, then just copy the sample "Include" code into the processors where you need them. If you are using the Panvalet include, then change the "-INC" references to "++INCLUDE" references (starting in column 8).

Options provide the details for the Automated Test Facility for Batch Applications. Two categories of OPTIONS are a part of this procedure.

  • Options for your existing elements (Cobol for example) that specify one or more automated tests to be triggered.
  • Options for your JCL elements that specify how to tailor, run and evaluate a test.

Setup steps for the Automated Test Facility for Batch Applications:

  1. Prepare your existing processors to recognize OPTIONS that request automated tests. This step addresses your existing Generate and/or Move processors:

    a) A fetch for the element's options is necessary. If you do not already have one, then copy (or include) the content of GET#OPTE into your existing processor(s).

    b) Copy or Include the content of AUTOTEST into your processor(s), placed after the fetch.

  2. Copy TEST#JOB into a REXX library that will be accessed by your processors.

  3. Prepare the JCL (or other element type) processor(s).

    a) Install GTESTING as an Endevor processor. Optionally, you may copy GTESTING into an existing processor. Tailor the top of the processor to specify values applicable to your site. Be sure to name the library where you placed the TEST#JOB Rexx module. Also, consider the value given to the* RESLTHLQ processor variable. This value names the High Level Qualifier for datasets where job outputs are captured. You can use the C1USERID processor, if you prefer. The Rexx driver, TEST#JOB, creates datasets prefixed with RESLTHLQ and with additional nodes for C1Stage, date and Job number.

    b) Define the use of your processor to the Endevor Environments, stages, systems, types and processor groups where you need to support Automated Testing.

  4. Prepare the OPTIONS that drive Automated Testing. For example, if you have a batch COBOL program COBA that runs in a JCL element, JOBA, then you will need OPTIONS for both.

    a) Build OPTIONS for your existing elements. Prepare OPTIONS for triggering automated tests, using the provided Example COBOL element OPTIONS.

    b) Build OPTIONS for your JCL (or other element type). Use the provided Example JCL element OPTIONS, where an example is given for every variation of supported syntax. Note that there are several kinds of OPTIONS statements for JCL: - Search and Replace pairs - Others that optionally specify values for waiting and comparing

    Note:

    The provided OPTIONS specify the Endevor C1STAGE, where Automated Testing is to occur. You can modify it to meet your needs, including using C1ENVMNT or C1SUBSYS to provide Automated Testing for Deploy to Test actions.

Note: Members OPTVALDT, TXTRPLCE, JCLRPLCE and YAML2REX are REXX subroutines required for the Automated Test Facility for Batch Applications. They are used by more than one solution on this GitHub, but can be found under the Field-Developed-Programs folder in the Processor-Tools-and-Processor-Snippets subfolder.