Confirm
355
edits
Changes
no edit summary
hw.ramSize=256
</pre>
<p><span class="fck_mw_template">{{note|Target (in the example above, <<tt>>android-10<</tt>>;) probably needs to match build specified in .mozconfig (see Building Fennec Native below).}}</span>
</p>
<ul><li> to launch:
mvn test
</pre>
<p><span class="fck_mw_template">{{note|<<tt>>mvn assembly:assembly<</tt> > may fail, however, it is still ok to proceed.}}</span>
</p><p>To do real Android development and testing, you need to import android-sync as a project in Eclipse with the ADT installed.
</p><p>Note that both android-sync and sync-crypto have JUnit 4 tests that run in both Eclipse and Maven. The subdirectory android-sync/test includes Android JUnit 3 tests for activity and store testing. This is to avoid the mammoth annoyance of testing in a VM without introducing robolectric.
<pre class="_fck_mw_lspace">$ANDROID_HOME/platform-tools/adb install -r objdir-droid/dist/fennec*apk
</pre>
<p><span class="fck_mw_template">{{note|You may need to run <<tt>>adb kill-server; adb start-server<</tt> > if adb doesn't recognize the emulator.}}</span>
</p>
<h4> Accessing Fennec/Android Sync debug statements </h4>
<ul><li> Open Eclipse, choose <tt>File > Import... > General > Existing Projects into Workspace</tt>, and specify your git repository directory.
</li></ul>
<p><span class="fck_mw_template">{{note|You may need to set <<tt>>M2_REPO<</tt>>; (for example, as described at [http://www.mkyong.com/maven/how-to-configure-m2_repo-variable-in-eclipse-ide/]) to something like <<tt>>$HOME/.m2/repository<</tt>>.}}</span>
</p>
<h4> To run the unit test suite under Eclipse </h4>
