Confirmed users
355
edits
CloudServices/NativeSync: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Nalexander (talk | contribs) No edit summary |
|||
| Line 25: | Line 25: | ||
hw.ramSize=256 | hw.ramSize=256 | ||
</pre> | </pre> | ||
<p><span class="fck_mw_template">{{note|Target (in the example above, | <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> | </p> | ||
<ul><li> to launch: | <ul><li> to launch: | ||
| Line 85: | Line 85: | ||
mvn test | mvn test | ||
</pre> | </pre> | ||
<p><span class="fck_mw_template">{{note| | <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>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. | </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. | ||
| Line 110: | Line 110: | ||
<pre class="_fck_mw_lspace">$ANDROID_HOME/platform-tools/adb install -r objdir-droid/dist/fennec*apk | <pre class="_fck_mw_lspace">$ANDROID_HOME/platform-tools/adb install -r objdir-droid/dist/fennec*apk | ||
</pre> | </pre> | ||
<p><span class="fck_mw_template">{{note|You may need to run | <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> | </p> | ||
<h4> Accessing Fennec/Android Sync debug statements </h4> | <h4> Accessing Fennec/Android Sync debug statements </h4> | ||
| Line 132: | Line 132: | ||
<ul><li> Open Eclipse, choose <tt>File > Import... > General > Existing Projects into Workspace</tt>, and specify your git repository directory. | <ul><li> Open Eclipse, choose <tt>File > Import... > General > Existing Projects into Workspace</tt>, and specify your git repository directory. | ||
</li></ul> | </li></ul> | ||
<p><span class="fck_mw_template">{{note|You may need to set | <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> | </p> | ||
<h4> To run the unit test suite under Eclipse </h4> | <h4> To run the unit test suite under Eclipse </h4> | ||