Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am assuming you are familiar with the <a href="http://code.google.com/p/maven-android-plugin/" rel="nofollow noreferrer">Android Maven plugin</a>? If not, you should check it out. Here is a method that is not bulletproof, but should work:</p> <p>1- Start by writing a shell script that launches the Calabash tests. This shell script, say <code>calabash.sh</code>, wouldn't be too complicated, just something along the lines of:</p> <pre><code>calabash-android run ../target/&lt;app&gt;.apk /path/to/calabash/tests </code></pre> <p>2- Launch this script once <code>maven</code> has finished its <code>integration-test</code> phase (if you are using <code>Android Maven</code>, that's when you run your unit tests). This is taken from <a href="https://stackoverflow.com/questions/3491937/i-want-to-execute-shell-commands-from-mavens-pom-xml">this SO question</a>:</p> <pre><code>&lt;plugin&gt; &lt;artifactId&gt;exec-maven-plugin&lt;/artifactId&gt; &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt; &lt;executions&gt; &lt;execution&gt; &lt;id&gt;Version Calculation&lt;/id&gt; &lt;phase&gt;validate&lt;/phase&gt; //This occurs [after integration-test][3] &lt;goals&gt; &lt;goal&gt;exec&lt;/goal&gt; &lt;/goals&gt; &lt;configuration&gt; &lt;executable&gt;${basedir}/scripts/calabash.sh&lt;/executable&gt; &lt;/configuration&gt; &lt;/execution&gt; &lt;/executions&gt; &lt;/plugin&gt; </code></pre> <p>This is not a bulletproof solution because I suspect that Maven cannot report any calabash test failures. Also, you might need to add some bash magic to make the script run until completion before Maven finishes building.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload