v0.4-alpha

Fourth alpha release of OEMock.

This version is functional, and provides more functionality that v0.3-alpha. It has been run and tested on a live procedural code-base, but has not been tested on more that the most basic coding patterns for classes, and is known to be deficient in some areas. (for example, when identifying class methods on stubbed/mocked objects, overloaded methods are not supported.)

This release has focussed more on the stability of the product working with a large code-base, rather than adding new features.

Known Issues/Limitations

• When identifying class methods in a Stub or Mock object, overloaded methods are not supported.
  • Issue #17 raised for implementation.
• You cannot specify expectations on BUFFER, TABLE or DATASET parameters.
  • Issue #30 raised for fix.

Changes Since Last Release

• Add functionality to automatically compile a test double after it is generated
• Raise a more meaningful error when a syntax error is found in a file being stubbed/mocked.
• Fix error when recording BUFFER, TABLE and DATASET parameter values in a mocked file.
  • These values are no longer recorded and expectations should not be raised on these parameters
  • This will be resolved in a later release (see issue #30)
• Resolve issue when producing a test double on a large source file with the SUBSTITUTE command (error 11311)
• Fix issue with table parameters not being regenerated correctly
• Reduce the amount of options output on a temp-table in a test double to prevent creating a statement longer than maximum allowed value.
• Code generated now uses "~n" as a line ending, rather than CHR(13)
  • This should aid with debugging generated code, but should have no impact during use.
• Missing temp-table definitions in unit tests for OEMock have been added.

v0.3-alpha

Third alpha release of OEMock.

This version is functional, and provides more functionality that v0.2-alpha, but has not been tested on more that the most basic coding patterns, and is known to be deficient in some areas. (for example, when identifying class methods on stubbed/mocked objects, overloaded methods are not supported.)

This release has focussed more on the stability of the product, rather than adding new features.

Known Issues/Limitations

• When identifying class methods in a Stub or Mock object, overloaded methods are not supported.

Changes Since Last Release

• Support for class events
• Issues with failing unit tests resolved
• Code generated now uses CHR(13) as a line ending, not CHR(10) + CHR(13)
  • This should aid with debugging generated code, but should have no impact during use.
• Introduction of CHANGELOG.md, and sections moved from readme.md.

v0.2-alpha

Second alpha release of OEMock.

This version is functional, and provides more functionality that v0.1-alpha, but has not been tested on more that the most basic coding patterns, and is known to be deficient in some areas. (for example, when identifying class methods on stubbed/mocked objects, overloaded methods are not supported..)

Known Issues/Limitations

• When identifying class methods in a Stub or Mock object, overloaded methods are not supported.
• Inspection of DataSet properties is not complete.

Changes Since Last Release

• Support for DataSets.
  • DataSets are identified in procedures and classes
  • DataSet parameters are now identified
• Support for Temp-Tables
  • Although it is not currently possible to support automatic detection of Temp-Tables, they can be manually added to a test double through method calls.
• Support for procedure file parameter
  • Although it is not currently possible to support automatic detection of parameters declared in the main block of a procedure, they can be manually added to a test double through method calls.
• Table Parameters are correctly identified in class methods, functions and procedures
• Ability to define expected parameter values for use in Expectations
• Documentation has been moved into OEMock Wiki

v0.1-alpha

Initial release of OEMock.

This version is functional, but does not provide many features, and does not support more that the most basic coding patterns (for example, only a few types of parameters are supported, and Mock objects cannot assert how many times a method/procedure/function is called with a specific input value.)

Known Issues/Limitations

• When identifying class methods in a Stub or Mock object, overloaded methods are not supported.
• Only primitive data types, objects and buffers are correctly identified and supported on stubbed/mocked methods/procedures or functions.
• Temp-Tables cannot be identified as method/procedure/function parameters and are currently not supported.
• Parameters passed to or from procedure files are not supported.
• Datasets are not identified or supported.
• Expectations cannot be set on Mock objects which identify the number of times a method/procedure/function is called with a particular parameter value.