Chandler Anderson

No problem! Thank you for the quick response.

Thank you @davidmreed for the transparency! That is a good workaround for now, really appreciate the insight.

I have the same requirement, specifically to generate `test-result-codecoverage.json` for use with a static code scanner (SonarQube) that is compatible specifically with the SFDX-generated file. @davidmreed are there other ways...

> Hi @zenibako ! > > Do you experienced the issue with [custom apex types](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/langCon_apex_expressions_operators_understanding.htm#:~:text=User%2Ddefined%20types%20are%20compared%20by%20reference%2C%20which%20means%20that%20two%20objects%20are%20equal%20only%20if%20they%20reference%20the%20same%20location%20in%20memory.%20You%20can%20override%20this%20default%20comparison%20behavior%20by%20providing%20equals%20and%20hashCode%20methods%20in%20your%20class%20to%20compare%20object%20values%20instead.) only ? Exactly; I was setting up a spy on a method that takes an...

Thanks for the suggestions. Just committed a change to use `==` instead of `String.equals()` to maintain consistency. I tried to use `jsonEqual`, but it reintroduces the original issue. It appears...

@scolladon Thank you for explaining that in more detail. I can implement a unit test to recreate my problem scenario and find an alternative approach that isn't at risk at...

@scolladon It turns out that the issue was actually due to me using an SObject as an argument for `whenCalledWith()`. So the Custom Apex Type thing was a red herring....

OK, so here are my findings: The source of the problem in my codebase was that I was using SObject types (`OauthTokenExchangeHandler` and `OauthTokenExchHandlerApp`) that were not supported before API...

> Thank you very much for your work here, I learned a lot about how apex type works :) > > I think the PR is nearly ready, I have...

Applied the `EqualsMatchable` suggestion. I think that does it for these changes then.