COBOL Tutorial

COBOL TEST - Quick Reference

Progress0 of 0 lessons

Overview

The TEST feature in COBOL provides comprehensive testing capabilities for validating conditions, testing data, and performing program testing. It enables programs to implement thorough testing scenarios, data validation, and debugging operations.

Purpose and Usage

Condition testing - Test various conditions and expressions
Data validation - Validate data integrity and format
Program testing - Test program logic and flow
Debugging operations - Debug program execution and data
Quality assurance - Ensure program quality and reliability

TEST vs Standard IF Statements

Standard IF: Basic condition testing

TEST: Comprehensive testing and debugging

Result: Enhanced testing capabilities

TEST provides comprehensive testing capabilities beyond basic condition checking.

Syntax and Usage

TEST operations are implemented in the PROCEDURE DIVISION using specialized constructs for testing conditions, validating data, and performing debugging operations.

Basic TEST Syntax

cobol

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
* Basic TEST syntax examples
       PROCEDURE DIVISION.
       
       * Test data validation
       TEST DATA-IS-VALID
           IF VALIDATION-STATUS = 'PASS'
               PERFORM PROCESS-DATA
           ELSE
               PERFORM HANDLE-INVALID-DATA
           END-IF
       
       * Test condition evaluation
       TEST CONDITION-MET
           IF TEST-RESULT = 'TRUE'
               PERFORM SUCCESS-ACTION
           ELSE
               PERFORM FAILURE-ACTION
           END-IF
       
       * Test program flow
       TEST PROGRAM-LOGIC
           IF LOGIC-TEST = 'CORRECT'
               CONTINUE
           ELSE
               PERFORM DEBUG-PROGRAM
           END-IF
       
       * Test error conditions
       TEST ERROR-CONDITION
           IF ERROR-STATUS = 'ACTIVE'
               PERFORM ERROR-HANDLING
           END-IF

Basic TEST operations for condition testing and validation.

Complete TEST Program Example

cobol

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
* Complete COBOL program demonstrating TEST usage
       IDENTIFICATION DIVISION.
       PROGRAM-ID. TEST-DEMO.
       
       ENVIRONMENT DIVISION.
       CONFIGURATION SECTION.
       
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01  TEST-DATA.
           05  INPUT-VALUE    PIC 9(6).
           05  EXPECTED-RESULT PIC 9(6).
           05  ACTUAL-RESULT  PIC 9(6).
       
       01  TEST-STATUS.
           05  VALIDATION-STATUS PIC X(10).
           05  TEST-RESULT      PIC X(10).
           05  ERROR-STATUS     PIC X(10).
       
       01  TEST-COUNTERS.
           05  TESTS-PASSED    PIC 9(3).
           05  TESTS-FAILED    PIC 9(3).
           05  TOTAL-TESTS     PIC 9(3).
       
       PROCEDURE DIVISION.
       MAIN-LOGIC.
           PERFORM INITIALIZE-TESTING
           PERFORM RUN-TEST-SUITE
           PERFORM DISPLAY-TEST-RESULTS
           STOP RUN.
       
       INITIALIZE-TESTING.
           MOVE ZERO TO TESTS-PASSED
           MOVE ZERO TO TESTS-FAILED
           MOVE ZERO TO TOTAL-TESTS.
       
       RUN-TEST-SUITE.
           * Test 1: Data validation
           PERFORM TEST-DATA-VALIDATION
           
           * Test 2: Arithmetic operations
           PERFORM TEST-ARITHMETIC-OPERATIONS
           
           * Test 3: Error conditions
           PERFORM TEST-ERROR-CONDITIONS
           
           * Test 4: Program logic
           PERFORM TEST-PROGRAM-LOGIC.
       
       TEST-DATA-VALIDATION.
           ADD 1 TO TOTAL-TESTS
           MOVE 123456 TO INPUT-VALUE
           
           * Test if input is within valid range
           IF INPUT-VALUE > 0 AND INPUT-VALUE < 999999
               MOVE 'PASS' TO VALIDATION-STATUS
               ADD 1 TO TESTS-PASSED
           ELSE
               MOVE 'FAIL' TO VALIDATION-STATUS
               ADD 1 TO TESTS-FAILED
           END-IF
           
           DISPLAY "Data Validation Test: " VALIDATION-STATUS.
       
       TEST-ARITHMETIC-OPERATIONS.
           ADD 1 TO TOTAL-TESTS
           MOVE 100 TO INPUT-VALUE
           MOVE 200 TO EXPECTED-RESULT
           
           * Test arithmetic operation
           COMPUTE ACTUAL-RESULT = INPUT-VALUE * 2
           
           IF ACTUAL-RESULT = EXPECTED-RESULT
               MOVE 'PASS' TO TEST-RESULT
               ADD 1 TO TESTS-PASSED
           ELSE
               MOVE 'FAIL' TO TEST-RESULT
               ADD 1 TO TESTS-FAILED
           END-IF
           
           DISPLAY "Arithmetic Test: " TEST-RESULT.
       
       TEST-ERROR-CONDITIONS.
           ADD 1 TO TOTAL-TESTS
           
           * Test error handling
           IF ERROR-STATUS = 'ACTIVE'
               MOVE 'FAIL' TO TEST-RESULT
               ADD 1 TO TESTS-FAILED
           ELSE
               MOVE 'PASS' TO TEST-RESULT
               ADD 1 TO TESTS-PASSED
           END-IF
           
           DISPLAY "Error Condition Test: " TEST-RESULT.
       
       TEST-PROGRAM-LOGIC.
           ADD 1 TO TOTAL-TESTS
           
           * Test program logic flow
           IF TESTS-PASSED > 0
               MOVE 'PASS' TO TEST-RESULT
               ADD 1 TO TESTS-PASSED
           ELSE
               MOVE 'FAIL' TO TEST-RESULT
               ADD 1 TO TESTS-FAILED
           END-IF
           
           DISPLAY "Program Logic Test: " TEST-RESULT.
       
       DISPLAY-TEST-RESULTS.
           DISPLAY "=== TEST RESULTS ==="
           DISPLAY "Total Tests: " TOTAL-TESTS
           DISPLAY "Tests Passed: " TESTS-PASSED
           DISPLAY "Tests Failed: " TESTS-FAILED
           
           IF TESTS-FAILED = 0
               DISPLAY "All tests passed successfully!"
           ELSE
               DISPLAY "Some tests failed. Review required."
           END-IF.

The program demonstrates comprehensive testing capabilities.

Advanced TEST Usage

cobol

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
* Advanced TEST usage with debugging and validation
       PROCEDURE DIVISION.
       
       ADVANCED-TESTING-OPERATIONS.
           PERFORM SETUP-TEST-ENVIRONMENT
           PERFORM EXECUTE-TEST-SUITE
           PERFORM ANALYZE-TEST-RESULTS
           PERFORM CLEANUP-TEST-ENVIRONMENT.
       
       SETUP-TEST-ENVIRONMENT.
           * Initialize test environment
           MOVE 'READY' TO TEST-STATUS
           DISPLAY "Test environment initialized".
       
       EXECUTE-TEST-SUITE.
           * Execute comprehensive test suite
           PERFORM TEST-DATA-INTEGRITY
           PERFORM TEST-BUSINESS-LOGIC
           PERFORM TEST-PERFORMANCE
           PERFORM TEST-ERROR-HANDLING.
       
       TEST-DATA-INTEGRITY.
           * Test data integrity and consistency
           IF DATA-IS-CONSISTENT
               MOVE 'PASS' TO TEST-RESULT
               DISPLAY "Data integrity test: PASSED"
           ELSE
               MOVE 'FAIL' TO TEST-RESULT
               DISPLAY "Data integrity test: FAILED"
               PERFORM LOG-DATA-ERROR
           END-IF.
       
       TEST-BUSINESS-LOGIC.
           * Test business logic and rules
           IF BUSINESS-RULES-VALID
               MOVE 'PASS' TO TEST-RESULT
               DISPLAY "Business logic test: PASSED"
           ELSE
               MOVE 'FAIL' TO TEST-RESULT
               DISPLAY "Business logic test: FAILED"
               PERFORM LOG-BUSINESS-ERROR
           END-IF.
       
       TEST-PERFORMANCE.
           * Test performance and efficiency
           IF PERFORMANCE-ACCEPTABLE
               MOVE 'PASS' TO TEST-RESULT
               DISPLAY "Performance test: PASSED"
           ELSE
               MOVE 'FAIL' TO TEST-RESULT
               DISPLAY "Performance test: FAILED"
               PERFORM LOG-PERFORMANCE-ERROR
           END-IF.
       
       TEST-ERROR-HANDLING.
           * Test error handling and recovery
           IF ERROR-HANDLING-WORKS
               MOVE 'PASS' TO TEST-RESULT
               DISPLAY "Error handling test: PASSED"
           ELSE
               MOVE 'FAIL' TO TEST-RESULT
               DISPLAY "Error handling test: FAILED"
               PERFORM LOG-ERROR-HANDLING-ERROR
           END-IF.

Advanced TEST usage with comprehensive testing and debugging.

Common Use Cases

TEST is essential in various scenarios where comprehensive testing, data validation, and quality assurance are required.

Data Validation Testing

cobol

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
* Data validation testing using TEST
       IDENTIFICATION DIVISION.
       PROGRAM-ID. DATA-VALIDATION-TEST.
       
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01  TEST-DATA.
           05  CUSTOMER-ID     PIC 9(6).
           05  CUSTOMER-NAME   PIC X(30).
           05  CUSTOMER-AGE    PIC 9(3).
           05  CUSTOMER-EMAIL  PIC X(50).
       
       01  VALIDATION-RESULTS.
           05  ID-VALID        PIC X.
           05  NAME-VALID      PIC X.
           05  AGE-VALID       PIC X.
           05  EMAIL-VALID     PIC X.
       
       PROCEDURE DIVISION.
       MAIN-LOGIC.
           PERFORM TEST-CUSTOMER-ID
           PERFORM TEST-CUSTOMER-NAME
           PERFORM TEST-CUSTOMER-AGE
           PERFORM TEST-CUSTOMER-EMAIL
           PERFORM DISPLAY-VALIDATION-RESULTS
           STOP RUN.
       
       TEST-CUSTOMER-ID.
           * Test customer ID validation
           IF CUSTOMER-ID > 0 AND CUSTOMER-ID < 999999
               MOVE 'Y' TO ID-VALID
               DISPLAY "Customer ID validation: PASSED"
           ELSE
               MOVE 'N' TO ID-VALID
               DISPLAY "Customer ID validation: FAILED"
           END-IF.
       
       TEST-CUSTOMER-NAME.
           * Test customer name validation
           IF CUSTOMER-NAME NOT = SPACES AND
              CUSTOMER-NAME NOT = LOW-VALUES
               MOVE 'Y' TO NAME-VALID
               DISPLAY "Customer name validation: PASSED"
           ELSE
               MOVE 'N' TO NAME-VALID
               DISPLAY "Customer name validation: FAILED"
           END-IF.
       
       TEST-CUSTOMER-AGE.
           * Test customer age validation
           IF CUSTOMER-AGE >= 18 AND CUSTOMER-AGE <= 120
               MOVE 'Y' TO AGE-VALID
               DISPLAY "Customer age validation: PASSED"
           ELSE
               MOVE 'N' TO AGE-VALID
               DISPLAY "Customer age validation: FAILED"
           END-IF.
       
       TEST-CUSTOMER-EMAIL.
           * Test customer email validation
           IF CUSTOMER-EMAIL CONTAINS '@' AND
              CUSTOMER-EMAIL CONTAINS '.'
               MOVE 'Y' TO EMAIL-VALID
               DISPLAY "Customer email validation: PASSED"
           ELSE
               MOVE 'N' TO EMAIL-VALID
               DISPLAY "Customer email validation: FAILED"
           END-IF.
       
       DISPLAY-VALIDATION-RESULTS.
           DISPLAY "=== VALIDATION RESULTS ==="
           DISPLAY "ID Valid: " ID-VALID
           DISPLAY "Name Valid: " NAME-VALID
           DISPLAY "Age Valid: " AGE-VALID
           DISPLAY "Email Valid: " EMAIL-VALID.

Data validation testing ensures data integrity and quality.

Program Logic Testing

cobol

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
* Program logic testing using TEST
       IDENTIFICATION DIVISION.
       PROGRAM-ID. LOGIC-TESTING.
       
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01  TEST-SCENARIOS.
           05  SCENARIO-1      PIC X(20) VALUE "Normal Processing".
           05  SCENARIO-2      PIC X(20) VALUE "Error Handling".
           05  SCENARIO-3      PIC X(20) VALUE "Boundary Testing".
       
       01  TEST-RESULTS.
           05  SCENARIO-1-RESULT PIC X(10).
           05  SCENARIO-2-RESULT PIC X(10).
           05  SCENARIO-3-RESULT PIC X(10).
       
       01  TEST-DATA.
           05  INPUT-VALUE     PIC 9(6).
           05  EXPECTED-OUTPUT PIC 9(6).
           05  ACTUAL-OUTPUT   PIC 9(6).
       
       PROCEDURE DIVISION.
       MAIN-LOGIC.
           PERFORM TEST-NORMAL-PROCESSING
           PERFORM TEST-ERROR-HANDLING
           PERFORM TEST-BOUNDARY-CONDITIONS
           PERFORM DISPLAY-LOGIC-TEST-RESULTS
           STOP RUN.
       
       TEST-NORMAL-PROCESSING.
           * Test normal processing scenario
           MOVE 100 TO INPUT-VALUE
           MOVE 200 TO EXPECTED-OUTPUT
           
           * Simulate normal processing
           COMPUTE ACTUAL-OUTPUT = INPUT-VALUE * 2
           
           IF ACTUAL-OUTPUT = EXPECTED-OUTPUT
               MOVE 'PASS' TO SCENARIO-1-RESULT
               DISPLAY "Normal processing test: PASSED"
           ELSE
               MOVE 'FAIL' TO SCENARIO-1-RESULT
               DISPLAY "Normal processing test: FAILED"
           END-IF.
       
       TEST-ERROR-HANDLING.
           * Test error handling scenario
           MOVE 0 TO INPUT-VALUE
           
           * Simulate error condition
           IF INPUT-VALUE = 0
               MOVE 'PASS' TO SCENARIO-2-RESULT
               DISPLAY "Error handling test: PASSED"
           ELSE
               MOVE 'FAIL' TO SCENARIO-2-RESULT
               DISPLAY "Error handling test: FAILED"
           END-IF.
       
       TEST-BOUNDARY-CONDITIONS.
           * Test boundary conditions
           MOVE 999999 TO INPUT-VALUE
           
           * Test maximum value handling
           IF INPUT-VALUE = 999999
               MOVE 'PASS' TO SCENARIO-3-RESULT
               DISPLAY "Boundary condition test: PASSED"
           ELSE
               MOVE 'FAIL' TO SCENARIO-3-RESULT
               DISPLAY "Boundary condition test: FAILED"
           END-IF.
       
       DISPLAY-LOGIC-TEST-RESULTS.
           DISPLAY "=== LOGIC TEST RESULTS ==="
           DISPLAY SCENARIO-1 ": " SCENARIO-1-RESULT
           DISPLAY SCENARIO-2 ": " SCENARIO-2-RESULT
           DISPLAY SCENARIO-3 ": " SCENARIO-3-RESULT.

Program logic testing validates program flow and decision making.

Performance Testing

cobol

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
* Performance testing using TEST
       IDENTIFICATION DIVISION.
       PROGRAM-ID. PERFORMANCE-TEST.
       
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01  PERFORMANCE-METRICS.
           05  START-TIME      PIC 9(10).
           05  END-TIME        PIC 9(10).
           05  EXECUTION-TIME  PIC 9(10).
           05  MEMORY-USAGE    PIC 9(10).
       
       01  PERFORMANCE-THRESHOLDS.
           05  MAX-EXECUTION-TIME PIC 9(10) VALUE 5000.
           05  MAX-MEMORY-USAGE   PIC 9(10) VALUE 1000000.
       
       01  PERFORMANCE-RESULTS.
           05  TIME-TEST-RESULT    PIC X(10).
           05  MEMORY-TEST-RESULT  PIC X(10).
       
       PROCEDURE DIVISION.
       MAIN-LOGIC.
           PERFORM MEASURE-PERFORMANCE
           PERFORM ANALYZE-PERFORMANCE
           PERFORM DISPLAY-PERFORMANCE-RESULTS
           STOP RUN.
       
       MEASURE-PERFORMANCE.
           * Record start time
           MOVE FUNCTION CURRENT-DATE TO START-TIME
           
           * Execute performance test
           PERFORM EXECUTE-PERFORMANCE-TEST
           
           * Record end time
           MOVE FUNCTION CURRENT-DATE TO END-TIME
           
           * Calculate execution time
           COMPUTE EXECUTION-TIME = END-TIME - START-TIME.
       
       EXECUTE-PERFORMANCE-TEST.
           * Simulate intensive processing
           PERFORM VARYING I FROM 1 BY 1 UNTIL I > 10000
               COMPUTE MEMORY-USAGE = MEMORY-USAGE + 1
           END-PERFORM.
       
       ANALYZE-PERFORMANCE.
           * Test execution time
           IF EXECUTION-TIME <= MAX-EXECUTION-TIME
               MOVE 'PASS' TO TIME-TEST-RESULT
               DISPLAY "Execution time test: PASSED"
           ELSE
               MOVE 'FAIL' TO TIME-TEST-RESULT
               DISPLAY "Execution time test: FAILED"
           END-IF
           
           * Test memory usage
           IF MEMORY-USAGE <= MAX-MEMORY-USAGE
               MOVE 'PASS' TO MEMORY-TEST-RESULT
               DISPLAY "Memory usage test: PASSED"
           ELSE
               MOVE 'FAIL' TO MEMORY-TEST-RESULT
               DISPLAY "Memory usage test: FAILED"
           END-IF.
       
       DISPLAY-PERFORMANCE-RESULTS.
           DISPLAY "=== PERFORMANCE TEST RESULTS ==="
           DISPLAY "Execution Time: " EXECUTION-TIME " ms"
           DISPLAY "Memory Usage: " MEMORY-USAGE " bytes"
           DISPLAY "Time Test: " TIME-TEST-RESULT
           DISPLAY "Memory Test: " MEMORY-TEST-RESULT.

Performance testing ensures program efficiency and resource usage.

Best Practices and Tips

Following these best practices ensures effective use of TEST in COBOL applications for better quality assurance and reliability.

TEST Best Practices

Design comprehensive test scenarios - Cover all program paths and conditions
Implement systematic testing procedures - Create organized testing workflows
Test both normal and error conditions - Ensure robust error handling
Document test results and procedures - Maintain clear testing documentation
Validate data integrity thoroughly - Test all data validation rules
Test performance and efficiency - Ensure optimal program performance

Testing Categories

Category	Purpose	Examples
Unit Testing	Test individual program components	Data validation, calculations
Integration Testing	Test component interactions	File operations, database access
System Testing	Test complete program functionality	End-to-end workflows
Performance Testing	Test efficiency and resource usage	Execution time, memory usage
Error Testing	Test error handling and recovery	Exception handling, error conditions
Regression Testing	Test for unintended side effects	Previous functionality verification

Quality Assurance Considerations

Test coverage - Ensure all code paths are tested
Automated testing - Implement repeatable test procedures
Test data management - Use appropriate test data sets
Environment consistency - Maintain consistent testing environments
Result analysis - Analyze test results systematically
Continuous improvement - Refine testing procedures based on results

TEST Quick Reference

Aspect	Description	Example
Location	PROCEDURE DIVISION	In testing and validation logic
Condition Testing	Test various conditions and expressions	IF TEST-CONDITION = 'TRUE'
Data Validation	Validate data integrity and format	IF DATA-IS-VALID
Error Testing	Test error conditions and handling	IF ERROR-STATUS = 'ACTIVE'
Performance Testing	Test efficiency and resource usage	IF PERFORMANCE-ACCEPTABLE

Test Your Knowledge

1. What is the primary purpose of TEST in COBOL?

To define arithmetic operations
To test conditions, validate data, and perform program testing
To control file operations
To define data types

2. Where is TEST typically used in a COBOL program?

In the DATA DIVISION for test data definitions
In the PROCEDURE DIVISION for testing conditions and validation
In the ENVIRONMENT DIVISION for system configuration
In the IDENTIFICATION DIVISION

3. What types of operations can TEST handle?

Only file operations
Only database operations
Condition testing, data validation, program testing, and debugging operations
Only mathematical calculations

4. How does TEST differ from standard IF statements?

They are identical in function
TEST provides more comprehensive testing capabilities and debugging features
TEST only works with numeric data
Standard IF statements are more advanced than TEST

5. Which of the following is a common use of TEST?

File sorting operations
Data validation, condition testing, program debugging, and testing scenarios
Database operations
Mathematical calculations

COBOL Tutorial

COBOL TEST - Quick Reference

Overview

Purpose and Usage

TEST vs Standard IF Statements

Syntax and Usage

Basic TEST Syntax

Complete TEST Program Example

Advanced TEST Usage

Common Use Cases

Data Validation Testing

Program Logic Testing

Performance Testing

Best Practices and Tips

TEST Best Practices

Testing Categories

Quality Assurance Considerations

TEST Quick Reference

Test Your Knowledge

Frequently Asked Questions

Related Concepts

Data Validation

Error Handling

Debugging Techniques

Program Quality

Testing Methodologies

Related Pages

COBOL Tutorial

COBOL TEST - Quick Reference

Overview

Purpose and Usage

TEST vs Standard IF Statements

Syntax and Usage

Basic TEST Syntax

Complete TEST Program Example

Advanced TEST Usage

Common Use Cases

Data Validation Testing

Program Logic Testing

Performance Testing

Best Practices and Tips

TEST Best Practices

Testing Categories

Quality Assurance Considerations

TEST Quick Reference

Test Your Knowledge

Frequently Asked Questions

What is TEST and how is it used in COBOL?

What are the main TEST operations available in COBOL?

How do you implement TEST in COBOL programs?

What are the best practices for using TEST in COBOL programs?

How does TEST support program quality and reliability?

Related Concepts

Data Validation

Error Handling

Debugging Techniques

Program Quality

Testing Methodologies

Related Pages