This should resolve the issue raised in #53. It turned out that there is no real way to know if a method is generated by the compiler or not (at least on 3.2), so instead I use the fact that default values follow the same naming schemes to exclude them from the list of the methods to override in the mock.
This should resolve the issue raised in #53. It turned out that there is no real way to know if a method is generated by the compiler or not (at least on 3.2), so instead I use the fact that default values follow the same naming schemes to exclude them from the list of the methods to override in the mock.