Testing Applications › Testing Systems in the HE Environment › Test a Load Module or Application

Test a Load Module or Application

The following is a summary of a typical sequence of activities to build and test an executable load module, and test an application system.

Follow these steps:

1. Specify the libraries in which the CA Gen stores the generated objects and the external libraries that are used during construction.
2. Specify the target environment.
3. Specify the load module packaging.
4. Check the load module components for consistency.
5. Generate the load modules.

   Because this activity generates the source code, set the Generate Debug Support option to Yes when generating load modules that you test using the Debug Trace Facility.

6. Install the load modules in the testing environment.

   This activity compiles, link-edits, and binds the generated source code, resolving external references.

7. Test the application transactions.
8. Review the results of the test process.

   To correct errors, change toolset diagrams, not generated code.

9. Regenerate and reinstall selected components that are based on the changes to the diagrams.
10. Repeat the steps, beginning with generating the load modules, until the load modules are debugged.

    Note: As testing continues, generate components that have been fully tested (or are not a critical part of the test) without the debug support option.

11. When the application or load module is fully tested, use the system generation tools to generate (without Debug Support) and install the application in the target production environment.

Update your construction library specifications to reflect the production environment rather than the testing environment.