8:44 a.m.
Bartosz Majsak created ARQ-755:
----------------------------------
Summary: Introduce annotation based db cleanup configuration
Key: ARQ-755
URL: https://issues.jboss.org/browse/ARQ-755
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all test
cases, but when define on method level it will override global settings.
--
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
5:29 a.m.
[
https://issues.jboss.org/browse/ARQ-755?page=com.atlassian.jira.plugin.sy...
]
Work on ARQ-755 started by Bartosz Majsak.
Introduce annotation based db cleanup configuration
---------------------------------------------------
Key: ARQ-755
URL: https://issues.jboss.org/browse/ARQ-755
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all
test cases, but when define on method level it will override global settings.
--
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
10:45 a.m.
[
https://issues.jboss.org/browse/ARQ-755?page=com.atlassian.jira.plugin.sy...
]
Bartosz Majsak updated ARQ-755:
-------------------------------
Description:
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all test
cases, but when define on method level it will override global settings.
Additionally there should @UsingScript counter part provided to give a user possiblity to
clean up database after test execution.
- rename @UsingScript to @UsingScriptBefore
- introduce @UsingScriptAfter
was:
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all test
cases, but when define on method level it will override global settings.
Introduce annotation based db cleanup configuration
---------------------------------------------------
Key: ARQ-755
URL: https://issues.jboss.org/browse/ARQ-755
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all
test cases, but when define on method level it will override global settings.
Additionally there should @UsingScript counter part provided to give a user possiblity to
clean up database after test execution.
- rename @UsingScript to @UsingScriptBefore
- introduce @UsingScriptAfter
--
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
11:06 a.m.
[
https://issues.jboss.org/browse/ARQ-755?page=com.atlassian.jira.plugin.sy...
]
Bartosz Majsak updated ARQ-755:
-------------------------------
Description:
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all test
cases, but when define on method level it will override global settings.
was:
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all test
cases, but when define on method level it will override global settings.
Additionally there should @UsingScript counter part provided to give a user possiblity to
clean up database after test execution.
- rename @UsingScript to @UsingScriptBefore
- introduce @UsingScriptAfter
Introduce annotation based db cleanup configuration
---------------------------------------------------
Key: ARQ-755
URL: https://issues.jboss.org/browse/ARQ-755
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all
test cases, but when define on method level it will override global settings.
--
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
1:15 p.m.
[
https://issues.jboss.org/browse/ARQ-755?page=com.atlassian.jira.plugin.sy...
]
Bartosz Majsak resolved ARQ-755.
--------------------------------
Resolution: Done
Introduce annotation based db cleanup configuration
---------------------------------------------------
Key: ARQ-755
URL: https://issues.jboss.org/browse/ARQ-755
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all
test cases, but when define on method level it will override global settings.
--
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
12:06 p.m.
[
https://issues.jboss.org/browse/ARQ-755?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen updated ARQ-755:
------------------------------
Fix Version/s: persistence_1.0.0.Alpha4
(was: persistence_1.0.0.next)
Introduce annotation based db cleanup configuration
---------------------------------------------------
Key: ARQ-755
URL: https://issues.jboss.org/browse/ARQ-755
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.Alpha4
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all
test cases, but when define on method level it will override global settings.
--
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
1:40 p.m.
[
https://issues.jboss.org/browse/ARQ-755?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-755.
-----------------------------
Introduce annotation based db cleanup configuration
---------------------------------------------------
Key: ARQ-755
URL: https://issues.jboss.org/browse/ARQ-755
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha3
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.Alpha4
User should have control on data cleanup event. Currently it's always executed after
the test. Provide @Cleanup annotation with following options:
- DISABLED
- BEFORE (default)
- AFTER
This annotation can be placed on class level - defining the default behaviour for all
test cases, but when define on method level it will override global settings.
--
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
5018
days inactive
5074
days old
arquillian-issues@lists.jboss.org
6 comments
2 participants
participants (2)
-
Aslak Knutsen (JIRA) -
Bartosz Majsak (JIRA)