You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: COBOL Programming Course #4 - Testing/COBOL Programming Course #4 - Testing.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -331,34 +331,34 @@ The difficulty in achieving this has resulted in falling back to manual processe
331
331
332
332
Many organizations have built, or are now building, CI/CD pipelines for their z/OS applications, with considerable success. These teams are looking to test automation to help them achieve an efficient pipeline. This chapter described an approach to test automation on z/OS, by using a framework for automating tests which offers deep integration with z/OS capabilities.
333
333
334
-
# Cobol Check
334
+
# COBOL Check
335
335
336
-
In this chapter, we discuss the concept of unit testing in cobol-programming language with the use of Cobol Check. It delivers precise, fine-grained unit testing/checking capabilities for Cobol, matching the conceptual level of detail found in unit testing frameworks designed for popular languages like Python, Ruby, C#, and Java.
336
+
In this chapter, we discuss the concept of unit testing in COBOL programming language with the use of COBOL Check. It delivers precise, fine-grained unit testing/checking capabilities for COBOL, matching the conceptual level of detail found in unit testing frameworks designed for popular languages like Python, Ruby, C#, and Java.
337
337
338
338
339
-
-**Introduction to Cobol Check**
339
+
-**Introduction to COBOL Check**
340
340
341
-
-**What is Cobol Check?**
342
-
-**Where Can you run Cobol Check?**
343
-
-**How does Cobol Check accomplish unit testing?**
341
+
-**What is COBOL Check?**
342
+
-**Where Can you run COBOL Check?**
343
+
-**How does COBOL Check accomplish unit testing?**
344
344
345
345
346
-
## Introduction to Cobol Check
346
+
## Introduction to COBOL Check
347
347
348
-
### What is Cobol Check?
348
+
### What is COBOL Check?
349
349
350
-
Cobol Check serves as a unit testing framework specifically designed to assist COBOL programmers who encounter challenges with modern development methods like test-driven development. One notable drawback of existing tools for COBOL and other mainframe languages is their limited granularity when it comes to unit testing, especially when compared to languages like Java, C++, and C# etc. However, COBOL Check offers a solution by enabling developers to conduct fine-grained unit testing using both gnuCOBOL and Enterprise COBOL.
350
+
COBOL Check serves as a unit testing framework specifically designed to assist COBOL programmers who encounter challenges with modern development methods like test-driven development. One notable drawback of existing tools for COBOL and other mainframe languages is their limited granularity when it comes to unit testing, especially when compared to languages like Java, C++, and C# etc. However, COBOL Check offers a solution by enabling developers to conduct fine-grained unit testing using both gnuCOBOL and Enterprise COBOL.
351
351
352
352
353
-
### Where Can you run Cobol Check?
353
+
### Where Can you run COBOL Check?
354
354
355
-
Cobol Check strives to facilitate the maintenance and modernization of legacy COBOL applications on IBM zSeries systems. It achieves this by providing developers with the flexibility to work on either the mainframe platform or off-platform environments such as Windows, Unix, Linux, or OS X instances disconnected from the mainframe. By harnessing the advantages of fine-grained "micro test" development at the level of individual Cobol paragraphs.
355
+
COBOL Check strives to facilitate the maintenance and modernization of legacy COBOL applications on IBM zSeries systems. It achieves this by providing developers with the flexibility to work on either the mainframe platform or off-platform environments such as Windows, Unix, Linux, or OS X instances disconnected from the mainframe. By harnessing the advantages of fine-grained "micro test" development at the level of individual COBOL paragraphs.
356
356
357
357
In this chapter, our focus will be on utilizing COBOL Check with Enterprise COBOL on a mainframe environment.
358
358
359
-
## How does Cobol Check accomplish unit testing?
359
+
## How does COBOL Check accomplish unit testing?
360
360
361
-
With cobol-check we can exercise individual cobol-paragraphs in isolation from the rest of the program and without any access to any external resources such as datasets or CICS facilities. Cobol is not designed to do this kind of thing at runtime then how does cobol check accomplish it?
362
-
Developers write test cases using the DSL (domain specific language). The DSL is designed to look similar to cobol-source code so it could be intuitive for cobol-programmers.
363
-
Cobol-check interprets these test cases and converts them into standard cobol statements and merges them with the source of the program under the test. This copy of the program under test which contains test code is then compiled and executed.
364
-
The test code does not run the entire procedure division; instead it only calls the specific paragraphs that are mentioned in the test case.
361
+
With COBOL Check we can exercise individual COBOL paragraphs in isolation from the rest of the program and without any access to any external resources such as datasets or CICS facilities. COBOL is not designed to do this kind of thing at runtime then how does COBOL check accomplish it?
362
+
Developers write test cases using the DSL (domain specific language). The DSL is designed to look similar to COBOL source code, so that it could be intuitive for COBOL programmers.
363
+
COBOL-check interprets these test cases and converts them into standard COBOL statements and merges them with the source of the program under the test. This copy of the program under test which contains test code is then compiled and executed.
364
+
The test code does not run the entire procedure division; instead, it only calls the specific paragraphs that are mentioned in the test case.
0 commit comments