Micro Focus Unit Testing Framework (Known Issues)

The Micro Focus Unit Testing Framework has a number of restrictions on the syntax contained in a test case, and size limits of source data in data-driven tests.

Syntax

The following syntax is not currently supported within a test case:

  • Native OO COBOL code
  • User interface syntax (i.e. anything that requires user interaction throughout the running of the program)

Data-driven tests

There are size limits on some of the elements of the .csv files used for data-driven tests:

Element Size limit (characters)
Header length 62464
Data line length 62464
Note: Within the IDE, only the first 255 characters of each row are displayed when showing the progress of a test.
MFU-DD-VALUE size 255
Override MFU-DD-VALUE size 255-62464 inclusive
Environment variable <=64512

You can circumvent some of these limits by storing long/complex field data in an external file, and then loading it into memory (using MFU_GET_FILE or MFUGETf) before the test is run.

Using the MFUPP Preprocessor

The following restrictions apply when running tests that utilize the MFUPP preprocessor:

  • When testing programs that contain EXEC statements (EXEC SQL), the statement cannot be split over multiple lines; for example:
    EXEC
    SQL
    COMMIT
    END-EXEC
  • SQL"IGNORE" does not support the expansion of SQL TYPES , such as:
    • BINARY
    • BLOB
    • BLOB-FILE
    • BLOB-LOCATOR
    • CHAR
    • CHAR-VARYING
    • CLOB
    • CLOB-FILE
    • DATE
    • DATE-RECORD
    • DBCLOB
    • DBCLOB-FILE
    • DBCLOB-LOCATOR
    • LONG-VARBINARY
    • LONG-VARCHAR
    • ROWID
    • TIME
    • TIME-RECORD
    • TIMESTAMP
    • TIMESTAMP-RECORD
    • TIMESTAMP-OFFSET
    • TIMESTAMP-OFFSET-RECORD
    • VARBINARY
    • XML
  • The preprocessor does not honor the SOURCE-ENCODING directive.

.NET 8 support

.NET 8 support on Windows and UNIX/Linux platforms is 64-bit only.