[jbosstools-issues] [JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132908#comment-13132908 ] 

Nick Boldt commented on JBIDE-19081:
------------------------------------

Do we still want to change the default include/exclude for what test classes are run, and apply that change in 4.4.x/10.0? See https://github.com/jbosstools/jbosstools-build/pull/167 for the last attempt to solve this, and its discussion.

> Use simpler Surefire include/exclude pattern in parent pom
> ----------------------------------------------------------
>
>                 Key: JBIDE-19081
>                 URL: https://issues.jboss.org/browse/JBIDE-19081
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Max Rydahl Andersen
>            Priority: Minor
>             Fix For: 4.4.x
>
>
> 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude:
> {code}
> include = *Test*, *Test, *TestCase
> exclude = *Abstract*
> {code}
> 2. If that causes test failures because running incorrectly named
> abstract stuff, they can refactor, add their own root pom overrides, use
> a TestSuite, or use @Ignore in test classes.
> 3. If the count of tests run suddenly DROPS because the pattern isn't
> running the correct # of tests, they can add their own root pom
> overrides, or use a TestSuite.
> Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)