Take interfaces out into their own files

[dafyddjohns]

The interfaces as they currently stand, within the SOQL class, do not allow then to be utilised with frameworks such as Apex Mockery, that depends on Test.createStub(). Mocking an inner type such as Queryable throws a System.TypeException with message "Test.createStub() cannot be called with inner Apex classes".

I can see that there is a mechanism to mock, but I'd like to be aligned with the apex mockery framework.

Context:
Apex Mockery is being used to create mocks of dependencies, but one of my dependencies uses SOQL lib. My real implementation has no coverage, which is expected as I haven't done integration tests, but I do want to verify that certain methods within my dependency are performing queries that contain certain logic.

Moving the interfaces out would allow better compatibility with such frameworks.

[dafyddjohns]

From what I can see, this isn't as easy as moving those interfaces out. Each of those interfaces then becomes a dependency if you are mocking the outermost Queryable class. I would need to mock a bunch of the other interfaces that feed into the query in order to spy on them, but there might be a simpler way. Essentially I want to be able to use Mockery's "this method was called with this argument", to ensure the logic is baked into the queries.

Any guidance/recommendations/thoughts appreciated.

[pgajek2]

Hi @dafyddjohns ,

Thanks for bringing that up - very interesting topic. I never thought there would be a need to move it outside, but you made some very valid points.

I created a new branch, feature/soql-interfaces:
https://github.com/beyond-the-cloud-dev/soql-lib/tree/feature/soql-interfaces/force-app/main/default/classes/standard-soql

On that branch, I moved the interfaces out. All interfaces are now in a separate folder, so you can click the folder and deploy everything at once.

Please let me know if it works for you.