openmainframeproject/cobol-check

A testing framework for Cobol applications

cobol-check's Issues

Perform common setup prior to each test case in a suite

This is a re-implementation of proof of concept functionality. No change in design.

Execute each test program after it has been generated (Linux)

After the Generator produces a test program, execute it by launching an OS process. Linux non-z/OS only.

Setup project structure on Linux

Set up project directories and a Gradle build to begin development.

Stub a paragraph

Stub a paragraph on which the paragraph under test depends. This is a re-implementation of proof of concept functionality.

Create and test z/OS developer and test setups

Create and test developer and test setups for z/OS and write the documentation. This will require help from external supporters of the project who can provide access to a z/OS system.

Create and test Mac OS X developer and test setups

Create and test developer and user setups for Apple Mac OS X.

Mock a CALL statement and provide fake results

Mock a CALL statement on which the code under test depends and substitute fake return values. This is a re-implementation of proof of concept functionality.

Mock or stub a CICS resource and provide fake results

This is a re-implementation of proof of concept functionality that will be designed differently. The proof of concept mocks specific EXEC CICS commands. The new implementation will mock or stub the CICS resource, and allow substitute results, EIBRESP/EIBRESP2 codes, and conditions for the test case.

Complete the Developer Certificate of Origin requiremens for the Open Mainframe Project

https://github.com/openmainframeproject/tac/blob/master/process/contribution_guidelines.md

Mock a batch file READ and provide a fake record

Stub access to a file in batch mode and populate Data Division items with values for the test case. This is a re-implementation of proof of concept functionality that involves minor redesign of the solution.

Mock a batch file OPEN and provide a fake status code

Stub accesses to a file in batch mode and provide a fake status code following the OPEN statement. This is a re-implementation of proof of concept functionality.

Expand copybooks

Optionally expand copybooks, with support for nested COPY statements and COPY REPLACING. This functionality was not included in the proof of concept but it is necessary in some circumstances. We consider it part of the initial functionality.

Create Committers csv file to comply with Open Mainframe Project template

See https://github.com/openmainframeproject/project-template

Generate unique test program for each program under test in the same run

Cobol-check allows the user to specify multiple programs to test in a single run, but only produces a single test program to execute the test suites. Instead, each program under test needs to have a separate test program produced.

Apply to the Open Mainframe Project

Work with John Mertic, who reached out to express interest in the project, who has offered to shepherd us through the application process.

Create and test FreeBSD developer and test setups

Create and test developer and test setups for FreeBSD.

Create and test Fedora-style Linux developer and test setups

Create and test developer and user setups for Fedora Linux (using yum) and write the documentation.

Messages not honoring change in Locale

Changing the Locale after starting Cobol Check has no effect. Messages continue to be emitted in the Locale that was set as default at the time the program started.

Create email account for Cobol Check

Mock or stub a SQL resource and provide fake results

This functionality was not supported in the proof of concept but was always in plan. We consider it part of the initial re-implementation.

Support parameterized test cases

This functionality was not included in the proof of concept but was always in plan. We consider it fundamental and include it in the re-implementation milestone.

Execute a paragraph in isolation

Add support for running a single paragraph in a Cobol program. This is a re-implementation of proof of concept functionality.

Add support to assert 88-level values

EXPECT statements should be able to assert true/false results for 88-level items.

Add license comment to the top of all source files per Open Mainframe Project guidelines

https://github.com/openmainframeproject/tac/blob/master/process/contribution_guidelines.md

Fake issue to enable upload of an image

Want to upload a graphic of the test automation pyramid.

Add required sections to the Readme to comply with the Open Mainframe Project template

https://github.com/openmainframeproject/project-template

Mock a paragraph and provide fake results

Mock a paragraph/section on which the paragraph/section under test depends and substitute Cobol statements for it.

Test a paragraph in isolation

Set preconditions (Data Division item values), execute paragraph in isolation, check postconditions (Data Division item values). This is a re-implementation of proof of concept functionality.

Create and test Windows developer and user setups

Create and test setups on Windows 10 and write the documentation.

Set up static code analysis

Set up support for static code analysis. Try Sonarcloud first. If that isn't suitable, find another solution.

Project documentation

Start creating project documentation and establish a reasonable structure for it. Use the project wiki on Github for this.

Create project forum

Sset up a form (probably Google forums) for community interaction.

Create Support file to comply with the Open Mainframe Project template

https://github.com/openmainframeproject/project-template

GetOpt can throw NullPointerException if no command-line options are specified

Create Twitter account for Cobol Check

Change Code of Conduct to comply with Open Mainframe Project template

See https://github.com/openmainframeproject/project-template

Fake issue to upload an image.

Create Governance doc to comply with the Open Mainframe Project template

https://github.com/openmainframeproject/project-template

Add support to assert a numeric result

EXPECT statements should support numeric "actual" results (numeric literals in the test case).

Switch to Apache License 2.0 to comply with Open Mainframe Project guidelines

https://github.com/openmainframeproject/project-template

Move "how to contribute" info to Contributing doc per Open Mainframe Project template

https://github.com/openmainframeproject/project-template

Log messages should include current timestamp

Log messages do not indicate the timestamp when they were written.

Add Changelog file to comply with Open Mainframe Project template

See https://github.com/openmainframeproject/project-template

Perform one-time setup at the start of a test suite

We want to be able to do a one time setup, before a test suite is run.
This is the implementation of the BEFORE-ALL keyword and functionality.
Unlike BEFORE-EACH, which runs before every testcase, BEFORE-EACH, should only run once.

Create Security file to comply with the Open Mainframe Project template

https://github.com/openmainframeproject/project-template

Create Third Party file to comply with the Open Mainframe Project template

https://github.com/openmainframeproject/project-template

Continuous integration support

Set up CI for the project. Look for suitable online service for this, such as Travis or Circle.

Add command-line option to display the current version of cobol-check

Configure two-factor authentication per Open Mainframe Project guidelines

See https://github.com/openmainframeproject/tac/blob/master/process/contribution_guidelines.md

Count the number of times a mock was accessed

Mocks usually track the number of times they are accessed. We want mocks in cobol-check to do the same. This is a re-implementation of proof of concept functionality.