amoss

amoss copied to clipboard

Checking the number of times a method has been called

1

Hi @bobalicious! Love the project! Is there any way we can tell how many times a method has been called? Some use cases for this feature: - we're not worried...

bowdi

Implement Adaptor or produce examples of use of Fake SObject framework

2

Example of a Test Double of a Data Source that uses a Fake SObject framework. Potentially implement an adaptor to one as a distinct project, if none exist with an...

bobalicious

bobalicious

StubProvider doesn't get the name of the parameters correctly when mocking abstract classes

bobalicious

Implement the following construct: ``` isACalloutMock() ... .expects() .body().setTo( Object ) ``` And, potentially ``` isACalloutMock() ... .expects() .body().contains( Object ) ``` Both would do a JSON Serialize on the...

bobalicious

Implement multiple checks against a single parameter

2

Pretty low priority, but allow the ability to, for example: ``` when( 'methodName' ) .withParameterNamed( 'parameter1' ) .containing( 'A string' ) .containing( 'Another string' ) ```

bobalicious

Extend the behaviour of the following, to allow for the checking of maps: - `withElementAt` - `withAllElements` - `withAnyElement` Only do it for maps keyed as per the trigger context...

bobalicious

`withFieldsSetTo` is a very useful method for checking that an SObject has certain fields set to certain values, but it can be a little long-winded for checking a single value....

bobalicious

Mixing of behaviours of `when` and `expects` could be better when applied to a single method

1

When applying an `expects` that is more specific than a `when` for a single method, it seems reasonable to expect the `expects` definition to be matched before the `when` is....

bobalicious

Lots of methods take: * Class Name * Method Name * Parameter Names * Parameter Values Feels like this could be better represented by a class, thus simplifying the signature...

bobalicious