Maybe I misread the doc - it was suggesting to me you needed
@RunWith(Categories)
On 02/02/17 20:49, Martin Choma wrote:
What do you mean?
@Category is already used in testsuite in conjuction with Arquillian,
e.g. WebSecurityBASICTestCase.
On Thu, Feb 2, 2017 at 7:36 PM, Darran Lofthouse
<darran.lofthouse(a)jboss.com <mailto:darran.lofthouse@jboss.com>> wrote:
That was a short lived decision.
We can only use @Category with the Categories runner but we are already
using the Arquillian runner.
I think back to the system property.
On 02/02/17 18:25, Darran Lofthouse wrote:
> I am going to give @Category a go - with Assume.assumeTrue I think we
> have the problem that some tests may be failing in their
initialisation
> code and that risks leaving behind orphaned processes that break
further
> tests.
>
> On 01/02/17 13:41, Martin Choma wrote:
>> Right, I see.
>> You can add property in testsuite/pom.xml to switch
InvocationIssue test
>> by default (works for me)
>>
>> <properties>
>> <excludedGroups>InvocationIssue</excludedGroups>
>>
>> New CI jobs have to be executed with empty excludedGroups, e.g.
>> -DexcludedGroups=
>>
>> But I admit SP approach is more obvious here.
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
<
https://lists.jboss.org/mailman/listinfo/wildfly-dev>
>>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
<
https://lists.jboss.org/mailman/listinfo/wildfly-dev>
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
<
https://lists.jboss.org/mailman/listinfo/wildfly-dev>