[jboss-jira] [JBoss JIRA] (AS7-3730) Arq: @CleanContainerDataDirsAfterTest - Delete data/ and /tmp after test is run.

[Ondrej Zizka (JIRA)]

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

Ondrej Zizka commented on AS7-3730:
-----------------------------------

{quote}
/data can actually contain real application data, such as timers and the transaction log. 
{quote}
That's exactly what we need to delete.

{quote}
it can be easily accomplished by setting up the maven clean plugin to clean up those dirs, without any arquillian changes.
{quote}
Unfortunately, that's not true. Maven can handle it only at the surefire-execution level **at best**.
We need to delete it **after each test method**. The other option is to have an extra surefire run for each test, with one test class per test. Not nice.

Anyway, this functionality would go to AS 7 container, so there will be no changes to Arquillian itself.
                
> Arq: @CleanContainerDataDirsAfterTest - Delete data/ and /tmp after test is run.
> --------------------------------------------------------------------------------
>
>                 Key: AS7-3730
>                 URL: https://issues.jboss.org/browse/AS7-3730
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Test Suite
>            Reporter: Ondrej Zizka
>            Assignee: Aslak Knutsen
>             Fix For: 7.1.1.Final
>
>
> Some tests leave files in AS /data dir.
> And the tested modules bypass their configuration from standalone.xml and rather rely on these data.
> This prevents running multiple tests within a single AS instance run; therefore, multiple AS instances, Surefire executions or Maven modules are needed.
> Having something like {{@CleanContainerDataDirsAfterTest}} per method would make writing these tests much easier and faster to run.
> Further, sometimes these tests run with multiple instances (clustering, messaging, ...).
> Not all of them may loose data in some scenarios - some of them must keep the data (e.g. for failover testing).
> Therefore, the annotation should have parameters - a list of container config names (matching arquillian.xml). Only those instances would be cleaned.
> {code:java}
> @CleanContainerDataDirsAfterTest({"InstanceFoo", "InstanceBar"})
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira