[
https://issues.jboss.org/browse/AS7-3728?page=com.atlassian.jira.plugin.s...
]
Miroslav Novak commented on AS7-3728:
-------------------------------------
Hi all,
I believe this feature would help us a lot with reducing effort to maintain AS7 testsuite.
For example for HornetQ testing we need to have very different configuration for HA
topologies - dedicated/colocated. We have to test it in different modes of paging like
BLOG/PAGE or AIO/NIO. Then if it's clustered/non-clustered and there are more
combinations we'd like to test.
Restoring configuration file after each test brings us much more effort and is very
error-prone. Suggested feature would save a lot of time.
We tried to precise requested feature for reloading configuration:
- @RestoreASConfigAfterTest as described will be needed per test and per test class
- per test - configuration will restore to state before the whole test class was
started
- we also need to have possibility to delete "tmp", "log",
"data" and "deployments" directory per test and per test class. But
those could be separate annotation for better flexibility.
Thanks,
Mirek
@RestoreASConfigAfterTest to make a snapshot before test and reload
it after.
-----------------------------------------------------------------------------
Key: AS7-3728
URL:
https://issues.jboss.org/browse/AS7-3728
Project: Application Server 7
Issue Type: Feature Request
Reporter: Ondrej Zizka
Assignee: Aslak Knutsen
Having a possibility to restore server configuration after the test is run, or similar
principle, would be very cool.
For example, there are some tests which change datasource config quite dramatically.
And getting it back to the original state afterwards requires a lot of coding.
So instead, the test would have {{@RestoreASConfigAfterTest}}
and Arq would re-load a snapshot it made before the test was run.
--
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