-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Add Unit Tests #189
Comments
I would love to, but I have very few time for developing the library and no time to write unit tests. |
Ok fair enough, Just keep watching pull requests and I will enable the lib to work with Travis CI. And pad out some tests. |
Ok, thanks :) |
Can't run tests on Windows using Maven: |
robolectric should be before junit. This is my testing dependency. <!-- Robo Electric -->
<dependency>
<groupId>com.squareup</groupId>
<artifactId>fest-android</artifactId>
<version>1.0.3</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.robolectric</groupId>
<artifactId>robolectric</artifactId>
<version>2.0-alpha-3-SNAPSHOT</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.8.2</version>
<scope>test</scope>
</dependency> |
Still have the problem... Searching a solution... |
You have @RunWith(RobolectricRunner.class) at the top of you test case. Also remembering that any class/lib you don't have implemented you'll need
|
I use robolectric-2.0-alpha-1 to avoid "Stub!" problem. |
Stub just means it can't find a class it's trying to run. if you look at my fork and the commits made you will see what is necessary
|
Your fork has the same "Stub!" problem for me. |
It would save you alot of time when regression testing if you added some unit test.
Especially in the case of the image downloaders.
The text was updated successfully, but these errors were encountered: