Hi Eric,
you can use *JUnit4Android* (an *Android library* project) to build Android
test runner applications for your *JUnit4 *tests and test suites.
https://github.com/dthommes/JUnit4Android/wiki
--
You received this message because you are subscribed to the Google
Groups Android Developers
Well, it doesn't look like InstrumentationTestRunner is compatible
with JUnit4TestAdapter.
Unfortunately, a JUnit 4 test runner can't run an Android test package
against an Android app.
In short, you can't figure it out because it isn't possible.
At this point, it might be more simple to
I was finally able to get this set up in Eclilpse. IT DOES NOT WORK.
The Android TestSuiteBuilder is casting the tests to TestMethod and
TestCase in the 'build' method, and one of those casts is breaking the
JUnit4TestAdapter. So while it is possible to run JUnit 4 tests on
JUnit 3 using the
At this point I really don't understand why Android cannot run JUnit 4
tests 'out of the box'. There MUST be a simple way to get Eclipse/
Android to install a JUnit 4 test runner so that when my tests run on
the device, JUnit 4 is used. It is discouraging that after all of the
reading and
I wish I could help you, but I'll have to be a taker on this thread.
However, I was wondering whether your problems might be due to
Eclipse? Have you tried building your .apk with Ant using aapt?
--
You received this message because you are subscribed to the Google
Groups Android Developers
It depends on what parts you want to test. If you need the android
test framework classes for testing activities and services in a valid
android context then i am not sure if you can make junit 4 work with
it.
However, if you extract your app logic into android independant
classes then you can
On Aug 19, 9:57 am, The.French.DJ the.french...@gmail.com wrote:
It depends on what parts you want to test. If you need the android
test framework classes for testing activities and services in a valid
android context then i am not sure if you can make junit 4 work with
it.
However, if you
JUnit tests Plain Old Java Objects (POJOs). Basically, it loads your
test class, runs a method, instantiates the class that you're testing,
tests the methods, does the asserts, and outputs the results. It
assumes that all the dependencies are built into the application
or .jar file or are on the
I absolutely want my POJO JUnit 4 tests running on the Android
emulator VM, even if they do not reference Android APIs. The reason
for this is fairly clear. Android has a different implementation of
the base Java APIs, and it uses a special VM, so I want to know that
all of the shared code I
I have never tried to use vanilla JUnit 4 running under Android. I am
not absolutely certain, but I predict that it won't work. To run any
test, you need to use InstrumentationTestRunner, and it assumes JUnit
3, which is substantially different from JUnit 4. However, the
documentation for JUnit 4
Ah, thank you very much. That bit of information about the test
runner helped tremendously. Believe it or not, I did some fairly
exhaustive searches on Google regarding this issue, but I always
referenced Android in some way. Had I just search on running JU 4 on
JU 3, I may have found the same
11 matches
Mail list logo
