Unit tests for OpenSatNav

[droidguy]

Unit tests for OSN. In two separate projects (each of them depends on the OpenSatNav:

* OpenSatNav_AndroidTest - Android native unit tests. Useful for lifecycle unit testing, but no mocking is supported. They're slower, because they run in the emulator. Start: Run As -> Android JUnit Test in eclipse.

* OpenSatNav_JavaTests - JUnit tests. Support mocking through standard Java mocking framework (here chosen: mockito framework). Run in eclipse (not in the emulator) using JVM rather than Dalvik VM. Require android.jar, which is a compiled Android Java code. Faster.

[droidguy (stan-berka)]

1. Can you commit it to repository?

2. I have not added the Java unit test project yet, because I'm not sure whether I should include the libraries (mockito framework + android.jar) or let the developer download them from the internet when setting up the project in his/her machine.

[chris_debian (cjhandrew)]

I'm not sure of the implications for other developers, but in principle it sounds ok.

Thanks for the idea.

Chris.

[Guillaume Rosaire (zerog)]

The SVN repository currently supports only one project (OSN), we need to change its layout with Enrique's Help, I'll try to contact him.

[Kieran Fleming (kieran-fleming)]

Thanks ZeroG.
About the android.jar and mockito, I think they should go in the repo so it's as easy as possible to do the testing.

[droidguy (stan-berka)]

I agree, that it may require to move stuff in repository. Specifically, I would move the OSN eclipse project from root/trunk, down to root/trunk/main or something like this, and place the tests in root/trunk/test-android and root/trunk/test-junit.
This way, one can deliver a patch to the app project which will also contain new/updated tests. Also, this way the tests and the app changes can be committed in the same revision and checked out together easily. Is this what you were thinking?
droidguy

[droidguy (stan-berka)]

I'm attaching the JUnit test project with all libraries included.