New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use testify with custom build type? #131
Comments
Okay, it seems like i was missing some additions, that were not mentioned in the docs.
Maybe you could improve the docs here, since this was really tricky to find out. |
@bkonrad-check Thank you for logging this issue. Support for multi-modules and custom build types is an emerging topic of interest. Testify can be customized for many build configurations, but most of the that support was added to the codebase long ago, but without the necessary documentation. It's a priority for us to include more detailed and advanced guidance on handling these scenarios. We're also working on updating the Sample to include more realistic, real-world examples which will be useful for helping developers set up Testify in their apps. |
Hey!
But I gets error then running
UPD: |
@zhkvdm If this isn't working, it's possible the auto-detection of the tasks is failing for your project. You can try to manually configure the task dependency in your You can try setting:
You can also try running in "verbose" mode as this will print out the underlying
|
Hey there,
in our app we have an custom build type for us, on which our instrumentation tests rely,, which is called GoogleMock, so build type and flavor. So the default installDebug isn't working.
I set this up like this:
This isn't working, since for some reason the androidx.test.runner.AndroidJUnitRunner cannot be found. The error looks like:
However, if I use an example project, where I don't have the build type, same dependency versions and just use debug everything is working fine. So I guess either I have to configure something else or there might be an issue in testify, which leads to not working code in case of build variants.
Look forward for help, thanks!
The text was updated successfully, but these errors were encountered: