[
https://issues.jboss.org/browse/AS7-5844?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-5844:
-----------------------------------
The idea/requests behind this is that packages only allow to divide tests into a tree. But
sometimes, as Stuart wrote, there are some cross-cutting concerns, see the suggested
categories. It's not supposed to replace package-based fine-grained division, but to
complement it, to allow define groups of tests they need to run, instead of creating and
maintaining list of packages or even classes.
Another example where current model has some flaws are smoke tests: Separating the tests
physically to different module is artificial and not much semantic: If any tests starts
being considered as smoke test, what we do? Move it to different module and change package
name. Does that make sense? Wouldn't it be better to just add `(a)Category(Smoke.class)`
?
It also collides with the technical solution of separating tests by type of server setup
(multinode, ...). If we decided to include a multinode test as smoke, what would we do?
Move it to smoke module and create another surefire execution? Doesn't make much
sense. Just adding the `Smoke` category and filtering the tests to be run using categories
is way better.
TS: Tests grouping 2: Create categories & let devs categorize the
tests.
------------------------------------------------------------------------
Key: AS7-5844
URL:
https://issues.jboss.org/browse/AS7-5844
Project: Application Server 7
Issue Type: Feature Request
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Based on AS7-2086 and SUREFIRE-803, we can now create the categories for tests.
They would be in testsuite/shared.
Example:
{code}
interface AllTests;
interface ATests extends AllTests;
interface BTests extends AllTests;
interface AaTests extends ATests;
@Category(ATests.class) public void ATest();
@Category(AaTests.class) public void AaTest();
@Category(BTests.class) public void BTest();
{code}
It should be possible to have multiple categories:
{code}
@Categories({Foo.class, Bar.class})
{code}
TODO: Check if it also works with FailSafe.
Some categories candidates (feel free to extend):
* ASTest
** EJB
** JPA
** Management
** Security
*** CommonCriteria
** NonArquillian
** Transactions
** Multinode
*** Clustering
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira