Action Required Dialogs

Depending on the selected Xpediter debug session you may encounter one of the following pop-ups:

• Scripts Warning pop-up
  If your launch configuration uses scripts, Total Test displays the following dialog box as the Background process is limited to the SET ABBREV ON command. Other script commands may result in unpredictable results when continuing. Click Yes to continue, No to cancel the request.

• CICS Wait user input pop-up
  This pop-up appears during background recording, when the recording is waiting for the user to entered the CICS transaction associated with the launch.

• IMS Wait user input pop-up
  This pop-up appears during background recording, when the recording is waiting for the user to entered the IMS transaction associated with the launch.

Record Test Case from an Xpediter/Eclipse Debugging Session

When developers need to test any COBOL program behavior changes, they would initiate an Xpediter debug session to generate a test and validate their change.

1. Restart debugging the program in Xpediter which stops at the main program entry.
2. Find the sub-program for which to collect test data.
3. Right-click and select Record Test Case… on the Procedure section of the program on which to collect data. For more details, see Context-Menus-from-Xpediter-Debug-Session.
4. In the Record Test Case dialog window's General tab, select an existing project or create a new project.
   
5. Select the project from the Project drop-down or create a new one using the NEW button.
6. Select a test folder from the Folder drop-down or enter a new folder name.
7. In the Scenario drop-down, the last scenario specified for this program is pre-selected. Otherwise, a new scenario is displayed, using the name of the program with the suffix _Scenario (<program>_Scenario), for example, CWKTVSKS_Scenario.
8. Optionally, you may specify the project's test suite into which the generated test scenario will be copied.

9. Select which test to generate, either Unit Test (Virtualized Test, default), Functional Test (Non-virtualized Test), or both.

   Warning

   Important

   The Functional Test selection is only available when using a Repository Server (Window > Preferences > Compuware > Topaz for Total Test > Repository Server with check box Use repository server.)

10. If you selected Functional Test, select the Host connection from the Functional Test Environment drop-down list. Use the Configure button to add or modify a connection.

    Warning

    Important

    The Unit Test Options tab includes fields and settings specific for generating Virtualized Test test cases. For detailed descriptions, see Context-Menus-from-Xpediter-Debug-Session.

11. Click OK to create the test case.
12. If so desired, use the Xpediter session to change variable values at this point.
13. Issue the appropriate Run commands in your Xpediter debug session. Xpediter collects and saves the program entry data from the structure specified by the Using Statements.
14. Xpediter continues executing the rest of the program. For a Data Stub to be created, at least one Read or one Write must be executed in Xpediter during data collection. When the program ends or is stopped, Xpediter transfers the collected data to Topaz for Total Test.
15. The new Test Scenarios appear in the Test Project previously specified. Select the new Test Scenario(s) in the Test Project Explorer View. Topaz for Total Test populates the project folders with the transferred data.

Scenarios Folder:

Test Scenarios:

• Non-virtualized Test test case (<program>.scenario)
  This is the generated Non-virtualized Test that you can execute using the Extending-the-Execution-Context.
• Virtualized Test test case (<program>_Scenaritestscenario)
  This is the generated Virtualized Test that you can execute using the Execution Context Dialog or the classic Virtualized Test Run Test Dialog.
• Context file (<scenario_name>.context)
  
  
  

Verify that the Repository Server was updated with the information from the generated Total Test Scenario

Before executing the Non-virtualized Test and Virtualized Test test scenarios with the Execute (Execution Context) dialog box for the first time, verify that the program component information in the Repository and all runtime information found is included in the Repository. If it's not included, enter the program component information, including load libraries, Db2 settings, CICS applid, DD statements, manually.

1. Follow the instructions in Working-with-the-Repository and Defining-and-Using-Components to add the program component information to Repository.
2. Refresh the Repository.

Limitations When Generating a Total Test Scenario from Xpediter

• If data value of a field cannot be unhexed, the field will show the hexed value.
• Generation of UTF/DBCS field is not supported in generation.
• Pointer limitations:
  • Can only refer to areas that Program Analyzer can find
  • The pointer can only refer to one structure
  • Expected values for the pointer referenced structure cannot be captured and must be entered manually
• When COBOL “Occurs… depend on” is used in a data structure, the expected value of ODO fields will not be generated due to the limitation of ODO support in non-virtualized testing.
• No functional test is generated for IMS programs.