-
Notifications
You must be signed in to change notification settings - Fork 395
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
Junit4 test runner #625
Junit4 test runner #625
Conversation
Motivation: We are now going to support two testing styles. The Javadoc of the finder now explicitly states that it checks the old style of tests run by the instrumentation test runner.
Notes: Perhaps we want to remove the default/empty methods?
20d414f
to
7456194
Compare
df192f2
to
e0fbd5c
Compare
I need the Android support stuff to be installed in maven local for the test to work. I've tried setting the m2 repository android creates in the sdk as part of my repositories in the test, but this doesn't seem to be working. Suggestions? |
Have you tried creating a hosted repository in Nexus that points to the Android SDK m2 repo? |
I mean it runs on my machine and if I deploy with the sdk deployer I don't need the repository stuff in the test project's pom. This is a no sdk deployer on Travis problem. |
I am inclined to remove the execution of the IT tests from the travis run to be honest. I has mostly been failing anyway. In the long run we hopefully get the provision mojo implemented so that we can get the SDK Maven repos into the local Maven repo and then run IT's on travis again. Wdyt @simpligility/android-maven-plugins-core-committers |
Merged this now and also disabled the IT tests to see if this goes green in travis as it should.. |
Fixes #623 and supplies JUnit runner.
Also fixes #617 (see a9f051f)