maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dao Le (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-1045) Separate of each test class into 1 suite causes problem with setUp embedded DBs and testNG dependsOnGroup
Date Fri, 06 Dec 2013 16:53:45 GMT

     [ https://jira.codehaus.org/browse/SUREFIRE-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dao Le updated SUREFIRE-1045:
-----------------------------

    Description: 
There are 2 problems with this approach:
1/ EmbeddedMongo was to be run before the tests, it is pretty slow to set up and tear down
and even causes problems when I do this too often. In the old version, everything is a big
suite, so we only need to start it once (using @BeforeSuite) and drop all the databases before
each test method, and then tear down (using @AfterSuite.) Now this is not possible, and as
mention, I can't set up and tear down on each test class.

2/ I want to run testB() of class B after a group of tests in class A. This is also not possible.

  was:
There are 2 problems with this approach:
1/ I want to run EmbeddedMongo, it is pretty slow to set up and tear down and even causes
problems when I do this too often. In the old version, everything is a big suite, so we only
need to start it once (using @BeforeSuite) and drop all the databases before each test method,
and then tear down (using @AfterSuite.) Now this is not possible, and as mention, I can't
set up and tear down on each test class.

2/ I want to run testB() of class B after a group of tests in class A. This is also not possible.

    
> Separate of each test class into 1 suite causes problem with setUp embedded DBs and testNG
dependsOnGroup
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1045
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1045
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: TestNG support
>    Affects Versions: 2.16
>            Reporter: Dao Le
>
> There are 2 problems with this approach:
> 1/ EmbeddedMongo was to be run before the tests, it is pretty slow to set up and tear
down and even causes problems when I do this too often. In the old version, everything is
a big suite, so we only need to start it once (using @BeforeSuite) and drop all the databases
before each test method, and then tear down (using @AfterSuite.) Now this is not possible,
and as mention, I can't set up and tear down on each test class.
> 2/ I want to run testB() of class B after a group of tests in class A. This is also not
possible.

--
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

Mime
View raw message