Allow expectations on BUFFER, TABLE and DATASET parameters #30
Description
In issue #22, changes were made to fix an issue where recording the value of BUFFER, TABLE and DATASET parameters would fail.
The fix was to only generate calls to OEMockRegister:RegisterMethodCallParam() for primitive (and object) type parameters. This prevents expectations from being raised on BUFFER, TABLE and DATASET parameters.
New functionality should be added to allow expectations to be set on these parameters.
For each parameter type, different types of expectations are required - for example, on a BUFFER type, do you verify that a record is available or not? On a TABLE parameter, do you verify the number of records that are linked to the table?