Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Take a look at the <a href="http://maven.apache.org/plugins/maven-failsafe-plugin/integration-test-mojo.html#includes">failsafe docs</a> for the test names <code>failsafe</code> expects by default:</p> <pre><code>&lt;includes&gt; &lt;include&gt;**/IT*.java&lt;/include&gt; &lt;include&gt;**/*IT.java&lt;/include&gt; &lt;include&gt;**/*ITCase.java&lt;/include&gt; &lt;/includes&gt; </code></pre> <p>Are your tests named following one of these patterns? If not, try defining the <code>&lt;includes&gt;</code> element in the plugin configuration. Or change your test name(s) to fit the default pattern.</p> <hr> <p>Okay, now that we've verified the test class names - typically when I add executions to plugin config I do it something like this:</p> <pre><code>&lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-failsafe-plugin&lt;/artifactId&gt; &lt;version&gt;${version.maven.failsafe.plugin}&lt;/version&gt; &lt;configuration&gt; &lt;/configuration&gt; &lt;executions&gt; &lt;execution&gt; &lt;id&gt;failsafe-integration-tests&lt;/id&gt; &lt;phase&gt;integration-test&lt;/phase&gt; &lt;goals&gt; &lt;goal&gt;integration-test&lt;/goal&gt; &lt;/goals&gt; &lt;/execution&gt; &lt;execution&gt; &lt;id&gt;failsafe-verify&lt;/id&gt; &lt;phase&gt;verify&lt;/phase&gt; &lt;goals&gt; &lt;goal&gt;verify&lt;/goal&gt; &lt;/goals&gt; &lt;/execution&gt; &lt;/executions&gt; &lt;/plugin&gt; </code></pre> <p>This explicitly binds the <code>failsafe</code> plugin goals you want to run to the correct phases of the build lifecycle. I believe the <code>surefire</code> plugin is bound to the <code>test</code> lifecycle phase by default (for a jar, war, &amp; ejb anyway), but nothing is bound to <code>integration-test</code> or <code>verify</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POfailsafe plugin won't run on one project but will run on another -- why?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChristopher Poile
    1. USuser944849
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POfailsafe plugin won't run on one project but will run on another -- why?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COYep, my integration tests are named foobarIT.java. I've even tried explicitly putting the `includes` in (and did it again now, just in case). The problem now isn't that failsafe doesn't find my tests -- it does, when I run `mvn failsafe:integration-test`. The problem is when I run `mvn verify` or `mvn integration-test` failsafe isn't called, surefire is.
      singulars
      1. PO
      1. USChristopher Poile
    2. COAnd that did it! I wonder why just `<goal>integration-test</goal>` didn't work before. Weird. Anyway, thank you!
      singulars
      1. PO
      1. USChristopher Poile
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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