When implementing the MapboxSearch SDK, when creating tests for my ViewModel, I encountered the challenge of creating stubs for the classes exposed in the SDK, such as PlaceAutocomplete.Suggestion and PlaceAutocomplete.Result.
It's not possible to create stubs because the constructors of these classes are internal and not public.
I can create stubs if I make the library import @testable, but this makes the build for testing very slow.
The solution could be something simple, just adding public to the constructors of these classes/structs/enums. Or, exposing stub methods through a test artifact in the SDK for us to use.
Would that be possible?
When implementing the MapboxSearch SDK, when creating tests for my ViewModel, I encountered the challenge of creating stubs for the classes exposed in the SDK, such as
PlaceAutocomplete.SuggestionandPlaceAutocomplete.Result.It's not possible to create stubs because the constructors of these classes are internal and not public.
I can create stubs if I make the library import
@testable, but this makes the build for testing very slow.The solution could be something simple, just adding
publicto the constructors of these classes/structs/enums. Or, exposing stub methods through a test artifact in the SDK for us to use.Would that be possible?