3.2.5. Request Unit Test (Batch Process)¶

3.2.5.1.1. Overall picture¶

3.2.5.3.1. StandaloneTestSupportTemplate¶

Provides a test execution environment for batch, messaging, and other processes that run outside the container. Reads test data and executes all test shots (TestShot ).

3.2.5.3.2. TestShot¶

Executes by holding information of 1 TestShot. The TestShot consists of the following elements:

• Preparation of input data
• Launch the main class
• Confirm the output results

Provides common preparation process and result checking functions for testing processes that operate outside of containers, such as batch and messaging processes.

Preparation process	Confirmation of results
Database setup	Check for database updates
	Check log output results
	Confirm the status code

Since the input data preparation and result confirmation logic is different for each batch and various messaging processes, it can be customized according to the architecture.

3.2.5.3.3. BatchRequestTestSupport¶

Superclass for batch process tests. The application programmer creates a test class by inheriting this class.

This class adds the following functions to the preparation process and result confirmation provided by TestShot .

Preparation process	Confirmation of results
Prepare input file	Check the contents of the output file

By using this class, the test source and test data of the request unit test can be standardized, and description of test source can be significantly reduced.

For the specific usage method, refer to How to Execute a Request Unit Test (Batch).

3.2.5.3.4. MainForRequestTesting¶

Main class for request unit test. The primary differences from the main class for production are as follows.

• Initialize the system repository from the component configuration file of the test.
• Disable the resident function.

3.2.5.3.5. FileSupport¶

A class that provides operations related to files. Primarily, the following functions are provided.

• Creates an input file from the test data.
• Compares the expected value of the test data with the actual output file and its contents.

File operations are provided as an independent class because they are necessary for other than batch processing (for example, file download).

3.2.5.4.1. Fixed-length file¶

For the basic description, see How to Execute a Request Unit Test (Batch).

3.2.5.4.2. Variable length file¶

For the basic description, see How to Execute a Request Unit Test (Batch).

3.2.5.5.1. Handler configuration of resident batch test¶

When performing a resident batch test, the handler configuration for production has to be changed for the test. If the test is performed without making this change, the test will not be implemented successfully because the process of the resident batch application that is being tested will not finish.

[Handlers that need to be modified]

The configuration example of the component configuration file is shown below.

• Production configuration

  <!-- Request thread loop -->
  <component name="requestThreadLoopHandler" class="nablarch.fw.handler.RequestThreadLoopHandler">
    <!-- Configuration of property is omitted -->
  </component>
  

• Test configuration

  Configure a component with the same name as the production configuration and overwrite it to use a handler for testing.

  <!-- Configuration to replace the request thread loop handler with a handler for testing -->
  <component name="requestThreadLoopHandler" class="nablarch.test.OneShotLoopHandler" />
  

3.2.5.5.2. Default value of directive¶

If the file directives are unified to some extent in the system, it is redundant to describe the same directive in each test data.

In such a case, by describing the default directive in the component configuration file, the directive description can be omitted for each test data.

Use map format for the component configuration file. The naming rules are as follows.

The configuration example is shown below.

<!-- Directive (common) -->
<map name="defaultDirectives">
  <entry key="text-encoding" value="Windows-31J" />
</map>

<!-- Directive (fixed-length) -->
<map name="variableLengthDirectives">
  <entry key="record-separator" value="NONE"/>
</map>

<!-- Directive (variable length) -->
<map name="variableLengthDirectives">
  <entry key="quoting-delimiter" value="" />
  <entry key="record-separator" value="CRLF"/>
</map>