Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created 2 modules with benchmarks for mockk and mockingbird,
benchmark-mockingbird
andbenchmark-mockk
as the control benchmark.Currently, mockingbird benchmark runs using gradle-profiler for an average of 3610ms, while mockk runs with an average of 3263ms. This discrepancy is due to the lack of any KSP code generation running on the mockk benchmark. I did some preliminary testing, and it showed that if a KSP is added to the mockk, for example, if dagger is added to both benchmarks, the discrepancy is non existent and mockingbird performs slightly better. I'm going to leave the benchmarks without this for now.
In order to run the benchmarks, select a folder that you want to run the benchmark in, and then run
and