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 and test developer and test setups for FreeBSD.

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.

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

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

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

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

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

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.

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

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

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.

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

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

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

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

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

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.

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

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

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

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

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

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

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.

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

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 developer and user setups for Apple Mac OS X.

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.

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.

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

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

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

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

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

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

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.

Want to upload a graphic of the test automation pyramid.

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

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

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

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.

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

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

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.