[ https://jira.jboss.org/jira/browse/ISPN-323?page=com.atlassian.jira.plugi... ] Sanne Grinovero updated ISPN-323: --------------------------------- Summary: Identify tests not cleaning up their CacheManager (was: Indentify tests not cleaning up their CacheManager) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-323?page=com.atlassian.jira.plugi... ] Manik Surtani edited comment on ISPN-323 at 1/4/10 6:27 AM: ------------------------------------------------------------ Perhaps you could add a TestNG test listener to print out a list of all tests that have a running cache manager at the end of a test run? was (Author: manik.surtani(a)jboss.com): Perhaps you could add a TestNG cache listener to print out a list of all tests that have a running cache manager at the end of a test run? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-323?page=com.atlassian.jira.plugi... ] Mircea Markus commented on ISPN-323: ------------------------------------ Same as: https://jira.jboss.org/jira/browse/ISPN-314 The solution we used in JBossCache (the test fwk was taken from there), was to: - each test passes its TestName.class object when instantiating a new CacheManager - fwk keeps track of the test class that instantiated it - when the .class is different from the previous call (i.e. the thread moved to next test class) make sure that all the managers were destroyed The cache listeners idea sounds appealing as well... I suggest closing this JIRA and pointing to the other one -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/ISPN-323?page=com.atlassian.jira.plugi... ] Sanne Grinovero resolved ISPN-323. ---------------------------------- Resolution: Done Following Mircea's advice, this listener is finished: more could be done in ISPN-314 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira